I posted this in another thread:

"By default, the driver pack does not have the JMicron controllers set up correctly. You need to edit the txtsetup.sif with the CC_0104 and CC_0106 suffixes, and also add CC_0101 to the exclusion list of both the jraid and jahci INF files."

Could you post a global topic to explain in details what exactly you modify in txtsetup.sif to use JMicron controler ? Thanks for all
Best regards from France...

rayw69 wrote:

Bâshrat the Sneaky wrote:

Couldn't agree more

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

I don't think it is fair to call jmicron crap just because the txtsetup.sif file is not created correctly when using driverpacks.

I would agree with you, if this were the first time we had a bad JMicron experience. But I will look into that supposed txtsetup.sif error. I'd be very glad if that would solve everything, and then I would draw my words back as well. But I'm afraid we're not the only ones having this issue... Just google for JMicron BSOD and you'll find plenty of hits.

Well, if that is the litmus test for whether or not something is crap or not, then every single brand is crap. I can type in the words "Nvidia" or "Intel" or "ATI" or "Promise" or anything else with "BSOD" into google and get a million results.

I posted this in another thread:

"By default, the driver pack does not have the JMicron controllers set up correctly. You need to edit the txtsetup.sif with the CC_0104 and CC_0106 suffixes, and also add CC_0101 to the exclusion list of both the jraid and jahci INF files."

It took me the better part of a day to figure out the above. Lots and lots of manual editing of the txtsetup.sif file and the various other SIF and .inf files. And multiple installations of Windows XP. When I discovered driverpacks and how to pre-load drivers, I literally had zero experience with txtsetup.oem files, and how to properly edit .inf files. This whole jmicron thing is really a simple problem, for a person with previous experience editing .inf files, and knows what the various suffixes for device IDs refer to.

I'd be willing to bet that there are other drivers in the mass storage driverpack which need the EXACT same kind of editing to work properly. Suppose there was a problem with the Highpoint driver in driverpacks. How would you ever find out? Not like any motherboard manufacturers are using Highpoint controllers.

It is just that the Jmicron controllers have become real popular lately with the new Intel southbridges that completely eliminate IDE support. Just about every damn Intel board using ICH8/ICH8R is going to have a Jmicron controller integrated for IDE support. The large number of people having problems with Jmicron is simply a reflection of the large number of motherboard manufacturers who are now using Jmicron. If by chance, my motherboard didn't include the Jmicron controller, or I had simply no chosen to use it, then I'd never think there was a problem with the driverpacks.

Anyways, I hope you'll be able to implement the above fixes into the next version of the mass storage driver pack. I think the fact that Jmicron is becoming more and more popular by the day is not a reason to make Jmicron drivers not load by default. If anything, it should be a reason to work harder to find a solution.

Bâshrat the Sneaky wrote:

Bionicmaster wrote:

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

I don't think it is fair to call jmicron crap just because the txtsetup.sif file is not created correctly when using driverpacks.

I would agree with you, if this were the first time we had a bad JMicron experience. But I will look into that supposed txtsetup.sif error. I'd be very glad if that would solve everything, and then I would draw my words back as well. But I'm afraid we're not the only ones having this issue... Just google for JMicron BSOD and you'll find plenty of hits.

Bionicmaster wrote:

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

I don't think it is fair to call jmicron crap just because the txtsetup.sif file is not created correctly when using driverpacks.

hi
I had to leave for work, but just before I did, I looked at the drivers at the asrock site

i put the string posted in the hwid above into search
and this is indeed found in jahci.inf
VEN_197B&DEV_2360
the other F6 driver floppy has ALI

in driverpacks mass storage, this string is found in raid and jahci infs (and nowhere else)

thus, what S3pHiroTh posts makes sense to me.

I have done that me too... I have downloaded the driver from Asrock website (for found where is the problem in driverpacks for bsod) and the only difference between driverpacks and driver downloaded from asrock website, is what I have said before

