XP WinPE ISOs

For ISOs based on Windows XP, try a file extension of .isofira or .isomemF01. You can also try the .isowinvh and .isoHW file extensions.
 

WinPE (Vista/7/8/10) ISOs

For WinPE ISOs - use .ISOPE01 file extension (if E2B drive is a Removable USB drive). Try also .isoHW.
If your E2B USB drive is a hard disk drive, convert the ISO to a FAT32 .imgPTN file (also works for Removable Flash drives too).
 
Note: You can make .imgPTN partition image files from each ISO file and you don't need to 'fiddle' with INI files, etc., however the contents of the E2B partition will not be accessible once booted to WinPE. But, if you use the .imgPTNLBAa23 file extension, then partitions 2 and 3 of a E2B USB hard disk will be accessible from WinPE.
 
For some Vista/7/8/10 PE ISOs you can use .ISO (or you can try .ISOPE or .ISOPE01, but these need a removable USB flash drive or Helper drive).
 

WinBuilder ISOs

Most WinBuilder-based ISOs will load the ISO file as drive Y: when the Desktop loads. To do this, WinPE needs to be told where the ISO file is.
 
For this purpose, most WinBuilder WinPE ISO files based on Vista/7/8/10 also require the use of the WinBuilder .ini file so that all the Desktop icons and programs are available. This .ini file (e.g. Win7PESE.ini) is usually found together with the .iso file in the WinBuilder ISO build folder.
 
Many WinBuilder PE's will display a yellow warning triangle with an exclamation mark icon on the Desktop if it fails to load all the desktop icons (see screenshot below). If you double-click on the yellow triangle Desktop icon, and search the text file that is loaded, look for an ExternalIniFileName= entry (e.g. WIN10PESE.ini). This is the specific name of the .ini file that WinPE is looking for.
 
       The yellow triangle icon indicates that some programs/features failed to load due to no .ini file being found.
 
For example, if you have a recent WinBuilder PE .ISO file from a Win7SE project build, the X:\Windows\system32\mountpemedia.ini file will specify an external INI file name of \Win7PESE.ini, so just add a file in the root of the E2B drive called Win7PESE.ini with the path and filename of the ISO you are using - 
 
Example \Win7PESE.ini
[IsoInfo]
IsoName=\_ISO\MAINMENU\Win7PE_x86.ISO
 
The filename of the .ini file used by the WinBulder PE ISO may vary depending on what PE build you are using.
 
However, this will only work as long as you have just one WinBuilder PE ISO of each type (e.g. Win7PESE) on your E2B drive because, for example, you can only have one Win7PESE.ini file and thus only boot to one WinBuilder Win7PESE type of ISO file. See below for how to have multiple WinBuilder ISOs using the .ISOWB file extension.
 

How to find the correct name of the .ini file for each ISO

 
Boot as a .ISO file and then double-click the yellow Desktop icon (see screenshot above) to find the ExternalIniFileName= entry.
 
Most WinBuilder PE builds have the file X:\Windows\system32\mountpemedia.ini built into the boot.wim file when WinBuilder makes the image. You can look at this file once the WinBuilder PE has booted, to see what it contains (see below). This file tells WinPE what the name and location of the PE ISO is, so that it can load it as drive Y:. However, this file also specifies an external INI file which WinPE will also look for. It is this external INI file that we need to provide on the E2B USB drive, but it must be of the same name that is specified by the mountpemedia.ini file - so check the X:\Windows\system32\mountpemedia.ini file if PE fails to load all Desktop icons.
 
Example X:\Windows\system32\mountpemedia.ini file showing where the external INI filename is specified.
[Settings]
ProjectName=Win7PESE
MountDrive=Y:
SearchFlagFile=Yes
FlagFileName=CdUSB.Y
SearchExternalIniFile=Yes
ExternalIniFileName=Win7PESE.ini    <<<<<< name of ini file used by WinBuilder ISO
DesktopWarningLabel=Win7PESE Warning
 
[IsoInfo]
IsoName=Win7PE_x86.ISO
 
[OnError]
Line1=CdUSB.Y or ISO NOT found !
 
The X:\Windows\system32\mountpemedia.ini file specifies an ISO file - in this case the WinBuilder PE ISO will look for \Win7PE_x86.ISO and so it will not find it. However, it also specifies the name of an external INI file which it expects to find at \Win7PESE.ini. We therefore need to ensure that this file is present on the root of the E2B USB drive and that it contains the true location of our ISO file.
 
 
 

E2B + Multiple WinBuilder ISOs (Removable and Fixed-disk drives)

If you have several ISOs that have been created by the same WinBuilder project (for instance you have Win10PESE_x86 and Win10PESE_x64), you can use the .isoWB file extension for each ISO as described below (E2B v1.30 and later):

1. Copy the .INI file used by your WinBuilder ISO (or make one) to the root of the E2B USB drive - this file is usually found in the same folder as the ISO when made by WinBuilder. e.g. \Win7PESE.ini. The contents of the file are not important, but the file name is critical and must not be changed - it must be the same name that is looked for by the WinBuilder ISO.

