Bâshrat the Sneaky

Of course you can delete them. If you want to know more about method 2 (Pyron's method), there's an extensive tutorial available. P.S.: please don't bump a very old topic next time

It will be possible in the future, but it must be automated: to do this manually is a true titan's work. I doubt anybody is stupid enough to start such a thing. And then I've not even said anything about keeping it up to date... This will be an option in the C++ version of the DriverPacks BASE, but it won't be for soon. P.S.: why 7zip instead of CAB isn't possible: Windows has built-in support for reading CABbed files. And AFAIK it's virtually impossible to hack Windows XP so that it has also built-in 7zip support... UPDATE: added to Things NOT to ask...

1. Make sure to keep a back-up, just in case! 2. You can leave EVERYTHING, the new DriverPacks BASE will automatically detect files and changes from an old slipstream, then it will delete them (or restore the original files) and slipstream the new DriverPacks. There's only one caveat: if you have used nLite AFTER the DriverPacks, or if you have made any changes to the dosnet.inf, txtsetup.sif or winnt.sif files, they will be lost!

Since you don't seem to receive any more errors, I suppose you have forgotten to replace the real setup with a fake one (which is how method 2 works). My suggestion: run the slipstreamer and choose method 2. Then copy the files to the root of your XPPROF share and execute RUN_ME.CMD. After that has finished, copy the same files again, but now to the root of your XPHOME share. It should work alot faster AND it should be more reliable!

It should NEVER take 3-4 hours to decompress all DriverPacks. Maybe on a 300MHz pc with an extremely slow HDD. Ow... now I notice you're saying you're using method 1. Then there's no decompression involved, only copying. Are you sure you've configured everything correctly? Are you sure the entire DVD doesn't get copied? 3-4 hours is far from normal... As for that audio device that didn't get installed: please post your HWIDs

I had noticed those dates myself, but didn't know that that link was broken. Thanks

Indeed, I finally got one and it seemed to be one for an ATI Mobility 9000 (that's an M9 GPU). No go, that is. I'll await your download link then

Getting that driver... praise Panasonic for great download speed! I also downloaded all ESS audio drivers, expect an updated DriverPack Sound B in the middle of this week.

Not in my power to solve this problem... I'm sorry! Please contact nVidia to get this issue solved.

Problems fixed. The directory structures of DriverPack Graphics B and C were also messed up... (only for the ATI drivers).

@midiboy: as soon as nVidia releases a new official WHQL driver (that will probably support this GPU), I will include it immediately, as always. I will not include a beta driver, for obvious reasons

Seems to be solved now. I never got a reply from DreamHost, though :| Topic closed.

@nerd-light: Maybe you had the files opened in a text editor? @laura: You're very right. Applied both your suggestions.

Request implemented, topic closed.

This issue was solved in DriverPack MassStorage V6.02. Topic closed.

Apparently the problem is related to the graphics driver. But what I don't understand is why after once booting up in Safe mode the same driver works fine. Also a friend of mine, who used an unattended cd downloaded from the net, had the same problem and he said that it is related to the geForce 6200 graphics card. Since he has the same card that I have it might just be the case. But even then what is still not understandable is why the same driver works fine after once booting up in Safe mode. To us this seems to be very very awkward, but after you've worked frequently with Windows setup for one year or more, you'll have learned to accept these odd errors and sometimes even more odd fixes or work-arounds I suppose your problem is 'solved' now? Beside the fact that you need an additional reboot in order to get things working as they should have after the first reboot...

Request implemented, topic closed.

It will work smoothly, on condition the paths are updated correctly in the winnt.sif file under the OemPnPDriversPath entry. There are two big 'but's: 1. Many control panels will not get installed. 2. MassStorage drivers will not be available during textmode setup!

Do you have the .NET Framework installed before BTS_DPs_finish.cmd executes?

See Things NOT to ask... Question answered, topic closed.

A support request has been sent. Now it's waiting for their reply/fix...

Enlightening One () Instead of deleting drivers, I could just delete the DevicePath entry in the registry for the drivers 'which should get deleted'.

I know

I mean deleting drivers from the HDD after they got extracted from the CD/DVD...

Did VMWare select the wrong driver then?