Bâshrat the Sneaky

If you just meant USB 2.0 controllers, that's fine: they are all supported by Windows XP SP2 (note the 'SP2'!).

That's planned for the C++ version of the DriverPacks BASE. I think you understand it'd be completely unmanageable to do that with 'primitive' batch files, since that would be several hundreds of archives! Question answered, topic closed.

Hmm... Then please post your HWIDs. I DID answer the nVidia thingie:

I noticed that a new guide was reported at the frontpage... it was yours! Good initiative! For users that have found this topic through the search function, you can find tarquel's guide right here. Topic closed now.

Thanks again for your fix, tommk I also fixed that nasty typo! Problems solved, topic closed.

I'm afraid there's no decent solution except from using imaging techniques to install Windows XP onto a pc that has a cardreader installed. Cardreaders tend to mess up Windows XP's installation!

BTS DriverPacks And Multi-Boot Discs

@midiboy 1. untrue The HWIDs are different. You can verify that by doing a search in the r5's .inf file for the first HWID of the jbod's .inf file: it will not find it and therefore the ide/jbod/whateveryounameit driver still is necessary. 2a. probably it's indeed an error on your side, else I'd have complaints all over the forum 2b. ehm probably it's the control panel that doesn't finish properly, or are there more files left than just THAT sound driver? 3a. solved thanks to tommk 3b. I'll look into that @tommk Thanks! I was already wondering why it didn't work... I'd never have noticed that syntax error, as did many others not notice it!

This is really an awkward problem :s I'm confident the problem lies at Fujitsu-Siemens' side... But still: could you please post the EXACT (complete) error code? That might help to narrow down the problem to a specific cause.

Could you define what should be in it? What kind of devices it should support?

Got it & checked it. The structure is just fine, the only issue is the FILENAME, as I said in my previous post. You should name it something like DriverPack_custom_for_PVR250.7z, then it will be detected by the DriverPacks BASE.

Then e-mail the file to BashratTheSneaky [AT] gmail [DOT] com.

The filename must be of the type 'DriverPack_*.7z'!

Must be your system... it worked just fine here What error do you get?

Nothing has changed regarding the nForce mass storage drivers. I completed the requests of more than 2,5 months, but I temporarily skipped the old 'main topic': if you posted your problem there, I will process it soon. If you didn't post it there, please point me to it. P.S.: by far the majority of nForce-based motherboards is working just fine!

That controller needed the si3112r driver, it didn't work with the si3112 driver. Please remove that work-around if you want to test if that work-around is no longer necessary.

NOW

DriverPack MassStorage V6.02.1 Changelog: V6.02.1 (25 Feb 06) -Fixed: the driver files for the Intel SATA RAID controller were still the old ones. -New: support for HighPoint RocketRAID 2310 PCIe SATA II Controller. -New: separate driver for ALi/ULi M5288 SATA Controller (M1575/M1697). -Updated: ALi/ULi M5228 ATA/RAID Controller & ALi/ULi M5281/M5283 SATA/RAID Controller drivers from 09/14/2004, 5.0.2.8 & 09/19/2004, 5.0.2.8 to 09/14/2004, 5.0.2.8 & 03/07/2005, 5.0.2.9. -Updated: ALi/ULi M5287 SATA/RAID Controller (M1573) driver from 02/05/2005, 6.2.0.3 to 10/18/2005, 1.0.1.0. -Updated: ALi/ULi M5289 SATA/RAID Controller (M1689/M1567) driver from 11/17/2004, 5.0.2.9 to 10/18/2005, 1.0.1.0. -Updated: Promise Ultra Controllers driver from 05/16/2003, 2.0.0.43 to 06/25/2002, 2.0.0050.42. V6.02 (19 Feb 06) -Fixed: booting from Promise SATAII150 TX2plus IDE Controller. -Fixed: VIA has released a driver that works perfectly on ALL motherboards with VIA SATA controllers! No more need for the viaMraid/viaSraid work-around! -New: support for HighPoint RocketRAID 2320 PCIe SATA II Controller. -New: support for HighPoint RocketRAID 404/454 ATA RAID (HPT374) Controller. -New: support for JMicron 20360/20363 AHCI Controller. -New: work-around: 3ware 7000/8000 Series - 3ware 9000 Series. -New: work-around: HighPoint RocketRAID 154x/1640 - HighPoint RocketRaid 404. -New: work-around: Silicon Image SiI 3112/3512 - custom Silicon Image SiI 3112/3512 for ATI chipsets. -Updated: 3ware 9000 Series SATA RAID Controller driver from 11/18/2004,2.04.02.048 to 12/14/2005,3.00.01.052 [9.3.0.3] . -Updated: Intel SATA RAID controllers from 06/17/2005,5.1.0.1022 to 10/12/2005,5.5.0.1035. -Updated: Silicon Image SiI 3112/3512 SATALink Controller (and others) driver from 09/13/2005, 1.3.61.0 to 01/24/2006, 1.3.63.1. -Updated: Silicon Image SiI 3112/3512 SATARaid Controller (and others) driver from 08/27/2004, 1.7.0.51 to 01/12/2006, 1.0.56.0 (this strange update is due to that the previous driver was a custom one by ATI, which supported all controllers - the updated one only supports a select few of the ATI controllers, thus I had to make a work-around). -Updated: Silicon Image SiI 3114 SoftRaid 5 Controller driver from 03/31/2005, 1.2.3.1 to 01/12/2006, 1.4.3.0. -Updated: Silicon Image SiI 3124 SATALink Controller driver from 04/26/2005, 1.3.0.16 to 11/29/2005, 1.3.17.0. -Updated: Silicon Image SiI 3132 SoftRaid 5 Controller driver from 03/31/2005, 1.2.3.1 to 10/18/2005, 1.3.0.9. -Updated: Silicon Image SiI 3132 SATALink Controller driver from 04/25/2005, 1.0.0.9 to 01/25/2006, 1.0.14.1. -Updated: Silicon Image SiI 3132 SoftRaid 5 Controller driver from 03/31/2005, 1.2.3.1 to 01/12/2006, 1.4.3.0. -Updated: VIA RAID controllers from 04/08/2005, 5.1.2600.430 [4.30H] to 10/25/2005, 5.1.2600.520 [5.20C]. Download

BTS DriverPacks BASE V6.02.3 Changelog: V6.02.3 (19 Feb 06) -Updated: [DPB]: updated to reflect the changes in DriverPack MassStorage V6.02. Download Known issues -none

Request implemented, topic closed.

All VIA RAID problems solved in DriverPack MassStorage V6.02! Topic closed!

Problem solved in DriverPack MassStorage V6.02. Topic closed.

Topic closed until further notice: currently everything seems to be working fine.

By reading your winnt.sif file, it seems that you have used nLite AFTER the DriverPacks, and that must have been the cause. Topic closed due to inactivitity.

No feedback => topic closed. If the problem persists, please open a new topic.