After you provide all the information that the custom Windows PE service OS build script requires
winpe.wim
are extracted into the WIM directory (for example, C:\build_work\WIM
). There are two ways to do this:Method A: Use a Windows AIK tools to make your modifications.
If you are using Windows AIK version 1.1, use the peimg.exe
command. The default location of this executable file is:
C:\Program Files\Windows AIK\Tools\PETools\peimg.exe
If you are using Windows AIK version 2.0 or 3.1, use the dism.exe
command. The default location of this executable file is:
C:\Program Files\Windows AIK\Tools\Servicing\dism.exe
See the Windows AIK documentation for information about how to use these commands (or use the /help
command line option).
Method B: Add the drivers to a driver list.
After you see a message indicating that all required information is gathered, the build.config
file will be created in the C:\ Build_scripts
directory to store the information that is needed to build the winpe.wim
and the ISOs. You can use a text editor to open this file and add the appropriate drivers below the empty DRIVERS
list.
For example:
declare DRIVERS = “ cdrom.inf \
e:\\tmp\\work\\WIM\\windows\\inf\\adp94xx.inf \
e:\\tmp\\work\\WIM\\windows\\inf\\3com*.inf “
Note: Because the back-slash (\
) is a special character, you must “escape” it by using two back-slashes, as shown in this example.
Note that all lines except the last end with a back-slash. In this case, the back-slash indicates a continuation of the declaration.
If you do not specify a directory, the script will search for the driver in the <work-dir>\WIM\Windows\inf
directory.
If you prefer, you can provide a fully qualified path that specifies the location and driver, such as c:\\anydirectory\\mydrivers.inf
You can also specify a path with a filename containing a wild card, such as c:\\anydirectory\\md*.inf
, which will install all md*.inf
files found in c:\anydirectory
.
After you are finished, type run to continue, and the drivers will be added to winpe.wim
.
If you run the script again in the future, you will be prompted about whether you want to keep the build.config
file or replace it with a new one. Also, the script will pause automatically. If you do not have additional packages or drivers to add, simply type run to continue.