i put the string posted in the hwid above into search
and this is indeed found in jahci.inf
VEN_197B&DEV_2360
the other F6 driver floppy has ALI

in driverpacks mass storage, this string is found in raid and jahci infs (and nowhere else)

thus, what S3pHiroTh posts makes sense to me.

PCI\VEN_197B&DEV_2360="jraid"
PCI\VEN_197B&DEV_2361="jraid"
PCI\VEN_197B&DEV_2363="jraid"
PCI\VEN_197B&DEV_2365="jraid"
PCI\VEN_197B&DEV_2366="jraid"

This is the piece of txtsetup.sif, as you can see it load always RAID driver!!

change the "jraid" option with "jahci" option for your controller hwid.

I have Asrock 939Dual-Sata2 too and I have solved this by changing the first line

PCI\VEN_197B&DEV_2360="jraid"

to

PCI\VEN_197B&DEV_2360="jahci"

Bye.

in this mobo that mention, I had trouble to install O.S in SATA2 disc with JMicron connector, simply Disc doesn't boot, with or without drivers, Black Screen before Blue Screen Loads.... a real trouble, I was thinking in change discs, my SATA for boot and my SATA2 for info (my SATA in the ALI controller was recognized right, without any driver in IDE mode), thinking that my SATA2 disc was not able to boot, but a few days later, I changed my PC for an AM2 based A64, with nforce 410/Geforce 6100 based Chipset, and all is right, my S.O. is in SATA2 disc and all is right....

Experience: Jmicron is too bad...

Couldn't agree more

I will make the appropriate changes in DriverPack MassStorage, to reflect that JMicron is absolute crap: its drivers will NOT be loaded by default, brave souls will be able to renable them manually.

Experience: Jmicron is too bad...

you could post the version you extracted.

you could compare driver version with what you find in that folder...
jraid.inf
;Copyright 2005, JMicron Technology Corp.

[Version]
Signature="$Windows NT$"
Provider=%JMICRON%
ClassGUID={4D36E97B-E325-11CE-BFC1-08002BE10318}
Class=SCSIAdapter
DriverVer=06/26/2006, 1.12.04.00   
CatalogFile=jraid.cat

the section on asrock

%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2360&SUBSYS_03601849  ; ASROCK
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2361&SUBSYS_03611849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2363&SUBSYS_03631849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_03651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2366&SUBSYS_03661849

%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2360&SUBSYS_23601849  ; ASROCK
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2361&SUBSYS_23611849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2363&SUBSYS_23631849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2365&SUBSYS_23651849
%PCI\VEN_197B&DEV_2363.DeviceDesc% = JM , PCI\VEN_197B&DEV_2366&SUBSYS_23661849

If you have the choice, DO NOT USE THE JMICRON CONTROLLER. But you do not have the choice... Good luck!

the zip file for the JMicron_XP_2k(v207) doesnt contain a floppy image,
but a folder with the needed files.
In the readme.txt, this is mentioned,
If you want to build pre-install disk for windows,
copy directory "X32" and "X64" and file "JMicron", "txtsetup.oem" to floppy disk

So you mean that the problem is only related to the jmicron driver integrated in the mass storage
driver pack?
I will try to integrate the jmicron driver from asrock with nlite.
And after that integrate the driverpacks with dpbase but unchecking the txtmode for mass storage.
Is it that what you mean. Or not integrating the mass storage, only the others?
I want to use this install cd also for my other computers, so the mass storage driver pack would be very handy.

Will try nlite, this afternoon.

thanks for all the support!

here is a link to this model
http://www.asrock.com/product/939Dual-SATA2.htm
Wim may want to look at the supplied drivers...

as a temporary solution, I could suggest Nlite and winimage
winimage to extract the floppy image to a folder (for that F6 floppy)
nlite to integrate only the content that extracted floppy (like I once did for my mobo)

if you want to, driverpacks without mass storage/txtmode
test setup
post results

if it works that way, Bâshrat the Sneaky may want to look at the content of the F6 floppy and redo some filtering