[xenon2050]

WOW! That guide is absolutely, totally, awesome! I downloaded WAIK and was trying to figure out how to use it then I remembered having run across your guide... And it saved me a lot of time and errors, at least so far. At the very least it will point me in the right direction. Thanks!

[rick456]

Thanks Martin, for your well explained and helpful guide(s)/site, please keep it up.

And, not to be too off-topic but, I tried to use your "http://firegeier.unattended-sponsor.de/en/inject_drivers_into_image.html" but my problem seemed to be rooted in the "boot.wim".
I had that annoying "...CD/DVD required device drivers is missing..." very early on in the Phase1 install ?
But this led me to look a little deeper and I found
http://apcmag.com/54..._windows_pe_2_0, which with a bit of your guide fixed my initial unattended driver-injection booting problem.
ok, bear with me here, but a lot of people have had this kinda problem too, and I've posted this tip elswhere, maybe you could brush it up and add it to your guide collection as "inject drivers into boot.wim using PETools"?

Also, If I followed something wrong in your guide/site, believe me -I RTFM'd it, then just yell at me, - its ok,
but in the meantime I'd like to share my "boot.wim" FIX with
ya'll. maybe it could be of use to some users who need to apply this before they can get into the fully-unattended tips in your guide(s). ?

...
*********************************************************************
for that "...CD/DVD required device drivers are missing..." on my Vista 64 new install.

-the web-links mentioned here provide a very good understanding, for me anyway, for
dealing with any automated Vista installs.-and many thanks to those Authors.
I went into some over-detail here, but hey, step-by-step feedback is good,
especially when it includes corrections.

I think, during the very early install phases of a PASS1, the "boot.wim" a mini-Vista boot image
is loaded with a bare skeloton of drivers into a virtual-memory-CD-Drive,
(very similar to "md" Memory Devices used in unix).
This however, is just enough to begin installing the big PASS2(nonWinPE) "install.wim" Vista image
onto your HD via your DVD-drive.
-But, if for instance, the virtual mini-Vista image(boot.wim) can't load the
"...required CD/DVD device drivers..."
for example, the newer SATA DVD-Drive/controller(s), then it needs to find them via
a loadable floppy, USB-flash drive,...which is where You come in -compliments of Microsoft.

So, to permanently fix this you basically "mount" your copied ...\sources\boot.wim,
inject the required drivers (.inf files), unmount it, and then "re-image" your
new (OEM) DVD master on a blank DVD.

-and here's the "General" HowTo driver-injection article I found (for Vista 32), and early Workstation deployments,
which worked for me.
http://apcmag.com/54..._windows_pe_2_0

