Lucius Snow

@ Thauzar : I get your ideas about Appz . Sure that'd be great and that'd not be that complicated to create it from the current model for \Driverz. About the 7zip compression, i just followed Bâshrat the Sneaky's guide in his drivers pack. That was the settings of the screenshot. Anyway it works very well, never got any error when unpacking the drivers and the ratio compression is amazing ! Much powerful than RAR, ACE, ZIP or whatever ...

Cheers. Let us know how it goes.

Alright, here is my full method : 1/ First, i've followed serialzs' guide : EXCEPT for that : I kept this line.So i put my 7zip files in X:\$OEM$\Driverz (X: = you CD ROM letter drive). By the way you have to keep that exact structure otherwise it doesn't work (so forget this method for multiboot). Then the drivers got extracted into C:\Driverz (thanks to drvz.exe running before the drivers installation step of XP install). Since serialzs' method never worked here for installing automaticaly the drivers during the install, i decided to keep using the traditionnal method with OemPNPDriversPath (that's why i still use its command line in winnt.sif). Drvz.exe creates a subfolder in C:\Driverz named by the 7zip file archive. For example, if in \$OEM$\Driverz you have SND.7z, then you'll get C:\Driverz\SND created. So when you create your 7z archives, don't compress the folder SND for example otherwise you'll get C:\Driverz\SND\SND. Instead, just select in 7zip software all the subfolders and then create your archive with the name SND.7z. See the captures below. So now, the last step is to enter the paths in OemPNPDriversPath. Still with the SND example, that'll be that : I tested this method on 3 PC yersterday, it worked great on all of them. By the way, i didn't get prompted for the WHQL alert. It ignored them. Inconvenient : i still have to use the OemPNPDriversPath method Advantage : great gain of space by compressing the drivers in 7zip format.

It doesn't work here either. @ Aaron : the only difference i see with my winnt.sif seems to be UnattendSwitch=Yes. On 'Yes', it skips the oobe so the 'Help protect' page won't appear anyway.

That's what i finally did. I let drvz.exe decompressing the files in C:\Driverz and added manually all the paths in OemPNPDriverPath.

@ Bâshrat the Sneaky ... Tonight i've installed a PC using an unattended CD with your sound pack. The soundcard (a Soundmax onboard an Asus P4PE) got installed like a Realtek . Strangely, the device manager didn't show any error with it but there was no sound at all. Do you know what the problem could be ? Cheers.

Hello all, Does anybody know how to manage the associations files with K-lite ? I'd like to unregister the MPEG files with Media player classic. Thank you.

Same problem. No solution yet.

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\DriverSearching] "DontSearchWindowsUpdate"=dword:00000001 "DontPromptForWindowsUpdate"=dword:00000001

Yep. And i'm sure it won't be that complicated to make. However, it should be good to specify the search into \Driverz only because the update process takes a long time.

Cheers crahak. Well if it's not possible (unless writing an app - and i'm not a developper lol), i'll just keep both process then

Any news about that issue ? I still get the prompt during the installation process.

Hello all, During the autorun process, two things occur : a window opens to ask an action (browse, play etc.) and another one is searching on the drive ("automatic execution") something to run. Is it possible to keep the first process and disable the second one ? Thank you.

A new try in a real installation confirmed this. @ serialzs : would you agree to publish the code source of your drvz.exe ? Some developpers here may be able to help you to find out the last problem concerning the installation drivers step.

Just did a new try ... Non-multiboot CD this time / simulation with VMware. Driverz got extracted with the \$OEM$\Driverz structure but the drivers didn't get installed. Like Keul, if i try to install them after the installation by clicking on Update, Windows find them and install them alone.

Some encouraging news : I finally managed to get the drivers unpacked to C:\Driverz by doing a test after the installation. I ran drvz.exe after simulating a CD respecting the structure \$OEM$\Driverz. My multiboot structure doesn't work though.

I followed exactly the instructions so i don't understand what the problem is. @ serialzs : Thanks to your new file, i got the following messages : 1 CD ROM drive No files / directories matched the search pattern My files are in H:\Setup\XP\Professional\$OEM$\Driverz and compressed with 7zip using the settings that Bâshrat the Sneaky put in his documentations.

Hence the point of this driver pack... Sure but when this pack doesn't support your RAID controller, how can you do without F6 ?

Thanks ! What's new in this file ?

Can you please post your winnt.sif and txtsetup.sif ? Did you use .7z or .cab archives in Driverz ? By the way, must these archives contain a specific directory ?

@ Bâshrat the Sneaky : Any progression in the work of the next version ? A release soon ? Thanks.

So we can use presetup.cmd to decompress files when the setup starts and keep the OemPNPDriverPath path anyhow ? @ serialzs : Is it possible you publish the code source of your drvz.exe ? Maybe the developers who are hanging around here may be able to find what is going wrong.

I never could use the F6 method in a unattended CD. The files couldn't get copied from the floppy

Has anybody got any success with the new DRVZ.EXE ?

Yes, i did. However i'm using a multiboot CD so the structure is not exactly the same. Like i explained, here is how i proceed : My directory is like this : BOOT1 = regular BOOT2 = unattended So ... 1/ I edited the TXTSETUP.SIF in \BOOT2 (and not the one in \Setup\XP\Professional\I386). 2/ I edited the WINNT.SIF in \BOOT2 (it can only be right since there's no else winnt.sif) 3/ The 3 files were copied to \Setup\XP\Professional\I386 (and not in \BOOT2). I also tried in both \I386 and \BOOT2. Last notice : the 3 files get expanded and copied properly to C:\Windows\System32. But no Driverz folder created. If i run drvz.exe after the installation with the CD ROM still inserted, \Driverz doesn't get created either.