Bâshrat the Sneaky

Hi patwa, next time please attach a file instead of completely posting it! You can find links to some nice tutorials in the sticky, in section #1. Topic closed.

Method 1 requires OemPreInstall in your winnt.sif to be set to "Yes". If you modify your winnt.sif afterwards, I can't do anything about that. About the problem with method 2: did you already try disabling your 8 in 1 card reader? You really are the first and only one with this problem, so probably that's the cause.

Erm.... Please attach/send your Methods_V5101.7z!

Nice I also use this one and would recommend it to everyone: it's fast, stable and easy in use!

Errr? When you can select a partition, setup DID find the HDD connected to the SATA controller? That SATA controller is NOT recognised when you use a Windows XP CD with no slipstreamed drivers? And AFTER Windows XP has been installed, the driver is NOT installed?

What is the command line you are using? EDIT: Temporarily disabling the Driver Signing Policy isn't a possibility?

Hm.... After reading your quite complete overview of what's wrong and the process you've gone through, I think the only conclusion can be (especially considering the error "...have been replaced by unrecognised version...") that nLite slipstreams the newer drivers, replacing the original, older ones. The easiest way to prevent that, is using the OemPnPDriversPath method for your drivers. That way Windows won't complain - 100% sure. Check the sticky, section #2.

Odd... Could you please tell me WHICH WatchDriverSigningPolicy.exe you're using? (Where did you get it?)

Hmm... I suppose you have 2 possibilities for a correct installation: 1. slipstream the KB888111 driver + install the driver any way you like (slipstream, OemPnPDriversPath, Pyron's method, KtD method) 2. do everything manually: install the KB88811 driver manually + install the driver manually (And if 2. doesn't work, 1. sure does!)

That is EXACTLY what it's supposed to do. The question is: did you enter your OemPnPDriversPath correctly? Do you actually HAVE the folders you referenced there?

Actually the problems I've encountered ARE caused by the DriverPacks. Here is how I tested. Used a New WindowsXP CD with Integrated Service Pack 2. Ran the latest packs (v5.10.1base, and all the latest packs). Installed this new CD on 4 different machines (two Intel - 955 and an older 875p ) and (two nVidia - Abit NF2 and Asus NF3), using both Method 1 and Method 2. On all 8 tests, all 4 using the NForce chipsets encountered the problems I've described. So it appears whatever drivers and/or changes you've made to the nForce drivers from the 5.07 builds to new v5.10.1 is what is causing the problems. As I said before, there are no changes to the DriverPacks BASE, except for the URI's. Do you use RyanVM's UpdatePacks? P.S.: on my ASUS A7N8X-E Deluxe the nForce 2 chipset drivers installed without a hitch. But I admit, that was with DPs BASE V5.08.1 - though there is virtually no difference between V5.08.1 and V5.10.1, as I've already said numerous times.

Thanks Siginet & Prathapml for notifying me! But 'a star'... dunno P.S.: Prathapml: I'd still like to see those pics/scans!

I would appreciate that a lot! Thanks! I wouldn't mind seeing those scans/pics either...

Use the Get_hwids.exe file you can find in my signature to determine what HWID your IRDA device has. Then google for that HWID and probably you'll find the driver you need.

That 'XPCD folder' can be named ANYTHING, like: UWXPCD, UAXPCD, WXPCD, XPDVD, anything you like....

I assume you're using the latest version of the DriverPacks BASE. Probably the cause is that you have spaces in your path to the DPs BASE!

Which version of the DPs BASE are you using? Older ones don't run WatchDriverSigningPolicy.exe, which may be the cause of this problem.

1. That's a possibility, yes. 2. Go beg at Microsoft, it's their policy. (In fact the reason is to reduce the numer of system failures due to faulty drivers.) 3. nLite is the easiest method. You could also do it manually. BTW, I had NO idea the FX series weren't WHQL'd in the 78.01 driver? :s What's that for nonsense! nVidia is NOT on the right track when it comes to drivers!

Not truly a 'bug', but... If you want to move a topic and you move it to the same forum as the original one, you get a flat ERROR instead of a message. Wasn't that different before?

That was already (obviously) on the TODO list!

Only these SiS and VIA chipset drivers or also others? At what stage of setup?

Then are you using the latest Realtek drivers? THE CORRECT drivers? (NOT the AC'97 drivers...)

The reason of this post? This information can be found in section #1 of the sticky. Topic closed.

This .exe has to be running DURING driver installation, that must be the reason why it doesn't work for you!

This means you didn't understand what Siginet said. Siginet suggested you could build a MULTIBOOT CD/DVD, from which you can select any 'setup' you've put on it...