Guide For Compressed Drivers Unattended Install

[CrashUK]

this works very well 7zip packed drivers.. and it speed upinstalling windows if you have a lot of drivers.

[Thauzar]

I am currently trying using the new 7za and the other files from the updated version. But with the older one I get no drivers in C:\DRIVERZ but 1 file (I forgot the name but there is a 1 in it... somebody already reported this error. I used 7zip to compress my drivers. I test my installations with VirtualPC from Microsoft, not VMWare. Hope the updated files will solve the problem, will report on this in about an hour or so

[turbomcp]

i used a real pc this time

with updated 7za.exe

but still same problem

on

C:\DRIVERZ

i see only the root of the folders i 7ziped(vmware,vga,net,Sound)

but no subfolders or drivers there

any idea

??

what am i doing wrong

i add the 3 files(with updated 7za.ex_) to i386

added 3 entries to txtsetup.sif

created $OEM$\DRIVERZ and added my 7zip files(root and drivers beneeth it like VGA\A;VGA\b...... root being VGA)

and added guiunattended......driverz...

any idea

[turbomcp]

here are the files if anyone is interested in helping me

[sourceDisksFiles]

bootvid.dll = 1,,,,,,3_,2,0,0,,1,2

kdcom.dll = 1,,,,,,3_,2,0,0,,1,2

c_1252.nls = 1,,,,,,3_,2,0,0,,1,2

c_437.nls = 1,,,,,,3_,2,0,0,,1,2

l_intl.nls = 1,,,,,,3_,2,0,0,,1,2

vgaoem.fon = 1,,,,,,3_,22,0,0,,1,2

acpi.sys = 100,,,,,,3_,4,1,,,1,4

wmilib.sys = 1,,,,,,3_,4,0,0,,1,4

atapi.sys = 100,,,,,,4_,4,0,0,,1,4

disk.sys = 100,,,,,,5_,4,0,0,,1,4

classpnp.sys = 100,,,,,,5_,4,0,0,,1,4

dmio.sys = 100,,,,,,4_,4,0,0,,1,4

dmload.sys = 1,,,,,,4_,4,0,0,,1,4

ftdisk.sys = 1,,,,,,3_,4,0,0,,1,4

intelide.sys = 100,,,,,,3_,4,1,,,1,4

pciidex.sys = 100,,,,,,3_,4,0,0,,1,4

isapnp.sys = 1,,,,,,3_,4,1,,,1,4

7za.exe = 1,,,,,,,2,0,0

Drvz.exe = 1,,,,,,,2,0,0

DevPath.exe = 1,,,,,,,2,0,0

;SetupMgrTag

[Data]

AutoPartition=0

MsDosInitiated="0"

UnattendedInstall="Yes"

AutomaticUpdates=yes

[unattended]

UnattendMode=FullUnattended

OemSkipEula=Yes

Repartition=No

OemPreinstall=Yes

UnattendSwitch="yes"

TargetPath=\WINDOWS

DriverSigningPolicy=Ignore

NonDriverSigningPolicy=Ignore

[GuiUnattended]

DetachedProgram="%SystemRoot%\system32\DRVZ.EXE"

AdminPassword="xxxx"

EncryptedAdminPassword=NO

OEMSkipRegional=1

TimeZone=135

OemSkipWelcome=1

[userData]

ProductKey=xxxx-xxxxx-xxxx-xxxx-xxxx

FullName="**"

OrgName=""

ComputerName=*

[RegionalSettings]

LanguageGroup=12,1

SystemLocale=0000040d

UserLocale=00000409

InputLocale=0000040d:0000040d

InputLocale_DefaultUser=00000409:00000409

UserLocale_DefaultUser=00000409

[identification]

JoinWorkgroup=MSHOME

[Networking]

InstallDefaultComponents=Yes

[WindowsFirewall]

Profiles = WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]

Mode = 0

[iEPopupBlocker]

AllowedSites=

BlockPopups=Yes

FilterLevel=High

ShowInformationBar=Yes

[Components]

msmsgs=on

msnexplr=off

[shell]

DefaultStartPanelOff = Yes

DefaultThemesOff = Yes

[Display]

BitsPerPel = 32

Vrefresh = 85

Xresolution = 800

Yresolution = 600

[GuiRunOnce]

[keul]

Ok, I'm back after further tests in real pc environment.

I've got 2 news for you : a bad one, and a... bad one

The bad one is that serialzs updated method does not work at all (at least for me). I copied new files, and didn't forget to update txtsetup.sif. But this time, there was no C:\Drivers forder at all at the end of install (although the 3 files were in windows\system32).

