Manual integration and installation question (Page 1 of 2)

WAIK / DISM

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

okay, wasn't lazy, did a little research, it is possible after all, and in a number of ways even...

METHOD 1 (too long):

first, you HAVE to dism mass storage drivers (and lan - if you enabled network for pe in answer file) into boot.wim (2nd index only needed for setup) cause it runs completely from memory and copies nothing to hdd (and dvd drive could be ANY letter at this point) - it is equivalent to integrating them in I386 folder as before for xp

but know that the injected drivers are automaticaly expanded within image, and multiple copies of them are kept separately if there are more than one .inf files per folder (or multiple entries in a single *.inf), so integrate only boot critical drivers this way (chipset, storage and lan) or your image may not fit on a dvd - and you can actualy run out of ram when booting from it

mount image (must be writable, so copy to hdd first):
Dism /Mount-Wim /WimFile:C:\test\boot.wim /Index:2 /MountDir:C:\test\offline

remove old drivers (skip if this is the first time):
Dism /Image:C:\test\offline /Remove-Driver /Driver:OEM1.inf /Driver:OEM2.inf ...  /Driver:OEM99.inf
(how ever many there are third party drivers in C:\test\offline\Windows\Inf folder, you cant uninstall default ones)

inject all the drivers from C:\D folder, including in subfolders and even unsigned ones:
Dism /Image:C:\test\offline /Add-Driver /Driver:C:\D /Recurse /ForceUnsigned

dismount image (and then replace boot.wim from where you got it):
Dism /Unmount-Wim /MountDir:C:\test\offline /Commit

second, you create a $OEM$\$$\Inf\D folder INSIDE sources folder on install dvd/usb (not in root anymore) and add ALL the drivers there (dvd:\sources\$OEM$\$$\Inf\D) - they get automaticaly copied to C:\Windows\Inf\D folder during install (and windows already searches for drivers there on its own, including subfolders), only needed ones also get copied to windows driverstore folder, so you can safely delete C:\Windows\Inf\D after install if you wish

METHOD 2 (but only for vista/2008 with any integrated service pack, or 7 and 2008 R2):

at install windows automaticaly searches ALL the available drives for $WinPEDriver$ folder (not $WinPEDriverS$) in its root, so copy only boot critical drivers there (dvd:\$WinPEDriver$), they can be in subfolders too and are used during the whole install

but beware not to run out of ram as before, cause WinPE doesnt have anywhere else to keep its driverstore folder but memory

also - if a driver fails to inject in boot.wim with dism tool (as in previous method) the setup WILL fail if you put it in $WinPEDriver$ folder, so i suggest that you test all the drivers with dism FIRST (you can see the failed ones in C:\Windows\Logs\DISM\dism.log file) and move the bad ones to dvd:\sources\$OEM$\$$\Inf\D folder (as in previous method)

winpe supports cabbed drivers - but i had to expand some to work with dism (only 2 or 3 out of ALL the available driverpacks, but just one can f*ck you up)

METHOD 3 (too large):

forget everything from above and in the answer file for install.wim image, under Microsoft-Windows-Setup in WinPE pass just set UseConfigurationSet to true - now you have a system variable %configsetroot% which always points to the drive containing autounattend.xml in its root (doesnt need to be the install drive)

add the %configsetroot%\your_drivers_path to Microsoft-Windows-PnpCustomizationWinPE as a device driver path, and they are immediately available from the very start

but know that ALL the files from %configsetroot% drive WILL be automaticaly copied to C:\Windows\configsetroot folder, which can safely be deleted afterwards

EDIT: corrected $OEM$\$$\Windows\Inf\D to $OEM$\$$\Inf\D (but $OEM$\$1\Windows\Inf\D would work too)

Last edited by pOcHa (2010-10-31 12:10:48)

thank you, it is the least i could do to contribute for all of your hard work, since paypal still ignores Serbia

its $WinPEDriver$ actualy, not %WinPEDriver% sorry (and you just unzip the downloaded driverpacks there any way you like), edited the previous post with some more clarifications...

here is a very simple batch file with which i makecab (best compression) all usual driver files (but not *.exe, sometimes i need to start the driver installation manualy) in ALL the subfolders under it - it also deletes the originals afterward and writes a log file too (use wordpad not notepad)

