serialzs Posted September 3, 2004 Author Share Posted September 3, 2004 @turbomcpin your 7zip application folder...try to RUN this file then compress your drivers... its like a WINZIP windowit is the main window of 7ZIP Application... 7zFMn.exe-=[serialzs]=- Link to comment Share on other sites More sharing options...
CrashUK Posted September 3, 2004 Share Posted September 3, 2004 @Lucius SnowNO...$OEM$\$1\Driverz is for copying file to %systemdrive%\DRIVERZ without extracting it...$OEM$\Driverz is for my program that will extract compressed driversin %systemdrive%\DRIVERZ with the subdirectory...So which one will work.. or which is best or fastest Which one should I use?? I tryed $OEM$\Driverzwhen windows is install you get them black windows and you see it unpacking the drivers..If I use the $OEM$\$1\Driverz will it still install my drivers. Link to comment Share on other sites More sharing options...
serialzs Posted September 3, 2004 Author Share Posted September 3, 2004 @CrashUKUse $OEM$\Driverz...-=[serialzs]=- Link to comment Share on other sites More sharing options...
CrashUK Posted September 3, 2004 Share Posted September 3, 2004 @CrashUKUse $OEM$\Driverz...-=[serialzs]=-Also can you tell the commands to move the c:\driverz\ to c:\windows\driverszOnce Windows has been installedmaybe rename it to DriverPack..I know how to copy them but not how to move them.. I what to use move down to it being a lot faster.. Link to comment Share on other sites More sharing options...
CrashUK Posted September 3, 2004 Share Posted September 3, 2004 @CrashUKUse $OEM$\Driverz...-=[serialzs]=-Try that windows unpacks the drivers but does not install them.. ??? anyone know why.. I am using your new version.. Link to comment Share on other sites More sharing options...
turbomcp Posted September 4, 2004 Share Posted September 4, 2004 i dont get itdidnt we conclude this issueby saying windows doent look in the registry(atleast not in that location)after gui starts only before that?we tried entering the same info before gui starts and everything workssohow can this thing work?(i wish it would but how) Link to comment Share on other sites More sharing options...
Thauzar Posted September 4, 2004 Share Posted September 4, 2004 If it only extracts them but windows does not see them, why not put the program under unattended and not GUIunattended so it starts before the gui? could this work or is the drivers not going to be uncompressed on the c: drive after that? We could also do 2 operations, one before gui starts with uncompressed drivers so windows sees them during install and another one during gui mode simply to get the files copied on the drive and extracted on the C: some people could even use this step to rename their driver files to DriverPack or copy them to c:\windows\DriverPack if they want to...ORI don't understant what file does what here, but if the files could simply get uncompressed, if we manually added them to OemPNPDriverPath or whatever the name and still save the MB. The only thing I don't know is how to uncompress them. Link to comment Share on other sites More sharing options...
Lucius Snow Posted September 4, 2004 Share Posted September 4, 2004 That's what i finally did. I let drvz.exe decompressing the files in C:\Driverz and added manually all the paths in OemPNPDriverPath. Link to comment Share on other sites More sharing options...
Thauzar Posted September 4, 2004 Share Posted September 4, 2004 Ok so that operation is done before OemPNPDriversPath considers the updated files? That would be perfect. I would get the extracted 7zip files and windows would still consider them when he installs driver. Did you do something specific to make it work or simply followed the instructions like everyone else but added the OemPNPDriversPath back to winnt.sif? Link to comment Share on other sites More sharing options...
Lucius Snow Posted September 4, 2004 Share Posted September 4, 2004 Ok so that operation is done before OemPNPDriversPath considers the updated files? That would be perfect. I would get the extracted 7zip files and windows would still consider them when he installs driver. Did you do something specific to make it work or simply followed the instructions like everyone else but added the OemPNPDriversPath back to winnt.sif?Alright, here is my full method :1/ First, i've followed serialzs' guide :1. Compress all your drivers *.CAB files or *.7z files(eg. VIDEO.CAB or SOUND.7Z means drivers for your components)note: NO SAME NAME!!! it only overwrite the files if it already exist... 2. Put the Compressed Driver FILES inside the directory named ->$OEM$/DriverzExample:your CDROM letter is D:\ it must be like this D:/$OEM$/Driverz Note: it's (Z) not (S) 3. Put the 3 files inside i386 folder then edit TXTSETUP.SIFIn TXTSETUP.SIF find [sourceDisksFiles]then add this 3 lines... 7za.exe = 1,,,,,,,2,0,0Drvz.exe = 1,,,,,,,2,0,0DevPath.exe = 1,,,,,,,2,0,0 4. Edit Winnt.SIF [unattended]DELETE => OemPnPDriversPath= (it is not needed anymore)ADD => DriverSigningPolicy=IgnoreADD => NonDriverSigningPolicy=Ignore [GuiUnattended]DetachedProgram="%SystemRoot%\system32\DRVZ.EXE"EXCEPT for that :DELETE => OemPnPDriversPath= (it is not needed anymore)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 :OemPnPDriversPath="Driverz\SND\A;Driverz\SND\C;Driverz\SND\CR;Driverz\SND\CR\L;Driverz\SND\N;Driverz\SND\R;Driverz\SND\S;Driverz\SND\T\A;Driverz\SND\T\D;Driverz\SND\V\E;Driverz\SND\V\V"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. Link to comment Share on other sites More sharing options...
Thauzar Posted September 4, 2004 Share Posted September 4, 2004 GREAT JOB LUCIUS!!! gonna test it right now and post back in a day since I'll also try the nLite 98.8 tu get rid of a SCSI error while installing Daemon Tools. But I don't want to use his included driver integration cause it's a new feature and maybe still have bugs.I keep fingers crossed but I'm confident it'll work perfectly Link to comment Share on other sites More sharing options...
Lucius Snow Posted September 4, 2004 Share Posted September 4, 2004 GREAT JOB LUCIUS!!! gonna test it right now and post back in a day since I'll also try the nLite 98.8 tu get rid of a SCSI error while installing Daemon Tools. But I don't want to use his included driver integration cause it's a new feature and maybe still have bugs.I keep fingers crossed but I'm confident it'll work perfectly Cheers. Let us know how it goes. Link to comment Share on other sites More sharing options...
Thauzar Posted September 4, 2004 Share Posted September 4, 2004 Just wondering, would there be a way to also compress the $OEM$\$1\Install\Applications\ folder so all our apps would take less place on the cd but could still be ran afterward using normal batch files in the last [] section of winnt.sif (I got a very bad memory for names) but you get my point I guess... The only thing to change would be the Driverz folder, lets call it Appz Link to comment Share on other sites More sharing options...
Thauzar Posted September 4, 2004 Share Posted September 4, 2004 I also noticed you put the dictionnary size to 48 while default is 32 with ultra compression and you maxed the word size to 255... why? (just being curious here, nothing important) Link to comment Share on other sites More sharing options...
idle.newbie Posted September 4, 2004 Share Posted September 4, 2004 i saw many ppl extract 7zip sfx with /Q /R:N, there's no such a argument for 7zip sfx, verify with any 7zip console sfx with any7zsfx.exe -?.@serialzsHow you test your drvz? VPC? VMWare? or real box?Pyron's setDevicePath.exe works great on his guide, but it's different @T-39. The setup program didn't refer to HKLM\....\DevicePath, i don't know why, it's been confirmed about 2 weeks ago with my friend's script here - MT39 thread.Testing on VMware with VMWare's video driver, almost the same as turbomcp's post.The Detached.cmd script comes from zippy, it's a script version of setDevicePath.exe. It extracts drivers & $OEM$\$$ & $1 sfx, modifies the regTweak and $winnt$.inf(compiled from winnt.sif by setup).Anyone who interested can test that Detached.cmd, take a look at the resulting log file %SystemDrive%\Detached.log.OemPnPDriversPath still a must have.i still use that Detached.cmd on my disc, tho the OemPnPDriversPath still needed but it does no harm to include that script, i compress all my $OEM$\$$, $1, $Docs, $Progs and extract @T-39 even with OemPreinstall=No(no copy @textmode, everything on disc). Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now