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.
Tip: If QRUN.g4b suggests an alternate file extension, enter A for Ask.
WinPE (Vista/7/8/10) non-WinBuilder ISOs
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.
WinBuilder ISOs (Gandalf, ChrisR PEs, etc.)
Please update to E2B v1.90 or later.
E2B will automatically update the .INI files in the root of the E2B drive if a WinBuilder ISO is detected.
You must keep the filename extension as .ISO and the filename must not contain any spaces.
This .ini file (e.g. \Win7PESE.ini) is usually written together with the .iso file in the WinBuilder ISO build folder by the WinBuilder make scripts when the ISO is made.
- ISO boots to WinPE
- Internal script looks for a specific .ini file using MountPEMedia.exe + MountPEMedia.ini - e.g. \WIN10PESE.ini (or drive with \CdUsb.Y file)
- Win10PESE.ini file contains path of where to find the ISO file
- Internal script loads the ISO file as virtual CD drive Y: (usually needs a .iso file extension and no spaces in name to work)
- Desktop icons + applications will now run correctly from Y:
IMPORTANT: WinBuilder ISO file names must contain no spaces.
The ISO may not be loaded as Y: if the filename contains spaces!
The file name must end with a .iso file extension or else it may not be loaded as the virtual CD Y: drive correctly.
Do not use .isodefault or .isodef or any other file extension as it may not work - you can use a .mnu file (see below).See this page for how to suppress the auto-suggest text.
How to tell if it has worked correctly
You must check to see if you have a Y: virtual CD drive present in Explorer (even if you do not get a Yellow warning triangle).
How to find the correct name of the .ini file for each ISO
Tip: If the WinPE ISO prompts you to 'Press ENTER to boot from CD\DVD', you can permanently fix this by changing the file extension to .isoBF (BF='Boot fix') - then boot to the ISO - then quit and rename the ISO file back to it's original file extension. This will patch the ISO file.
E2B + Multiple WinBuilder ISOs (Removable and Fixed-disk drives)
Using a .mnu file for non-standard .ini files (E2B v1.90+)
Using a .isoWB and WB folder (old, more complicated method!)
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) - do NOT uses any spaces in the filename.
Use an ISO filename of less than 20 characters with no spaces - e.g. Gandalf_WinPE_x64.isoWB is 17 characters.
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!):
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 (older method - even more complicated!)
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.
title WinBuilder ISO \n Use for most WinBuilder PE ISOsset ISO=Win7PE_x86.iso/%grub%/qrun.g4b force.iso01 /%ISO%boottitle 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
For 'vanilla' PE ISOs which don't use Y: (*Removable E2B USB Flash drives only)
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 driveset POSTCMD= %~pn0_Custom.cmd
set ISOLETTER=S:REM run \_ISO\WINPE\Winpe\xyz.cmd after the ISO file has been loaded as a virtual driveset 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 driveset 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 driveset POSTCMD=S:\xxx\yyy\zzz.cmd
Shortcuts.exe -f %SystemDrive%\Windows\System32\Win7PE.cfgPinTool.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
for /f "skip=1 delims=" %%i in ('wmic cdrom get drive') do set letter=%%i && goto :end
Note: If you also add a .txt file for each ISO, then you can change the menu text displayed for each file.
To support this site, please disable AdBlock for this domain.
Recommended for Easy2Boot - SanDisk Extreme SDCZ80-064G-G46
BitCoin also accepted.