UPDATE: there must be NO spaces in folder names, driverpacks dont have them so just check your path from root to batch file (makecab doesn't support spaces nor quotes in paths, stupid m$ would probably just say as always - its not a bug, its a feature!)

echo %date% %time% > MakeCab.log

FOR /R %%i IN (*.bin;*.cat;*.cpl;*.dat;*.dll;*.sys;*.vxd) DO MakeCab.exe /D CompressionType=LZX /D CompressionMemory=21 /L %%~dpi "%%i" >> MakeCab.log& DEL "%%i" /F /Q

PAUSE

and here is a very simple batch file with which i expand all the compressed driver files in ALL the subfolders under it, delete originals and write a log

echo %date% %time% > Expand.log

FOR /R %%i IN (*.??_) DO Expand.exe -r "%%i" >> Expand.log& DEL "%%i" /F /Q

PAUSE

i noticed that the dpinst.ex_ file in nvidia drivers is NOT cabbed but actualy just renamed, and of course expand doesnt know that so it just renames it too BUT not to its original name dpinst.exe - but to dpinst.ex or even dpinst.ex. sometimes (so check the logs always)

hope this helps...

Last edited by pOcHa (2010-10-24 08:05:46)

To make changes to BCD stores OTHER than the Boot store, use the /store switch. For example, this command:

      BCDEdit.exe /set {default} TESTSIGNING ON

becomes this, instead:

      BCDEdit.exe /store D:\Boot\BCD /set {default} TESTSIGNING ON

this is, of course, assuming one hard drive, the hidden boot partition, and booted from standard WinPE, causing the hidden BOOT partition to be assigned drive letter D:

ZC

silly me, its quite simple really, {default} entry in every bcd file on install dvd is for either winpe or setup (even in wim images), and windows entry gets automaticaly created during install (and then set to {default} one) with a unique guid so it cant be known in advance...

BUT {globalsettings} entry exist from the start with same guid, and all new entries inherit setting from it, so i will now try to:

1.) run bcdedit commands in winpe pass for {globalsettings}
UPDATE: didnt try it, cause you lose repair and upgrade options (only fresh install) when exist winpe pass in answer file

2.) edit {globalsettings} in ALL bcd files on install dvd (including inside images)
UPDATE: edited d:\boot\bcd and added another one to dvd:\sources\$OEM$\$$\Boot\DVD\PCAT to overwrite install.wim's, was to lazy to inject the last one in boot.wim also - but didnt and wouldnt work anyway, see below why

3.) add a bcd file with edited {globalsettings} from already installed windows to dvd:\sources\$OEM$\$1\Boot folder to overwrite the setup's one
UPDATE: setup creates a completely NEW bcd file and it gets succesfuly overwriten from $oem$ in offlineservicing pass, but AFTER all files get copied it creates random guids for a couple of entries so i ended up with duplicates - this method works, just delete "Windows 7", "Windows Resume Application", "Windows Recovery Environment" and "Ramdisk Options" from bcd in $oem$

only other alternatives to 3. would be a way to add bcd commands to offlineservicing pass or finding a script which creates a new bcd file (its not from any of the already existing bcd's on install dvd)

NOW, as you can see from batch files in my previous post, the peauth service must be stopped or it bsods already installed windows on logon and hangs up the setup on first logon too (and after restart it WONT continue) - i added the commands in serialize pass BUT they dont get executed soon enough, so i am at the end of my witts here and changing registry in install.wim just seems like too much work

Last edited by pOcHa (2010-10-24 04:29:01)

All excellent Info pOcha

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

There is an updated WAIK posted at the Microsoft download site - supposedly version 2.0.

cleaned and updated the guide with new driver signing workaround here:

http://forums.mydigitallife.info/thread … drivers...

Last edited by pOcHa (2010-10-31 15:27:01)

The instructions are above...

That is to say you asked "what the best way to do add drivers" at the end of the thread that describes in great detail the best way to do it...

Obviously you have been banging your head against the wall too long . (skip that step and read the above thread)

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

On the contrary, you must install windows before you do anything else... Yes?
Windows is installed from a Wim file... Yes?

That makes these instructions "Step 0"
IE the very first thing you do.

Once you add the drivers to windows... you are done... Let me be even more clear... These instructions don't just add the drivers during the install... They permenently add the drivers to windows.

Again what you want and keep asking for is right under your nose ... well if you scroll up.

DP BartPE Tutorial   DP_BASE Tutorial   HWID's Tool     Read BEFORE you post    UserBars!

The DriverPacks, the DP_Base program, and Support Forum are FREE!.

haeey.i read out all post its useful but i m worried about win7 drivers,
i search out a lot of time win7 graphics drivers but 

SO please suggest me webs for downloading win7 complete drivers

Yes There is an updated WAIK posted at the Microsoft download site - supposedly version 2.0.