Tuesday, 23 July 2019

E2B v1.B5a Beta now available

Booting Windows NT6 .VHD and .WIM files

Previously although .wim and .vhd files did not need to be contiguous, their file extension had to be unaltered so you could not use a file extension of say .wim64 so that it would only be listed on 64-bit systems, or perhaps  Win7Ult.vhd64ncq so that it would only be listed on 64-bit systems and so E2B would not complain about the fact that it was not contiguous.

Filename override suffixes

You could get around this restriction by using the filename override suffixes - e.g. Win7Ult_.vhd64ncq.vhd.

The filename extension suffix scheme of:


is mainly used for .iso files which have to keep their file extension as .iso because when they are booted, the startup files look for a file ending in '.iso' and typically mount the ISO file as a virtual CD drive so that the files inside it can be accessed.

E2B extension suffixes (not case sensitive)

E2B v1.B5a Beta removes this restriction with .vhd and .wim files, so you can use now also these extra file extension suffixes.

32 - file is only listed in menu on systems with 32-bit CPU
64 - file is only listed in menu on systems with 64-bit CPU
3GB - file is only listed in menu on systems with less than 4GB of RAM
4GB - file is only listed in menu on systems with more than 4GB of RAM
pwd - user must enter a password before the payload file can be run
NCQ -  (non-contiguous+quiet), the payload will not prompt the user with suggestions, redir will be set and will not try to make the file contiguous
quiet - redir will be set so that most messages will be suppressed
quietp - redir and redirp will be set so that all messages including warnings will be suppressed

  • WinPE amd64.iso64pwd
  • Ubuntu i386.iso3GBncq
Read more: http://www.easy2boot.com/add-payload-files/list-of-file-extensions-recognised-by-e2b/

Spaces in .vhd and .wim filenames are now OK too!

I have finally fixed the problem of  .vhd and .wim files not working if they contained spaces in their filename in this new v1.B5a version too! So now you can have a file such as:

\_ISO\MAINMENU\My Super-duper WinPE 10 x64.vhd64ncq


and no need to make a .txt file... yay! :-)

P.S. The latest version includes E2B_Editor v1.0.97 which supports STAMPs (1-10) in your .cfg file (but it does not support transparency). This allows you adjust the position of any STAMPs by editing the MyE2B.cfg file and then reloading the .cfg file back into the Editor to display the new position of the STAMP.

No comments:

Post a Comment