After that, I tried the hybrid method I described a few posts above : renaming 7za.exe to 7z.exe and packing it (using old drvz.exe). Yesterday, with this method in vmware, I had *.7z files unpacked, good device path in registry, but none of them has been installed. I thought I was vmware's fault (my vmware.7z drivers didn't match vmware version.). After that, I tried updating vmware drivers on my unattend cd, but with no success : no drivers were installed during setup. BUT after setup when I clicked on "update drivers" in device manager, new drivers were automatically found in c:\drivers\vmware. .

Then, I blamed vmware one more time and decided to test in real environment but then again, the same thing appened : drivers are unpacked but not installed during setup (although, as in my vmware tests, "update drivers" is working great after setup).

To complete, I would say that I've got SP2 slipstreamed on a XP french version, and that old method (oemdriverspath + self extracting 7z) always worked for me.

So has anyone got this metod to work, or is this a kind of curse above my head ?

[Bâshrat the Sneaky]

Ok, I'm back after further tests in real pc environment.

I've got 2 news for you : a bad one, and a... bad one   

The bad one is that serialzs updated method does not work at all (at least for me). I copied new files, and didn't forget to update txtsetup.sif. But this time, there was no C:\Drivers forder at all at the end of install (although the 3 files were in windows\system32).

After that, I tried the hybrid method I described a few posts above : renaming 7za.exe to 7z.exe and packing it (using old drvz.exe). Yesterday, with this method in vmware, I had *.7z files unpacked, good device path in registry, but none of them has been installed. I thought I was vmware's fault (my vmware.7z drivers didn't match vmware version.). After that, I tried updating vmware drivers on my unattend cd, but with no success : no drivers were installed during setup. BUT after setup when I clicked on "update drivers" in device manager, new drivers were automatically found in c:\drivers\vmware.  .

Then, I blamed vmware one more time and decided to test in real environment but then again, the same thing appened : drivers are unpacked but not installed during setup (although, as in my vmware tests, "update drivers"  is working great after setup).

To complete, I would say that I've got SP2 slipstreamed on a XP french version, and that old method (oemdriverspath + self extracting 7z) always worked for me.

So has anyone got this metod to work, or is this a kind of curse above my head ?

In theory it SHOULD work. For CrashUK it worked!

I too will test this also ASAP and post my results.

[Thauzar]

I too have XP SP2 french version and this time, with the updated files, there was not even a DRIVERZ folder on my root drive. I had tried with the new files, and I did not forget to update the txtsomething.sif I had to change. I really don't know what is going on but we took a step back, not forth.

Need help here I guess

[Lucius Snow]

Hmm i have a little question about the way to install it.

I've created a CD with a multiboot menu (XP regular / XP unattended) by following the method described there.

So 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).

Tell me if i did it right.

Thank you very much.

[keul]

@Lucius Snow : I think you should be right. I'll keep fingers crossed for you.

@Thauzar : Thank you ! I'm not the only one to be cursed ! Try using old drvz.ex_ and 7za.ex_ renamed to 7z.ex_, (and of course, change txtsetup.sif), it worked for me (i mean, 7z files were unpacked, not installed). I think there is a problem with new drvz.exe, if serialzs is around ...

[turbomcp]

i was begining to think im nuts or something

since this thing doesnt work

did about 10 installs on vmware or physical pc

same thing

anyway i think vmware doesnt have any "bugs" this is regular extraction and search for drivers during install,nothing more

if it will work in vmware it will work on regular pc also

i mean when i use oempnppath= for vmware drivers they all work great

so vmware can do it

its something to do with the filesa themself and what they do

anyway waiting for serials to see whats happening

[serialzs]

@Thauzar

XPSP2 french i use ONLY ENGLISH version can you tell me what's there DIFFERENCE...

@Lucius Snow

multiboot i think it will work try to test it cause i dont use multiboot CDs...

sorrie...

@keul

can you post all your Folder Structure...

@turbomcp

how did you compressed your drivers???

[serialzs]

@all

if you want it to try this PROG...

here is the steps:

1. extract the ZIP file wherever you want...

2. expand the 7za.ex_, Drvz.ex_, DevPath.ex_ to 7za.exe, Drvz.exe, DevPath.exe

then put it in your %systemroot%\system32...(no renaming of files)