2. Add extra spaces to the .ini file using NotePad to make a larger file (e.g. by adding 100 spaces to the end of it).

The .INI file MUST be at least as big as the .WB file that you are going to create.

3. Copy your WinBuilder PE .ISO file to the desired menu folder (e.g. \_ISO\MAINMENU or \_ISO\WINPE) - avoid spaces in the filename if possible.

4. Rename the ISO file extension to .isoWB (e.g. \_ISO\MAINMENU\WBPE.isoWB)

5. Make a subfolder called WB (e.g. \_ISO\MAINMENU\WB)  - the sub-folder MUST be named WB - this cannot be changed.

6. Create a text file in the WB folder with the same name as the .isoWB file but with a .WB file extension - e.g. \_ISO\MAINMENU\WB\WBPE.WB)

The contents of the .WB file should contain two lines (the text in red should be changed to match the name of the .INI file used by your WinBuilder ISO (the one you made in the root of the E2B drive in Step 1), make sure you keep the case of the word IniName the same, don't use ININAME or ininame - only IniName will work!):

!BAT
set IniName=
Win7PESE.ini

7. (optional) Create a .txt file for the .isoWB file so that the menu entry is not just displayed as the filename, e.g.

title My WinPE ISO\n Boot the ISO using Easy2Boot

Example File Structure for ChrisR's Win10PESE project (must use a WB sub-folder)

\Win10PESE.ini                                                       <-- must be over 1KB (any contents inside - it is overwritten by E2B)
\_ISO\WINPE\Win10PESE_x86.isoWB                 <-- WinBuilder PE ISO renamed to .isoWB
\_ISO\WINPE\WB\Win10PESE_x86.WB              <-- text file containing the name of the INI file used by the PE ISO (see step 6 above). Filename must match the .ISO filename.

For another example using WinPE-Yol.iso - see my blog article here.
 

Use a .mnu file for multiple WinBuilder ISOs

If you prefer, you can instead use the .mnu file in the \_ISO\docs\Sample mnu files\WinBuilder_PE_Multiple_ISOs folder (v1.30 and later) for each WinBuilder PE ISO file.

Details are inside the ReadMe.txt file. 

Note: The .WB file goes in the same folder as the .iso file when using a .mnu file.

Please note, if using pre-v.1.71 E2B versions, the INI file needs to be about 1000 bytes or larger if your E2B USB drive is an NTFS volume.
 

An alternative way to boot WinBuilder or WinPE ISOs

Note: For this method, all the WinBulder .ISO files need to be in the root of the E2B drive. They must not be renamed. No INI file is required.

1. Ensure there is no \Win7PESE.ini file (or whatever is used by the PE ISO) or \CdUSB.y file in the root of any drive. Delete them if they exist
2. Copy your WinPE ISO file to the root of you E2B drive - e.g. U:\ - do NOT rename the ISO file
3. Copy the WinBuilder_ISO.mnu file to an E2B menu folder (e.g. U:\_ISO\MAINMENU\MNU)
4. Rename and edit the .mnu file (any name xxxxxxx.mnu will work!) to contain the correct ISO name of your WinBuilder PE ISO. Delete the menu entry that is not required .from the example below
 
WinBuilderPE_ISO.mnu
title WinBuilder ISO \n Use for most WinBuilder PE ISOs
set ISO=Win7PE_x86.iso
/%grub%/qrun.g4b force.iso01 /%ISO%
boot
 
title WinBuilder ISO + Load ISO as new drive letter \n Use for WinBuilder PE ISOs\n which don't auto-load the ISO as Y:
set ISO=Win7PE_x86.iso
/%grub%/qrun.g4b force.isope01 /%ISO%
boot
 
Repeat these steps for each WinBuilder ISO. Note that the second menu requires an E2B USB Flash drive (or an E2B USB HDD+USB Flash 'Helper' drive).
 
If you are using WinFE (see here for how to make a WinFE ISO), in order to get PStart to work correctly, you will need to Mount the E2B USB drive using the WinFE Write Protect Tool that will automatically run on startup (it can be mounted as ReadOnly or Read\Write).
 
If you want the ISOs to be located in \_ISO\MAINMENU\MNU then you will need to specify the path in the WinBuilder - Finals - Create ISO parameters before you click on the Play arrow, as shown below:
 
The ISO (WinFESS.ISO in this case) must be placed in the \_ISO\MAINMENU\MNU
The path in the .mnu file must also be changed.
 
 

Gandalf WinPE ISOs

This can be added to E2B as a FAT32 .imgPTN file and will then MBR or UEFI-bot (if supported).
Another way to boot it, is to rename the ISO to it's original WinBuilder name of \WIN10PESE_x64.ISO (for the 64-bit version) and place it in the root of the E2B drive. Then copy the file "\_ISO\docs\Sample mnu files\Windows\WinBuilderPE_ISO.mnu" to a suitable menu folder (e.g. \_ISO\WIN) and then edit it with the correct ISO name.
 
\_ISO\WIN\Gandalf.mnu
title Gandalf 10 x64\n Boot to Gandalf PE
set ISO=WIN10PESE_x64.iso
/%grub%/qrun.g4b force.iso01 /%ISO%
 
Note that this only allows you to have one ISO on the E2B USB drive of that name, so you cannot add more, similar WinBuilder ISOs unless you use the E2B .isoWB file extension.
 
This can be added to E2B as a FAT32 .imgPTN file (details as in previous blog here).
 
 
 
 
Another way to boot it, is to rename the ISO to it's original WinBuilder name of \WIN10PESE_x64.ISO (for the 64-bit version) and place it in the root of the E2B drive. Then copy the "\_ISO\docs\Sample mnu files\Windows\WinBuilderPE_ISO.mnu" to a suitable menu folder (e.g. \_ISO\WIN) and then edit it with the correct ISO name.
 
\_ISO\WIN\Gandalf.mnu
==================
title Gandalf 10 x64\n Boot to Gandalf PE
set ISO=WIN10PESE_x64.iso
/%grub%/qrun.g4b force.iso01 /%ISO%
 
Note that this only allows you to have one ISO on the E2B USB drive of that name, so you cannot add more, similar WinBuilder ISOs unless you use the E2B .isoWB file extension.
 

For 'vanilla' PE ISOs which don't use Y: (Removable E2B USB Flash drives only)

E2B recognises a special file extension of .isoPE and .isoPE01. These can be used for WinPE v2 (Vista), v3 (Win7) and v4 (Win8/10) based .iso files. If you use the .isoPE file extension AND the E2B boot drive is a Removable USB Flash drive (or you have a 'Helper' USB flash drive) then, when wpeinit runs to initialise the network when the WinPE ISO boots, the WinPE ISO file will be mounted as a virtual DVD drive and given the letter Y: by default. This means that for WinPE (e.g. WinBuilder) projects, you can boot directly from a .isoPE file and the auxilliary files which the WinPE environment expects to find on the Y: DVD drive, will be present on the Y: drive. Thus the PStart menu items, etc. should work as if it had booted from a DVD.
 
If you wish to have the ISO load as a different drive letter, then you need to make a new file with the same filename as the ISO but with a .cmd file extension (in the same folder as the .isoPE file).
 
e.g. \_ISO\MAINMENU\PE3x86.cmd  if the iso was at \_ISO\MAINMENU\PE3x86.isoPE01
 
The .cmd file should contain a line similar to the one below:
 
set ISOLETTER=S:
 
In this way, you do not need to remember what drive letter each different ISO uses, once you have made the .cmd files for each of your WinPE ISO files.

If you require a .cmd file to run some operations after the ISO has been mounted but before PE has fully loaded (e.g. to copy files, etc.), you can define a POSTCMD variable, e.g. if the ISO was called  \_ISO\WINPE\Winpe\123.iso, then here are 4 different examples of what could be in your 123.cmd file:
 
set ISOLETTER=S:
REM run \_ISO\WINPE\Winpe\123_Custom.cmd after the ISO file has been loaded as a virtual drive
set POSTCMD= %~pn0_Custom.cmd
 
set ISOLETTER=S:
REM run \_ISO\WINPE\Winpe\xyz.cmd after the ISO file has been loaded as a virtual drive
set POSTCMD= %~p0xyz.cmd
 
set ISOLETTER=S:
REM Run a cmd file from the E2B USB drive after the ISO file has been loaded as a virtual drive
set POSTCMD=%USBDRIVE%\xxx\yyy\zzz.cmd
 
set ISOLETTER=S:
REM Run a cmd file from the ISO after the ISO file has been loaded as a virtual drive
set POSTCMD=S:\xxx\yyy\zzz.cmd
 
For WinBuilder PE ISOs, you can force it to load the Desktop icons by having a .cmd file on the E2B drive containing the correct commands - e.g.
 
Shortcuts.exe -f %SystemDrive%\Windows\System32\Win7PE.cfg
PinTool.exe -debug %SystemDrive%\Windows\System32\Win7PE.cfg

The .isoPE01 file extension has the same affect as the .isoPE extension, except that it swaps over the USB boot drive 0 with drive 1 (the internal HDD) before booting to the ISO (BIOS swap only). This may be useful for running WinPE ISOs that normally contain recovery software which expects HD0 to be the 'system' HDD.

Example .cmd file to replace an existing CD-ROM drive letter with that of the ISO

123.cmd
=====

@echo off
for /f "skip=1 delims=" %%i in ('wmic cdrom get drive') do set letter=%%i && goto :end
:end
set ISOLETTER=%letter%:

Thanks to (NF) for this example.

Note: If you also add a .txt file for each ISO, then you can change the menu text displayed for each file.
 

 





More Info