Bâshrat the Sneaky

Request implemented, topic closed.

Topic closed.

Well, it seems you'd like it very much if this problem could be solved. I hope you'd like to see getting it fixed so much, that you would be willing to do a test for me? Could you please do another installation with your UWXPCD, but with ONE significant modification: delete the part of $OEM$\D\BTS_DPs_finish.cmd that installs the control panels of the X-Fi and Audigy devices. After you've finished your installation, please check which drivers are installed. And more specificly, whether these files exist: -%SYSTEMROOT%\system32\drivers\ha10kx2k.sys -%SYSTEMROOT%\system32\drivers\ha20kx2k.sys P.S.: there are MORE conditions than only the checks for the .ini files, those checks only exist to detect whether the control panel is available or not (you could have deleted them (and thus have created a custom DriverPack)).

@Fencer128: Those INI copying statements were already removed in V6.03.3. I've fixed those paths now, though. As for that annoying default sound scheme that isn't working: I suspect that it's some registry setting. Could you please use RegShot (freeware) to find the changes made by the installer? @cjei: Ok, thank you, fixed that!

Could you please try this slipstreamer batch file? I made a very small change, but it might solve the problem. It's a 100% pure guess, though; it's not based on any fact... (But I also don't understand why Microsoft made her already-not-so-great command line even suckier, by allowing such an annoying, ridiculous bug...) BTS_DPs_Slipstreamer_V6033.cmd

It's safer to apply XPize before the DriverPacks. I don't know what the XPize slipstreamer exactly changes, so my guess is currently that something went wrong there.

@discountpc: I hadn't changed a thing to solve it... since there was no bug UPDATE: perhaps that was the endless loop bug I also mentioned in my reply to Vagabond8 below? That statement were already at the beginning of the file, and that '@echo off' is unnecessary, since the window is hidden anyway @Vagabond8: are you using an older DriverPacks BASE, perhaps? There was an endless loop bug in the finishing script...

Erm?! How could I ever have missed that??? Fixed version online tonight... UPDATE: Fixed version online (a while ago). Topic closed.

I knew it... Good luck recovering your data

Of course. And AFAIK, nothing special is needed (except for maybe special MCE graphics drivers?).

I had a feeling this would be the case. Anyhow, let me try and explain: Under: DriverPack Graphics C Current version: V6.03 Archive size: 34.05 MB Decompressed size: 118.91 MB Click on ---> Supported devices & changelog of DriverPack Graphics C. Once on that page, go to 'File --> Save As' and click on it. A 'Save Web Page' window will open up where in the default 'File name' already filled out will be 'Bâshrat the Sneaky's DriverPack Graphics B', whereas it should be 'Bâshrat the Sneaky's DriverPack Graphics C'. By the way, this is only a problem in the case of 'DriverPack Graphics C', in the case of all the other packs the file name by default shows correctly. Ahhhh! Now I see it! It has the wrong title. I'll change that in the next update

@Toolman: then it's probably being caused by overclocked RAM or a corrupt HDD, since you're the first to complaint Every time it has happened, it was such an error. @Fencer128: ah! I did not know that. I'll change that in the next update.

CRC errors??? :s May I ask how long that NTFS compression takes?

Maybe not so fast... but I haven't forgotten about this topic! Tomorrow I'll make a decent batch file that fixes this problem, but here's some demonstrational code: set t=%SystemDrive%\tmp.txt devcon find pci* >> %t% agrep -ci "SAPPHIRE" %t% if %errorlevel% GEQ 1 echo MATCH This lets devcon output all hwids that start with 'pci' to the file %SystemDRive%\tmp.txt. Then a case insensitive search is done for the string 'SAPPHIRE' (as in the brand Sapphire (my GPU is built by them)) and if one or more matches are found, the string 'MATCH' will be echoed. With this 'technique', any solution is possible. Off to bed now

It would be smarter to first extend your system's "true RAM" to its maximum first: it's ALOT faster than the i-RAM, which is limited to the PCI bus' speed. i.e.: it's better to have 2GB of system RAM than 1GB of system RAM + 1 GB of i-RAM-RAM: then you've got 2 'fast GigaBytes' instead of 1 fast and 1 slow.

DriverPack WLAN V6.03 Changelog: V6.03 (17 Mar 06) -New: added 1 Broadcom WLAN (generic) driver. -New: added 1 Broadcom WLAN Dell driver. -New: support for AVM FRITZ! WLAN USB Stick. -New: support for ALL LANCOM WLAN controllers. -New: support for ALL X-Micro WLAN controllers. Download

DriverPack LAN V6.03.1 Changelog: V6.03.1 (18 Mar 06) -New: support for nVidia nForce Professional Ethernet -Updated: Intel 10 Mb, 100 Mb / 1 Gb / 10 Gb drivers from 06/13/2005,8.0.21.0 & 09/14/2005,9.2.24.0 & 06/22/2005,2.1.11.0 [10.2] to 01/12/2005,8.0.27.0 & 01/23/2006,9.3.28.0 & 01/04/2006,2.1.11.0 [10.3]. Download

DriverPack Chipset V6.03.1 Changelog: V6.03.1 (18 Mar 06) -New: support for nVidia nForce Professional chipsets. Download

BTS DriverPacks BASE V6.03.3 Changelog: V6.03.3 (18 Feb 06) -No changes. Maintenance update. Download Known issues -none

Request implemented (in both DriverPack Chipset and LAN). Topic closed.

Already supported Look in D\L\NV\4x0. EDIT: Topic closed.

The rest aren't "signed" drivers, so its bad for uA CDs.Looks like i wont be using it just yet - i'll wait out the 2 weeks that it takes, for them to release a fully-WHQL driver for all cards. Thanks for posting that remark: I had not yet noticed it! I checked it and it's true: only NV40 and higher GPU's have a WHQL signed driver. Let's hope nVidia releases a truly WHQL signed driver soon! EDIT: Topic closed.

Could you please post a screenshot of your device manager OR use the tool in my sig and then post the generated hwids.txt?

Moved to Unattended Windows.

Sorry, fixed, it should have been labeled REQ and not yet solved