3. burn your COMPRESSED DRIVERS... (just like in the folder structure but without i386 folder...

4. dont remove the burn CD in your ROM...

5. Run... then type DRVZ.EXE

Example: you have a FILE NAMED VIDEO.CAB and SOUND.7z

heres what will happened:

1. open your %systemdrive%

2. see what inside of the folder named DRIVERZ (not S its Z)

3. you must see there the FOLDER NAMED as VIDEO and SOUND

4. inside of each FOLDER there must be your COMPONENT DRIVER FILES

5. to know if it REG in your REGISTRY run REGEDIT then look for

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\DevicePath

then see if your existing %systemdrive%\DRIVERZ are in the DevicePath...

thats all if it works in you OS it will be WORK in you XP INSTALLER...

-=[serialzs]=-

[Incroyable HULK]

Hi! I can wait to test Guide4Drivers tommorow...

As I Understand your instructions, step 3 is your way of transferring theses files to SYSTEM32...

3. Put the 3 files inside i386 folder then edit TXTSETUP.SIF

In TXTSETUP.SIF find [sourceDisksFiles]then add this 3 lines...

7za.exe = 1,,,,,,,2,0,0

Drvz.exe = 1,,,,,,,2,0,0

DevPath.exe = 1,,,,,,,2,0,0

So if I put theses files in \$OEM$\$$\System32 it should do the same instead of editing TXTSETUP.SIF? Right?

thanks!

[keul]

@serialzs:

here is my folder structure :

ROOT
   .$OEM$             (containing cmdlines.txt, registry.inf, apps.inf...)
   ...$1
   .....Apps
   .......Winamp
   .......Winrar
   .......Winzip
   .......[...]
   .....Patch          (empty)
   ...$$
   .....system32     (containing directx.cpl, and oemlogo*.* ...)
   ...Driverz          (containing chipset.7z, sound.7z, video.7z.....)
   .I386                (containing 7za.ex_, devpath.ex_, drvz.ex_)
   ...system32
   ...drw
   .....1033
   .....1036
   ...compdata
   ...asms
   .....1
   .....2
   .....10
   .....[...]
   .Support
   ...Tools
   .ValueAdd
   .Xtra

I tried your new files on my system with everything you said (files copied in system32, drivers burned...) with the same results as in vmware and real environment installation : no error message, but no folder Driverz is created in C:\. But I noticed one thing that might be interesting : my device path (which originally was only "%SystemRoot%\Inf") was transformed in this after launching drvz.exe :

%SystemRoot%\Inf;C:\WINDOWS\System32\1025;C:\WINDOWS\System32\1028;C:\WINDOWS\System32\1031;C:\WINDOWS\System32\1033;C:\WINDOWS\System32\1036;C:\WINDOWS\System32\1037;C:\WINDOWS\System32\1041;C:\WINDOWS\System32\1042;C:\WINDOWS\System32\1054;C:\WINDOWS\System32\2052;C:\WINDOWS\System32\3076;C:\WINDOWS\System32\3com_dmi;C:\WINDOWS\System32\appmgmt\MACHINE;C:\WINDOWS\System32\appmgmt\S-1-5-21-1482476501-1078081533-682003330-500;C:\WINDOWS\System32\appmgmt;C:\WINDOWS\System32\CatRoot\{127D0A1D-4EF2-11D1-8608-00C04FC295EE};C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}\TempDir;C:\WINDOWS\System32\CatRoot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE};C:\WINDOWS\System32\CatRoot;C:\WINDOWS\System32\CatRoot2\{127D0A1D-4EF2-11D1-8608-00C04FC295EE};C:\WINDOWS\System32\CatRoot2\{F750E6C3-38EE-11D1-85E5-00C04FC295EE};C:\WINDOWS\System32\CatRoot2;C:\WINDOWS\System32\Com;C:\WINDOWS\System32\config\systemprofile\Application Data\Microsoft\Internet Explorer;C:\WINDOWS\System32\config\systemprofile\Application Data\Microsoft\SystemCertificates\My\Certificates;C:\WINDOWS\System32\config\systemprofile\Application Data\Microsoft\SystemCertificates\My\CRLs;C:\WINDOWS\System32\config\systemprofile\Application Data\Microsoft\SystemCertificates\My\CTLs;C:\WINDOWS\System32\config\systemprofile\Application Data\Microsoft\SystemCertificates\My;C:\WINDOWS\System32\config\systemprofile\Application Data\Microsoft\SystemCertificates;C:\WINDOWS\System32\config\systemprofile\Application Data\Microsoft;C:\WINDOWS\System32\config\systemprofile\Application Data [B][... ok I stop here, there's no use to paste everything : it's every system32 subfolders[/B]]

The same thing happens when I install in vmware or real environment with your new files...

Now, using my "famous" hybrid method (old drvz.exe and 7za.exe renamed to 7z.exe), everything is fine :

Folder strucure of C:\Driverz:

31/08/2004  09:36    <REP>          chipset
31/08/2004  09:37    <REP>          lan
31/08/2004  09:37    <REP>          modem
31/08/2004  09:37    <REP>          monitor
31/08/2004  09:37    <REP>          sound
31/08/2004  09:37    <REP>          video
31/08/2004  09:37    <REP>          vmware
 R‚pertoire de C:\Driverz\chipset
