Bâshrat the Sneaky

Do you have OemPreinstall=Yes in your winnt.sif? This prevents the files from copying, if I remember well. P.S.: which driver is this? You could try my DriverPack MassStorage.

Try another version of nLite that does not cause this problem.

Find the product name/type of your Toshiba laptop and then google for it. You'll have the answers you need in a second!

Create an MSI setup that executes WatchDriverSigingPolicy.exe (or a self-made AutoIt compiled script). For as long as WatchDriverSigningPolicy.exe is active, you will be able to install any driver!

Check the sticky! (Section #1.) Topic closed!

You included BOTH the hotfix (KB888111 indeed) AND the Realtek audio driver in your UWXPCD?

Temporarily disable the Driver Signing Policy!

Check the sticky! (Check point #2.) Topic closed.

I think I'd agree with this. Similar problems have been reported to me regarding chipset drivers. Anyone else here having issues with that, on particular on nForce 3 and nForce 4 motherboards? Possibly (probably) also ethernet driver problems? If so, please don't hesitate to post that in the device drivers forum!

Yes indeed djbe.... I've told you this before, cybpsych!

I think you didn't quite understand me... In a nVidia nForce driver, you can find these folders: -AudioDrv => DP S A -AudioUtl => accompanies AudioDrv in DP S A (CPL) -Ethernet => DP L -IDE => DP M -SMBus => DP C That means, the only files that you can find in DP C (DriverPack Chipset), are originated from the SMBus folder (since all other drivers belong in another DriverPack). Go ahead and download the 6.53 driver AND the 7.13 (yes, Intel Edition!) driver. You'll see they are IDENTICAL when it comes to the files of the SMBus folder. That means... the cause has to lie elsewhere, in one of the other drivers! I suppose MassStorage (since that's the most 'critical' driver?). Could you please try that?

Doesn't matter

As long as the old disk is not using an older mass storage driverpack. You may be able to get away with it. If new Sound or video ControlPanels have been added you will not have those either. Basically just replace the newer DPs in the OEM directory and try it. It may work fine. ← Correct! @ZileXa: sorry, lots of work yesterday (and the rest of this week ), read too fast!

Search...

DriverPacks BASE V5.10.1 has been released yesterday.

@all_those_who_are_saying_reverting_to_6.65_solves_the_problem: impossible... the CHIPSET drivers are IDENTICAL to the 6.53 drivers, that have been released in MARCH this year! (That are these drivers: smbus, nf4pcie, nf4sys, the other ones are ethernet + audio drivers....)

@Nakatomi2010 & ZileXa & Powerhouse: neither of these problems CAN be caused by the DriverPacks. NO changes have been made to the V5.10 series, only the URI's have been updated. All those problems MUST have a cause outside of the DriverPacks! @Muiz: I know... Someone else reported that too. Ignore that, it's an entry I forgo to update.

@eddy_71: did the other drivers install? Did you slipstream the latest updates? Which language is your Windows XP? Since I figured out that the nVidia nForce drivers haven't changed a BIT since the 6.53 version: nor the 6.66, nor the 7.13 Intel Edition brought any changes! That means the problem must lie elsewhere. I've spend more than an hour comparing all nVidia nForce drivers tonight, resultating in the above conclusion.

Erm... That is what *I* will do, the porting to C. And... OS-independent updater? More details?

Eh......? Manually as in WITHOUT the DriverPacks? Check the Device Drivers forum 'Read this first' sticky. Or as in 'build your own DriverPack'? There's already a tutorial covering that, at uAwiki.org.

Basic (working, but older) IBM Thinkpad drivers are included in Windows XP by default, if I'm not mistaken. Therefor, they are NOT included in the DriverPacks (except for the Sound drivers). My guess is that you should NOT remove all drivers, and certainly not the ones that are labeled 'IBM Thinkpad' in nLite! EDIT: doh... Read it too fast... Hmmm............. nForce 4 chipset drivers must be the cause. Which versions of the DriverPacks BASE, DriverPack Chipset and DriverPack MassStorage are you using? EDIT: Oh yes, and which method did you use? Method 2, any chance?

oldskool & minimalistic TOO oldskool, NOT minimalistic ENOUGH

Impossible. There is no environment loaded at the PRESETUP (hence the word) stage. All executables/commands you use have to be stand-alone. To ensure this is the cause of your problem: add the following commands to your presetup.cmd: CMD.EXE /C PAUSE This allows you to test which commands work.

V5.07, V5.08 was never released and will be skipped. V5.10 will be released with MORE updates. Fixed.

I entered a wrong subversion . Auto-update is working again now...