Bâshrat the Sneaky

There seem to be some problems with nForce 4 motherboards. Probably a driver downgrade will fix this! (At least that's what people have reported to me!)

This is against my policy: no beta drivers!

Hmm... I'll check the .inf files then, to be sure.

99.9% sure. The other 0.1%: your .ISO got corrupted.

This is something that's on the to-do list, of course. But it's nice to see users are willing to do the effort to create their own solutions!

That's not much of a solution, is it? If you want to remove them, do it manually (NOT...) or with nLite (no problem...). P.S.: don't forget to invite me to your newly-opened bar!!! I will... I just need TIME, something I don't have at all, unfortunately...

Siginet covered it all... Use M2 and if you don't want to do it manually, use Siginet's PowerPacker.

@nite0859: hehe Call me, so I can help you

LOL Siginet was right: that's all you have to do!

I *DID* renew it, only my hosting provider screwed things up :|. I'll remember that: "Just, not too much time."!!!

@Ben.Hahlen: in which laptop is that? @tchuyev: you're the first one EVER to ask me to enable it by default! :s Why would you like it to be enabled by default?

Yes, all Geforce Go chips are supported! (In fact they were even supported sooner than the ATI Mobility Radeon series.) EDIT: Question answered, topic closed.

If they're not supported by ATI, I'm afraid it's impossible! EDIT: Question answered, topic closed.

Let WPI copy your favorites to the %UserProfile%\Favorites folder. (Or in Dutch: %UserProfile%\Favorieten). P.S.: where in Belgium do you live?

Could you please post your HWID? Check my signature for a tool to find it.

Thanks, djbe Forgot to say that

@RogueSpear: hehe @djbe: Monday I've been online for 2 hours. @Zxian: Erm? A bit slow, huh? Check uAwiki.org!

http://www.uawiki.org/doku.php?id=silent_a...s:installshield

@tchuyev: If this error message returns when you will be using the next (yet to be released) version of DriverPack MassStorage, please let me know! @ZenLord: Those problems are probably related to the nForce 4 drivers indeed. Might be fixed in the next version of DriverPack Chipset. @fatbwif: Thanks for your offer, but I've got new and more reliable hosting now! @cybpsych: Thanks! And: WTF! @AngryRaisin: ok that is noted! (PCI\VEN_1102&DEV_0008&SUBSYS_10011102&REV_00\4&2E98101C&0&08F0) @Nakatomi2010: Thanks for your testing. I'll downgrade to 6.65 for the moment then. @ZileXa: if you don't mind to do it manually, yes. But if you run the DriverPacks BASE again, it will change it automatically

@PsYhoza: please post the HWID of that problematic NIC. Secondly, try again a manual reinstall of its driver and tell me if that solved the problem. @dfndr_ov_freedom: Are you using a self-built DriverPack? Did you modify the DriverPacks BASE? Do you have spaces in your path? @homolka: that's too much work for now. It will come, but it will not come soon: I'd even tend to build the Windows XP x64 DriverPacks first. @aadosari: hmm... NONE of the DriverPacks got extracted? Or only some? @ZileXa: could you give me the exact name/product code and the HWID? Which previous versions?

You should not change the name of the I386 directory, it's hardcoded in Windows XP's setup process. It CAN'T be changed! I'd suggest you start all over, since I cannot predict the effects of the behaviour of my DriverPacks when no I386 directory was found during the slipstreaming process. (If you changed the name to AUTO after you slipstreamed my Driverpacks, there shouldn't be a problem: then you can simply change it back to "I386".)

Pressing the [G] or [R] button is really everything you have to do! As for the "ipgnd51.sys could not be found" error: please download DriverPack LAN again, probably it's been corrupted.

Erm... Are you a driver developer? I'd suggest you check MSDN's DDK KB. Topic moved to Device Drivers forum.

Hmm I don't think this is being caused by the DriverPacks: I don't alter any setup files that are protected by WFP. Probably it's because of some changes you made manually? I agree with trickytwista, try disabling WFP to get rid of that error. P.S.: don't you know WHICH files "have been replaced"?

I doubt a 'failed network boot' is related to a fake setup in any way. Yes, but would that matter? In short, this is what it does: Note: Windows 2K/XP/2K3 setup executes a setup.exe, it won't check for the integrity of it, which is why we can replace it that easily. Setup executes I386\SETUP.EX_ (or SETUP.EXE, doesn't matter), which is now a fake one. This fake setup will execute I386\presetup.cmd (Which extracts the DriverPacks to the harddisk, then alters the Device Path key in the registry and disables the Driver Signing Policy. After that, it will rename the real setup back to "setup.exe".) and then starts the real setup. That's it. You can find that in the I386\presetup.cmd file. Which DriverPack LAN version are you using? Or - if you added the driver yourself - which version of the Intel LAN driver are you using?