Bâshrat the Sneaky

Sorry for the EXTREMELY late reply, but I just haven't noticed it It's IMPOSSIBLE that the driver loads a random rt2500.sys! It loads the one in the same folder.... Please find YOUR driver's .inf file and compare it with the one that works for you. In particular, compare the HardwareIDs! EDIT: topic closed.

Nope, not yet I will add support for those in V5.04

It's certainly possible, and I might do that in the (VERY NEAR) future, but make sure to avoid overwriting files!. I think that will be for all DriverPacks V5.04. But on the other side... it will be VERY difficult for you guys to remove one driver out of the DriverPacks... Or to track this one file... On my side of the story, it will be more difficult, but not really hard; I can automate that.

@Ghostrider: thanks to share your experiences It might be useful info somewhere in the future @RogueSpear: well... you're not the first to think of that... RyanVM and I did the same, you can find it somewhere in Pyron's 'SOLVED: Driver from CD' topic. And I've got an additional question for you: how many drivers are you decompressing? ALL of my DriverPacks? The reason why I didn't add this method is simple: we thought that - certainly on a slower machine - the archives wouldn't be decompressed fast enough, so Windows wouldn't be able to search through ALL driver(pack)s, but just the part that has been decompressed at that time... What are you're experiences with that?

1) This is when you use ANY DP that has a separate batch file to install control panels. As MCT already said, it's used to hide a cmd window, which is what I'm doing with those batch files. 2) Indeed the files are compressed since DP BASE V5.02, to save space on your disc!

Ehm... I'm using a newer version of setup.exe, posted by iLE in Pyron's topic. That version has the 'Pre Setup Information Window', some have asked to remove this window, so I contacted iLE and he has written a new version of his setup.exe for me. THAT is the version I use... Indeed it isn't listed in Pyron's guide, but you DO need it if you are starting setup through winnt32.exe (if I remember well). And unfortunately my exams are coming up (next week), so I don't have the time to do some extensive testing ATM...

hmm... just maybe... the cause could be the dosnet.inf file. Please try the PRO2 installation WITHOUT the dosnet.inf file and tell me what happens! (you can use VMware/VirtualPC for this test)

@Salvo2002: no need to double-post!!! Please let this be the last time.

Try the tutorial!

If you compress them, you'd have to change the value of them in the txtsetup.sif file. But I don't know by heart what value that should be...

What language of Windows XP are you using? The same problem has been reported for French and German Windows XP editions...

Probably your OemPnPDriversPath is too long Use D instead of Drivers and 006 instead of 006_Storage, and so on... The maximum is 4096 characters for Windows XP

@S0mE0nesMiNd1: many people are having problems with this. @rcordorica: well... at first I was planning to use the txtsetup.oem method, but then I decided not too: cfeedback's post confirmed that it works like this too! And by the way... I DID use this method for the 3ware drivers, but it kept giving a 'error 18 on line...', you know that one... I guess I should look how nLite does it and try that method too... If that won't work, I'll use the txtsetup.oem method again.

Huh? This has been an error in the past (some versions of V5.02), but I solved it back then... I'll fix it asap. And about those files in the I386_original folder: they're the original files that ship with the Windows XP disc, in case someone decides to stop using DP MassStorage, the batch files will automatically put these original files back!

... which would be logical: the end-user should not notice any difference between Windows XP 32 and 64 bit... At least that's what I think.

BTS DriverPacks BASE V5.04.14 Download Please post your DriverPacks BASE V5.04 series related questions/problems/remarks in THIS TOPIC!

DriverPack Sound B V5.04.3 Download

DriverPack Graphics B V5.05 Download

Yes, I saw it, but I think it's better that you've reposted it. The portcls.sys error => with which motherboard/soundcard?

I suppose you're asking how you can use my DriverPack in a regular Windows XP environment, so using my DriverPacks FROM Windows XP? Well, then you have to change the DevicePath... Download SetDevicePath.exe from here And run it like this: SetDevicePath.exe %SystemDrive%\DP (assuming you're using my DriverPacks) You can run this from GUIRunOnce, or RunOnceEx, or just from Windows itself... OR if you're using method 2 (Pyron's method), you can remove the DevicePath reset from the presetup.cmd file.

It doesn't matter...

The nVidia works for me. But do you remember that version where the SiI3114r DID work?

Huh? You too? WTF is this... This problem has been fixed a long time ago: the aliide.sy_ file was REALLY missing in the I386 folder, but as you say, the file IS in the I386 directory... Please try removing its entry from the txtsetup.sif file and post the result then.

DriverPack WLAN V5.07 Supported devices. Changelog: V5.07 (25 July 05) -New: support for Atheros WLAN controllers in IBM systems. -New: support for Belkin F5D7000_ver3 WLAN controller. -New: support for Belkin F5D7050_ver2 WLAN controller. -New: support for D-Link DWL-G510 revision B WLAN controller. -New: support for Linksys WPC54GX WLAN controller. -New: support for Netgear WG311v3 802.11g WLAN controller. -New: support for SMC SMC2862W-G v2 WLAN controller. -Improved: the Airlink101 AWLH3025 802.11g Wireless PCI Adapter & AWLC3025 802.11g Wireless Cardbus Adapter driver, the SAFECOM SWLC-54108, SWLP-54108 driver and the Surecom EP-9321-g(A2) & EP-9428-g(A2) were identical. The first two were equal in version number, the third one was older. Only the first one was kept. -Improved: too many things to say... for details, check the DriverPack WLAN V5.04.4 thread. mark49 has pointed to many duplicate files. (And what a miserable job that was!) -Updated: Atheros HP from 04/05/2004,3.1.1.50 to 12/27/2004,4.0.0.140. -Updated: Buffalo WLI-CB-G54 driver fom 07/17/2003, 3.30.15.1 to 04/20/2004, 3.60.7.3. -Updated: Intel 2100, 2100A driver from 07/28/2004,1.2.3.14 [7.1.3.0] to 02/28/2005,1.2.4.35 [7.1.4.0]. -Updated: Intel 2200BG; 2915ABG driver from 10/29/2004,9.0.1.9 [9.0.1.9] to 04/29/2005,9.0.2.25 [9.0.2.0]. -Updated: Linksys WMP54G v4 driver from 03/27/2004, 2.02.03.0000 to 07/29/2004, 2.02.07.0000. -Updated: Linksys WMP54GS driver from 02/19/2004, 3.50.21.11 to 12/22/2004, 3.100.46.0. -Updated: Netgear WG111T driver from 10/04/2004,1.00.001 to 12/05/2003,1.00.001 & 01/07/2005,1.0.1.1007. -Updated: SiS 162 driver from 09/14/2004,5.1.1039.1040 to 10/26/2004,5.1.1039.1050. -Updated: SiS 163 driver from 10/18/2004,5.1.1039.1010 to 02/24/2005,5.1.1039.1030. -Removed: Buffalo WLI-PCM-L11GP driver, support is already included in the Agere WLAN controllers driver. Download

Please post here your problems/questions related to DriverPack Sound B V5.03!