How to add a DIY script for WinPE

The PE system provides three ways to start custom scripts: Winpeshl.ini, Startnet.cmd, and Unattend.xml. The default interface for the original eco-winpe system is the command prompt window, but you can create a custom Winpeshl.ini file to run your own shell application. You can also create your own Startnet.cmd batch file to run a specific set of commands, batch files, or scripts. Unattend.xml is the new answer file format for WinPE 2.0, which replaces Winbom.ini and Winpeoem.sif.

　　first, use Winpeshl.ini to add custom scripts :

You can use a Winpeshl.ini file to start a custom shell application. Winpeshl.exe will process the settings in Winpeshl.ini during startup. Use a text editor, such as Notepad, to create an Winpeshl.ini text file with the following file directory structure. For example:

[Launchapp]

AppPath =%systemdrive%myshell.exe

[Launchapps]

%systemdrive%mydirapplication1.exe,-option1-option2

Application2.exe,-option1-option2

Note: Set the AppPath entry as the path to the shell application. This path can be an absolute path, or you can use an environment variable (relative path), such as%systemroot%system32myshell.exe. command line options are not supported for apppath items. Save this file to the%systemroot%system32 of the WinPE system image.

　　Ii. Add custom scripts using Startnet.cmd:

Use Startnet.cmd to add custom command-line scripts to the WinPE system. By default, the WinPE system includes the Startnet.cmd script, which is located in the%systemroot%system32 of the WinPE system image. Currently, the main use of Startnet.cmd to start Wpeinit.exe. Used to install Plug and Play (PnP) devices, process Unattend.xml settings, and load network resources. Edit Startnet.cmd to include custom commands.

Note: For PNP and network support, make sure that you include a call to Wpeinit in your custom Startnet.cmd script.

　　Use Unattend.xml to add custom scripts:

Run Imagex/info d:boot.wim To view information about the WinPE system image. We should pay attention to this line:

Image Count:2

Explains that the WinPE system image file contains two images in fact. Detailed information about each image is described later. The special point here is that we need to edit a second image called WDS because WDS uses this image to boot the computer.

MOUNTRW the *.wim into the Pemount directory using the ImageX command plus the parameters:

IMAGEX/MOUNTRW C:winpe2pe2.wim 2 C:pemount

Use the peimg command to add third-party drivers to the WinPE 2.0 system, repeat this step if you need to add multiple device drivers.

Peimg/inf=c:winpe2netdrvxxx.inf c:pemountwindows

Use the ImageX command plus the parameters unmount and commit to write the modifications to the *.wim.

Imagex/unmount C:pemount/commit