----------------------------------------------------------
Here's my Hardware/OS:
-Microsoft Vista Ultimate 64-bit OS(purchased separately (brand new & legit), so as to Install "fresh" on my:
-Asus P5B-Premium Vista Edition motherbard; (no its not a joke, the board is actually called Vista Edition)
(with the onboard Intel ICH8R SATA controllers,.. and a Jmicron JMB363 PATA/SATA controller)
-Intel Quad-core CPU
-(2) Raptors striped across the ICH8R Sata controllers
-(1) Pioneer "SATA" DVR-212D DVD/CD on the Jmb363 sata controller(AHCI mode in BIOS).
---------------------------------------------------------

Note:
(my steps below are all for an "Ultimate Vista 64-bit" unattended driver injection,
Vista 32 will be slightly different $PATHS, however the info-link mentioned in
http://apcmag.com/54..._windows_pe_2_0 is for Vista 32, and is a good quick-reference guide
for modifying Vista "boot.wim" image files)

Important! -> You will need your (OEM) DVD, and the Windows "WAIK" installed from:
http://www.microsoft.com/downloads/details...;DisplayLang=en
-its a 998 Meg (mini)Vista DVD image file download, which you'll burn on a blank DVD and install it.
-Included with it though, is both the:
"Windows System Image Manager"-WSIM app- (which is primarily used for modifying ...\sources\install.wim image files).
and,
"Windows PE Tools Command Prompt" -PETools app- (which is primarily used for modifying ...\sources\boot.wim image files).

You'll only needed the PETools part of WAIK for this scenario.

Here's the steps I used:

1./ copy entire (OEM) DVD to D:\DVD, and make a couple sub-folders under D:\DVD
named "Drivers" and "Mount".

2./ In my case, I copied just the required (Intel and Jmicron)SATA contoller driver files to D:\DVD\Drivers
(*.inf/cat/sys files - but no exe's) any not-needed-for-booting drivers can may have go into "install.wim" later.

3./ Share D:\DVD with "full-control" permissions for yourself/Admin.

4./ if you have Vista 32 -skip to step 5./, otherwise, open an Administrator command shell
from "Start" -> "run" type cmd but instead of hitting "Enter"-key, hit the "Ctrl-Shift-Enter"
SETX Imgx "%Programfiles%\Windows AIK\Tools\amd64" -m

5./ from your "Start" -> Programs" -> "Microsoft Windows AIK" -Run as Admin the
"Windows PE Tools Command Prompt" shell.

6./
(cd C:\Program Files\Windows AIK\Tools\amd64)
imagex /mountrw D:\DVD\sources\boot.wim 2 D:\DVD\Mount
(cd C:\Program Files\Windows AIK\Tools\PETools)
peimg /inf=D:\DVD\Drivers\*.inf /image=D:\DVD\Mount
(cd C:\Program Files\Windows AIK\Tools\amd64)
imagex /unmount /commit D:\DVD\Mount
(cd C:\Program Files\Windows AIK\Tools\PETools)
oscdimg -n -m -b"%Programfiles%\Windows AIK\Tools\PETools\amd64\boot\etfsboot.com" D:\DVD D:\Vista64.iso

7./ thats it, burn that .iso onto a DVD blank with your favourite 3rd-party app.

note1: (the cd ... in brackets are there for brevity, although the PETools command shell actually
adds those $PATHS to your environment automatically, depending if you've got x86(32-bit), or amd64(64-bit)
-also since I just don't fully trust Microsoft automatically anymore, I prefer to "cd" around.
note2: in Step 6./ the "-m" switch in the oscdimg command seems to be an undocumented switch, however
it is required to create the DVD image size properly.

also see
http://firegeier.una...create_iso.html
-very well explained site on unattended Vista installs in general

cheers.

[Dobby]

@razormoon - The reason for the goto is so it loops round and keeps checking all drives until it finds the DriversRoot file. WinPE starts up before the drives get mapped so if you just did one check through the drives you might not find the DriversRoot file.

@seabird - Your config looks correct. So is the console window coming up with the drive that DriversRoot has been set to?

This post has been edited by Dobby: 13 October 2007 - 04:38 AM

[Sgt_Strider]

Sgt_Strider, on Sep 22 2007, 07:10 PM, said:

I finally decided to try an unattended installation with Vista after giving up on it early in the summer. I got some questions for FireGeier or anyone that is experienced at this.

oobeSystem \ Windows-International-Core

The setting above doesn't seem to exist even though I have followed the instructions carefully and I went back to double check it. Am I missing something here? It's odd that a similar menu to this exist for the Windows PE section.

Let's say that if this menu does exist and someone tell me how to add it, how can I enable Chinese (simplified and traditional characters) for Vista? I don't see the "language group" setting that exist in Windows XP. I'm not sure how to do it and I would appreciate if someone tells me how to add it. Thanks!

Can someone please answer my questions above? I've been waiting for almost one month for a response!

[Dobby]

There are two components. One called Windows-International-Core and one called Windows-International-Core-WinPE. The WinPE one only applies to the PE pass and the other applies to specialize and oobeSystem passes.

I'm not sure about the languages as I only use English and Russian (for the wife) but I noticed something about Language Packs so maybe you need one of these Packs to be able to select the appropriate language. Sorry I can't be anymore help.

[kentk]

was it something wrong with these lines from Firegeirers guide to install drivers from media ?? (":\" should NOT be there ?)

@ECHO OFF
SET DriversRoot=NULL

:SearchDriversRoot
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\DriversRoot.txt SET DriversRoot=%%i:\
IF NOT "%DriversRoot%"=="NULL" GOTO StartSetup
GOTO SearchDriversRoot

:StartSetup
ECHO DriversRoot=%DriversRoot%
X:\setup.exe

Has anyone manage to get this to work ???

This post has been edited by kentk: 15 October 2007 - 03:12 PM

[Dobby]

That batch script is correct I've just compared it to the one I use and it's identical except that I don't add the trailing slash to the path but do it in the Autounattend.xml. But that is purely cosmetic.

Do you get the console window appear when WinPE first boots and tells you that DriversRoot has been set?

[kentk]

Dobby, I have not tried it yet..

But I will tonight

So what you are saying is that it should look like this in order to work:

@ECHO OFF
SET DriversRoot=NULL

:SearchDriversRoot
FOR %%i IN (C D E F G H I J K L M N O P Q R S T U V W X Y Z) DO IF EXIST %%i:\DriversRoot.txt SET DriversRoot=%%i:
IF NOT "%DriversRoot%"=="NULL" GOTO StartSetup
GOTO SearchDriversRoot

:StartSetup
ECHO DriversRoot=%DriversRoot%
X:\setup.exe

Why is it X:\setup.exe ?

This post has been edited by kentk: 15 October 2007 - 11:26 PM

[Dobby]

Yes it's correct. It's checking each drive for a file called DriversRoot.txt which you should have created on the drive that you have your drivers on. When it finds this file it sets an environment variable called DriversRoot to it. This is what is then used in Autounattend.xml to tell WinPE where to find the drivers for your hardware %DriversRoot%\drivers is the drive and folder that you should have your drivers in.

X:\setup.exe tells WinPE to run windows setup. This is needed because you are overriding what WinPE does when it boots. I think X:\ is a ram drive that WinPE creates and copies a bunch of startup files to (but don't quote me on that. I never checked). Either that or it's just a drive mapped from the DVD probably to give a constant drive letter that setup knows about. (As your DVD drive could be D:, E:, or F: depending on how many hard drives you have).

[Sgt_Strider]

Dobby, on Oct 15 2007, 02:04 PM, said:

There are two components. One called Windows-International-Core and one called Windows-International-Core-WinPE. The WinPE one only applies to the PE pass and the other applies to specialize and oobeSystem passes.

I'm not sure about the languages as I only use English and Russian (for the wife) but I noticed something about Language Packs so maybe you need one of these Packs to be able to select the appropriate language. Sorry I can't be anymore help.

Can you post the settings that you're using to enable Russian language support?

[kentk]

Dobby, on Oct 16 2007, 08:15 AM, said:

Yes it's correct. It's checking each drive for a file called DriversRoot.txt which you should have created on the drive that you have your drivers on. When it finds this file it sets an environment variable called DriversRoot to it. This is what is then used in Autounattend.xml to tell WinPE where to find the drivers for your hardware %DriversRoot%\drivers is the drive and folder that you should have your drivers in.

X:\setup.exe tells WinPE to run windows setup. This is needed because you are overriding what WinPE does when it boots. I think X:\ is a ram drive that WinPE creates and copies a bunch of startup files to (but don't quote me on that. I never checked). Either that or it's just a drive mapped from the DVD probably to give a constant drive letter that setup knows about. (As your DVD drive could be D:, E:, or F: depending on how many hard drives you have).

Thanks Dobby

Is this method the best way to add AHCI drivers for my SATA disc during installation ??

This post has been edited by kentk: 16 October 2007 - 05:03 AM

[Dobby]

You're welcome

I don't know the answer to that. I've not had to install SATA drivers since XP SP1!

Anyone else?

This post has been edited by Dobby: 16 October 2007 - 05:15 AM

[kentk]

Yes, SATA drivers are included but not the AHCI drivers, you have to choose this setting in bios

in AHCI mode the SATA disc has better performance....i think

This post has been edited by kentk: 16 October 2007 - 05:17 AM

[razormoon]

@kentk and anyone else who is interested...

You can always hit Shift-F10 to bring up a cmd window during install. I've done this many times as it has allowed me to edit cmd files on-the-fly without having to rebuild an image. Pretty cool when you make mistakes in your cmd/batches. You can even run some programs from it (ie; notepad.exe).

I also use it to search drives (such as X:) to watch everything as it happens...

Careful when editing some files though as timing is everything (for instance, I edit setupcomplete.cmd at the very last second (beginning of third boot)). And you will most likely have to do ATTRIB -R commands to be able to edit some files (such as setupcomplete.cmd).

This post has been edited by razormoon: 16 October 2007 - 09:42 PM

[kentk]

cant get the "install drivers from media or DVD" to work...

Have set the Microsoft-Windows-PnPCustomizationsWinPE \ DriverPaths \ PathAndCredentials path to %DriversRoot%\Drivers

And in Setdriversroot.cmd

....SET DriversRoot=%%i:

When I boot the ISO I get a cmd window which say driversroot = d:

Shortly after I get a error window:

It is not possible to install one or more drivers which is necessary for systemstart, check that the drivers are correct and restart installation, OK...

I have copied files into the drivers folder, have made subfolders called 000_xxxx and in the folders I have unpacked the drivers (.inf and other filetypes)
Should it ONLY be .inf files in the folders ???

This post has been edited by kentk: 17 October 2007 - 02:38 PM

[Dobby]

Can you install Vista manually? I'm sure you can but I just wanted to check.

Also, have you checked the Windows\Panther logs setupact.log and setuperr.log and also in the UnattendGC folder (under the panther folder). Sometime (but not often) they give a bit more info about the error. If you press Shift+F10 when you get the error you'll get a command prompt. You could just try navigating to the folder mentioned just to make sure it's visible.

Lastly, try removing all but one of the drivers you are trying to install. If you list the drivers this may help us diagnose the problem. Also what medium do you have the Autounattend.xml and drivers on and what filesystem is it formatted as.

This post has been edited by Dobby: 17 October 2007 - 02:59 PM

[kentk]

The vista installation iso is/was working before this...

I have just altered the needed steps for "install drivers from media or dvd" and then this problem occoured

I have tried to burn DVD and ISO on VM same result

I tried to rename folders without 000_xxx and removed all but the .inf files, same error

I have added AHCI, Intel inf, Yukon LAN, intel LAN drivers...

setupact.log shows all files, tells that some is not .inf and pass on..in the end there is 0x0640ae IBSLIB publishmessage:It is not possible to install one or more drivers which is necessary for systemstart, check that the drivers are correct and restart installation

no UnattendGC folder !?

EDIT:

Another question, in the guide : imagex /mountrw D:\VistaWork\DVD\sources\boot.wim 2 D:\VistaWork\Mount

to mount boot.wim, but should it not be a "1" for the PE and not a "2" as in the guide ???

This post has been edited by kentk: 18 October 2007 - 02:53 AM

[kentk]

Anyone ??? Dobby ?

Have we lost Martin ? have not seen posts from him for a long while

This post has been edited by kentk: 21 October 2007 - 01:43 AM

[Dobby]

Dobby, on Oct 17 2007, 02:56 PM, said:

Lastly, try removing all but one of the drivers you are trying to install. If you list the drivers this may help us diagnose the problem. Also what medium do you have the Autounattend.xml and drivers on and what filesystem is it formatted as.

Have you tried this?

2 is correct

What's the Intel INF? Do you mean the lan drivers. Start with one set of drivers. And BTW it doesn't matter what other files/folders are in the drivers folder. I find it easiest just to place the whole bundle in there.

This post has been edited by Dobby: 21 October 2007 - 02:43 AM

[kentk]

Maybe I missunderstand what this pass is for !?

I thought I would add up all known drivers for my system so I dont need to install them after vista is installed..

I thought that this pass would make all drivers present for vista...

Intel INF is intel chipset drivers..