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.