Professional Documents
Culture Documents
===============================
Copy your payload file (e.g. .ISO, .IMA, .VHD, .WIM, etc.) to one of the E2B Menu
folders (\_ISO\XXXX).
For a simple test, just copy a linux LiveCD ISO file to \_ISO\MAINMENU folder and
then run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd.
Notes:
Windows Install ISOs ->> copy to correct \_ISO\WINDOWS\xxxx folder.
For the first attempt, DO NOT USE SPACES IN FILE NAMES (most payloads will
work if there are spaces in the filename, but some do not work).
Remember to always run \MAKE_THIS_DRIVE_CONTIGUOUS.cmd after copying all your
payload files.
Once you have a payload working, try renaming it so that it is more
'readable' in the menu or create a .txt file for it using \_ISO\TXT_Maker.exe or a
simple text editor.
The menu system and most 32-bit ISOs can be tried using \QEMU_MENU_TEST (run
as admin).cmd - but always test fully using a real system.
These 'normal' menu folders all behave identically. For instance a linux ISO will
work just as well in the \_ISO\WIN folder or the \_ISO\DOS folder.
The sub-menu entry will only appear in the Main Menu if there is at least one file
or folder inside the sub-menu folder.
For instance, if you don't want a DOS Menu - simple delete the folder contents
under \_ISO\DOS.
You can add your own sub-menu folders if you wish by using
\_ISO\SUB_MENU_Maker.cmd.
IMPORTANT: For Windows Install ISO files, the E2B USB Flash
drive must be of the REMOVABLE TYPE (not a hard disk or fixed disk).
If your E2B USB drive is a hard disk, you must also connect
a WinHelper USB Flash drive or convert the Windows Install ISO to a .imgPTN file,
otherwise you will get a 'A required CD/DVD drive device is
missing' error.
http://www.easy2boot.com/make-an-easy2boot-usb-drive/how-
to-make-a-helper-usb-flash-drive/
Tip: By using a .mnu file for each ISO, you can run any
Windows Install ISO from any Menu.
Windows 7 may not detect a USB drive if it is
connected to a USB 3 port (or has a modern USB chipset).
2.1 Examples
============
\_ISO\ANTIVIRUS
fred.iso <- will be auto-detected
fred.txt <- will be used as the menu entry title for fred.iso if present
(filename must be same)
\_ISO\ANTIVIRUS\MNU
jim.iso <- will NOT be auto-detected because not at top level of a menu folder
(must use a .mnu file)
jim.mnu <- will be auto-detected and added to the menu (filename does not need
to match the .iso)
NOTE: WINDOWS INSTALLER ISOs must go in the correct sub-folder under \_ISO\WINDOWS.
e.g. a Windows 7 Install ISO goes in \_ISO\WINDOWS\WIN7.
Windows Installer ISOs will not work correctly unless in a
\_ISO\WINDOWS\xxxx folder (3rd level).
If a .mnu file uses 'iftitle' then the test case in square brackets must be TRUE
for the menu to appear. e.g.
The menu entry 'Ubuntu 32-bit Live CD' will only be listed in the menu if
Ubuntu_32.iso is in the same folder as the .mnu file.
.mnu files are detected at the 2nd folder level and all levels below that level.
$HOME$ when used in a .mnu file means 'current path of this .mnu file' - e.g.
/_ISO/ANTIVIRUS.
$NAME$ when used in a .mnu file means 'filename, without extension, of the .mnu
file' - e.g. Ubuntu_32
You can use $HOME$/$NAME$.iso as a 'portable' file specification.
In this case, the .mnu filename must match the .iso filename.
Any text after \n in a 'title' line, defines the help text that appears under the
menu.
For examples of .mnu files, see the \_ISO\docs\Sample mnu files folder.
Comment lines must begin with the # symbol.
The filename of the .txt file must exactly match the name of the payload file (e.g.
ubuntu123.iso and ubuntu123.txt).
.txt files only work at the 2nd folder level in Menu folders (\_ISO\xxxx) or in the
\_ISO\WINDOWS\xxxx folders
Any characters after \n defines the content of the help text that appears under the
menu (max 4 lines)
You can use the \_ISO\TXT_Maker.exe Windows GUI to create .txt files.
3. MORE INFORMATION
===================
If a .mnu file is placed in a valid menu folder at \_ISO\xxxx (2nd level) or
anywhere below, it will be auto-detected by Easy2Boot.
WARNING: If a .mnu + .iso file are both placed in \_ISO\xxxx, you will get TWO MENU
ENTRIES, one for the .mnu file and one for the .iso file.
For this reason, typically an ISO file and .mnu file are usually both placed at the
3rd level - e.g. \_ISO\LINUX\MNU\ or \_ISO\LINUX\ANY_NAME\.