31/08/2004  09:36    <REP>          chipset
 R‚pertoire de C:\Driverz\chipset\chipset
31/08/2004  09:36    <REP>          nF
31/08/2004  09:37    <REP>          SiS
31/08/2004  09:37    <REP>          VIA-k7
 R‚pertoire de C:\Driverz\chipset\chipset\nF
31/08/2004  09:36    <REP>          IDE
31/08/2004  09:36    <REP>          IO
 R‚pertoire de C:\Driverz\chipset\chipset\nF\IDE
31/08/2004  09:36    <REP>          ITB
 R‚pertoire de C:\Driverz\chipset\chipset\nF\IDE\ITB
 R‚pertoire de C:\Driverz\chipset\chipset\nF\IO
 R‚pertoire de C:\Driverz\chipset\chipset\SiS
 R‚pertoire de C:\Driverz\chipset\chipset\VIA-k7
 R‚pertoire de C:\Driverz\lan
31/08/2004  09:37    <REP>          lan
 R‚pertoire de C:\Driverz\lan\lan
31/08/2004  09:37    <REP>          3C
31/08/2004  09:37    <REP>          BR
31/08/2004  09:37    <REP>          BU
31/08/2004  09:37    <REP>          D
31/08/2004  09:37    <REP>          I
31/08/2004  09:37    <REP>          L
31/08/2004  09:37    <REP>          LI
31/08/2004  09:37    <REP>          M
31/08/2004  09:37    <REP>          N
31/08/2004  09:37    <REP>          NV
31/08/2004  09:37    <REP>          O
31/08/2004  09:37    <REP>          R
31/08/2004  09:37    <REP>          S
31/08/2004  09:37    <REP>          V
 R‚pertoire de C:\Driverz\lan\lan\3C
31/08/2004  09:37    <REP>          1
31/08/2004  09:37    <REP>          2
 R‚pertoire de C:\Driverz\lan\lan\3C\1
[...]

And DevicePath :

%SystemRoot%\Inf;C:\Driverz\chipset\chipset\nF\IDE\ITB;C:\Driverz\chipset\chipset\nF\IDE;
C:\Driverz\chipset\chipset\nF\IO;C:\Driverz\chipset\chipset\nF;
C:\Driverz\chipset\chipset\SiS;C:\Driverz\chipset\chipset\VIA-k7;
C:\Driverz\chipset\chipset;C:\Driverz\chipset;C:\Driverz\lan\lan\3C\1;
C:\Driverz\lan\lan\3C\2;C:\Driverz\lan\lan\3C;C:\Driverz\lan\lan\BR\1;
C:\Driverz\lan\lan\BR\2;C:\Driverz\lan\lan\BR;C:\Driverz\lan\lan\BU\1;
C:\Driverz\lan\lan\BU\2;C:\Driverz\lan\lan\BU\3;C:\Driverz\lan\lan\BU;
C:\Driverz\lan\lan\D\1;C:\Driverz\lan\lan\D\500sx;C:\Driverz\lan\lan\D\500T;
C:\Driverz\lan\lan\D\530TX+;C:\Driverz\lan\lan\D\550T;[...]

which is the same result I have in vmware or real environment with "hybrid" method.

So obviously, you did something else in your new script that just changing a call from 7z.exe to 7za.exe, otherwise, it would have given the same results, right ?

What else can I say ?

- Although unpacking driverz and setting devicepath correctly, hybrid method doesn't help installing drivers during setup

- Hybrid method works however when clicking "update drivers" in device manager once windows is installed

- oempnpdriverspath method works ok with those drivers during setup

- Yesterday, I tried installing windows in vmware someting like 10 times (only sp1, adding "UpdateInstalledDrivers=Yes" in winnt.sif, adding "OEMPnPSigningPolicy=ignore" in winnt.sif, putting only vmware.7z file in driverz in case of a bad inf file bugging the whole thing, formating in fat32, in ntfs [who knows ?]...) but with no luck.

So it seems that there are 2 separated problems :

1- New files (with 7za.exe) not working at all on some (all?) systems.

2- The whole method which seems to work regarding to unpack files and modifying registry during setup but doesn't help to install drivers (may be setup doesn't wait for your script to end up at t-39 before detecting devices, may be registry is cached so modification are not applied immediatly...).

What else can I do to help finding what's going wrong ? I tried reversing your autoit script but it seems that you blocked decompilation so I couldn't do anything about it. Any idea before I get mad ?

[Bâshrat the Sneaky]

@Keul: it shoulbe cmdlines.txt, not cmdlines.inf!