Boot all your ISO's from one USB drive!
How to make an E2B USB drive, click here. Then just copy over all your ISO files and boot!
List of tested ISOs here. There is no limit on the number of ISOs and Windows Install ISOs or other payload files you can add.
Example themes (skins), see here.
Easy2Boot Forum is here.
Want the latest version? - see bottom of page.
Please subscribe to my blog for changes, bug fixes and news.
Easy2Boot can do all of these things - no other USB MultiBoot solution can do all of this from the same USB drive!
1. No limit to the number of different Linux, Windows Install, WinPE, etc. ISOs or other payload files
2. Boot almost ANY linux 'LiveCD' ISO - just copy it over! Unlike XBOOT or YUMI, you don't have to wait for Easy2Boot to be updated to support a new linux ISO distro - Easy2Boot is generic.
3. Install Windows XP to a system from a UNMODIFIED XP install ISOs (any number of different ISOs) to a IDE\SATA\AHCI\RAID\SCSI system - no need to integrate special mass-storage or F6 drivers! Also works with Server 2003 ISOs.
4. Install from any number of different Windows Vista/7/8/SVR2008R2/SVR2012 install ISOs
5. Boot directly from linux LiveCD ISOs with persistence - you can have all these (and more) on one Easy2Boot drive and boot them all with persistence - YLMF, Ubuntu, Fedora, StartOS, Porteus, pclinuxos, Backtrack5, kali-linux, Tails ISOs.
6. User configurable - you can change the background wallpaper, headings and text colours, move the menu position, make your own sub-menus, make it beep when the menu loads, add your own GFXBoot menu, define your own hotkeys, etc. etc.
7. You can use a FAT32, NTFS, exFAT or ext2 formatted Easy2Boot drive
8. Because Easy2Boot is not a 'utility', you can prepare an Easy2Boot drive under Windows or linux. Once prepared, just copy over (or delete) any ISOs you like at any time in the future.
9. Variety of example 'skins' included.
10. It's FREE!
Any Problems? - Contact Me
I have put a lot of hours of hard work into Easy2Boot and it is totally free!
<- If you use E2B, please consider making a donation, it would be much appreciated
When a new Upgrade Package becomes available, anyone who has made a donation will get it before everyone else!
Comments from users on forums/blogs,etc:nyquist - 'Easy2boot is awesome. Thanks for sharing this software with us.'
Rootman - 'This is one of the coolest things I've run across in a long time. You guys have GOT to check this out.'
maanu - please accept my congratulations on coding this beautiful tool.. my 1st experience was GREAT. it worked flawlessly on very 1st try (win8 64-bit install)
Jkplayschess - This is a fantastic tool! I rarely get excited about things, but I'm following the development of this closely!
sebus - The solution works VERY well indeed. Tested on W7 x64 so far
Weedy - I gotta say I'm annoyed that this tool seems to work exactly as advertised! This tool is a fantastic piece of software.
Sebastian - finally I found something amazing awesome that exceeded all my expectations: Easy2Boot - thank you! (private email)allcoms - unetbootin only allows you to boot one ISO per USB drive - easy2boot lets you boot as many ISOs as you can store on your drive and adding new ISOs is as simple as copying them into the correct folder so its platform neutral in that respect, not requiring you to run an updater as you do with say YUMI, which is Windows only. I have tried other Linux-friendly apps (multisystem etc) that have claimed to do this but none of them worked properly. Every ISO I have tested with E2B has worked 100% and I have tried at least a dozen distros, diagnostic and recovery ISOs with it now.
XBOOT (sadly no longer supported), Sardu, YUMI/PendriveLinux and other utilities are very good at what they do, but often you find that they don't work with a few of your ISOs, or they don't work with the latest version of a particular ISO and you have to wait for them to be updated. You can also find it difficult to manually add the ones that don't work and it is often not easy to know how to modify the menus. You also have to re-run the utility each time you make a change, or you have to download a new version of the utility and completely re-make the USB stick again, just to add or remove one ISO.
Easy2Boot Version 1 is just a collection of files that you can add to a grub4dos bootable USB Drive - it is NOT an application. Once you have made the grub4dos bootable USB drive and copied over the Easy2Boot files, just copy over any bootable payload files (linux LiveCD ISOs, Windows Install ISOs, memory test .bin files, floppy and hard disk images, etc.). Easy2Boot automatically looks at all the files on the drive and dynamically creates a new menu each time you boot from the USB drive. Each file will be booted according to it's file extension (unlike most MultiBoot Utilities, E2B does not look at the file name and does not need to recognise what type or version of linux is inside the ISO file).
PLEASE NOTE: With Easy2Boot I talk about 'payload files' because E2B can boot other files besides .iso files. Payload files are bootable files that E2B recognises and can boot from. So in many cases, a 'payload file' is an ISO file. However, a 'payload file' can also be a .BIN file (e.g. memtest86.bin) or a .IMA file (e.g. a DOS floppy disk 1.44MB image file), or a .IMG file (a bootable disk image) or a .VHD file (a virtual hard disk image), etc. etc.
Your E2B USB drive can be formatted either as FAT32 or NTFS. ExFat will also work for most payloads except XP or Vista RTM and some WinPE ISOs, for this reason exFat is not recommended (also you may find that some systems won't boot). E2B will also bootfrom an ext2 USB drive (but Windows Install ISOs won't work). UEFI booting is not supported by the E2B menu system but you can add an EFI bootloader to the E2B USB drive manually if you wish.
Once you have made a bootable Easy2Boot USB drive, you can simply copy all your payload files (.iso, .img, .ima, etc.) to one of the payload folders on your USB drive (e.g. \_ISO\MAINMENU folder). No menu editing required, no cheat code knowledge required for .ISO booting - just copy and boot! Your USB boot drive does not need to know what the ISO file version is and will work with almost all linux liveCD ISOs that you copy over - even new ones that come out in 6 months or 3 years time should just work (you don't need to keep updating E2B on your USB drive every few months for the next release of a new linux ISO)!
E2B on a USB Flash drive works with Windows Install ISOs too! Note that if you are using a bootable USB Hard Disk instead of a USB Flash drive, then the Windows Vista/7/8 install ISOs will not work unless you also use a USB flash drive at the same time (see here for more details).
E2B also allows you to have multiple linux ISOs which can all boot with persistence all using the same (single) partition on the E2B drive. You can even boot from the same linux ISO with 2 or more different persistent file-systems from a single USB FAT32 (or even an NTFS) Hard disk!
You can add the Easy2Boot files to your existing grub4dos bootable USB drive or make a fresh install using RMPrepUSB (recommended). If using an existing grub4dos bootable USB drive, it should have a maximum of two primary partitions, or just one primary and one or more logical partitions.
E2B is configurable, you can change the background image, move the menu, change the colours, use your own GFXMenu wallpaper, change the menu text and headings (non-ANSI characters are supported), add your own sub-menus, add menu hotkeys and lots more!
If your smartphone has an SD card and supports USB Mass Storage mode, then you can use your smartphone as a bootable USB device by installing E2B. With many phones you do not need to 'root' your phone. This means you can boot a PC or notebook from your phone and run linux or WinPE or even install Windows 7 onto a PC from your phone (if your smartphone does not support this, then root it and install DriveDroid from Google Play and then install E2B as described below)!
Click here for a list of tested ISOs that work with Easy2Boot! The blog for Easy2Boot V1 is here.
Check the \_ISO\Sample_MyE2B.cfg file for any new options and tweaks.
v1.00 2013-06-18 First Release
v1.01 2013-07-05 Few bug fixes
v1.02 E2B v1.01 + DPMS2 Update Pack v 1.02 (2013-07-06)
v1.03 2013-07-11 Requires new grldr, improved alphanumeric sort (not case sensitive), bug fixes, DPMS2 + auto-selection for XP ISO install, empty folders not listed in menu
v1.04 2013-07-15 DPMS2 small bugfixes/improvements. Small changes in XP Install Step 2
v1.05 2013-08-03 Ability to suppress the file enumeration messages when creating menus on startup. Jolene sample menu added!
v1.06 2013-08-05 .mnu and payload files are now enumerated together instead of separately in two stages, so the menu order is determined by the alphanumeric filenames of the .mnu and payload files.
v1.07 2013-08-24 Recognises .isoPE file extension and mounts the .isoPE file as a drive letter (virtual CD/DVD) when wpeinit runs. BugFix in automn.g4b (some sample .mnu files did not work since v1.00!). New grldr. Full alphabetical sorting (same order as in Windows Explorer). ISOASK variable supported. POSTCMD variable for WinPE ISOs.
v1.08 2013-09-04 bitdefender mnu file added to docs folder, Windows 8.1 temporary Product Keys added, master pwd opttion in MyE2B.cfg
v1.09 2013-09-14 Some sample .mnu files revised and added, .vhdmem, imz, imggz extensions supported, set DEFMENU=0 supported for no 'set default' menu item, .txt files now checked for 'title' keyword and user warned if missing.
v1.10 2013-09-15 Bugfix for DEFMENU=0 (thanks Sergei for spotting this!), added NOUNIFONT=1 (does not load unifont font file for faster booting)
v1.10a 2013-09-25 Sample .mnu files revised (note: The E2B+MassStorageDrivers download is still v 1.10 - if you want the latest .mnu files, download v1.10a and overwrite it).
v1.11 2013-09-28 Bugfix - the Unattend.xml and AutoUnattend.xml files are now wiped on startup. NOF9R and NOF10H variables available to suppress F9 and F10 in menu.
v1.12 2013-10-17 grub4dos 0.46a used if it boots as (fd0), 100K spaces.txt removed, global hotkeys, warning if file not contiguous, fix for .iso not booting in HP's, extra variables - see Sample_MyE2B.cfg for details.
v1.13 2013-10-18 bugfixes for v1.12!
v1.14 2013-10-21 More variables for advanced menu changes, beep when main menu is loaded - see Sample_MyE2B.cfg for details. If only one XP ISO present then it is autoloaded. Same if only one xml file for Vista.Win7 installs.
v1.15e 2013-10-26 Mainly bugfixes to v1.14 and earlier versions of v1.15!
v1.16 2013-10-29 Same as v1.15e. Extra menu theme for beep demo added. DPMS integrated download with v1.16 available.
v1.1.7 2013-11-15 .isoDOS extension supported for DOS-based ISOs. Checkaccess can be suppressed using a MyE2B.cfg setting. Some changes to finding of \autounatend.xml and \unattend.xml files.
v1.18 2013-11-30 .isoDOS01 extension, extra font support and 34 different fonts added (see Sample_MyE2B.cfg), grub4dos version 0.4.6a used
Thanks to the following people for their help through all 30 Beta's!
Fabrizio and Antonio, Halikus, llbranco, Weedy, Rootman, Administrator, Weidass, Corey, Dave N, Tomas, Whiznot, alacran, nyquist, moot, Nexes Senex, Krishna (and anyone else I have missed)!If you think I have not yet fixed any issues (due to an oversight) please email me!
Video. 1 - Introduction to Easy2Boot
Video. 2 - Installing Windows XP using E2B
Fig. 1 Easy2Boot screenshot (items 1-4 is due to added ISOs, item 17 is present because FASTLOAD has been enabled).
The menu hotkeys are shown in [square brackets].
For linux users see here.
For Windows users:
1. Download and install the latest version RMPrepUSB
2. Download Easy2Boot (either the basic download or E2B+XP MassStorage drivers)
2. Insert USB Flash drive
3. Run RMPrepUSB and tick the 'No User Prompts' checkbox and select:
4. Click on Install grub4dos button - answer 'No'=PBR.
5. (only if it fails to boot) Repeat step 4 but answer 'Yes'=MBR
6. Copy your linux ISO files to \_ISO\MAINMENU folder or \_ISO\LINUX folder.
Copy your Windows Install ISOs to correct folder under \_ISO\WINDOWS\xxxxxx.
Copy any other bootable files to \_ISO\MAINMENU folder.
7. Press CTRL+F2 in RMPrepUSB to make all file contiguous (or you may get Error 60).
You can now boot and test the USB drive on a real system (or press F11 in RMPrepUSB to boot it using the QEMU emulator.)
8. If any files don't boot properly:
If they are ISO files, rename the extension to .isoask and try the various options offered when you run them.
If they are not ISO files or you are still having problems, look in the \_ISO\docs folder for a special .mnu file and read the instructions inside or search for it on this page.
To make a new bootable E2B USB drive:
The steps below in outline are:
Note: If you are a linux user, format a USB Flash drive and then install grub4dos using bootlace for steps 1 and 2 (use the version of grldr included in the download).
'danboid' suggests using defragfs to make the ISO files contiguous under linux. See Tutorial 114 for full details on how to prepare an E2B USB drive under linux.
For Windows users, you are recommended to download and install the latest RMPrepUSB (or use the portable version if you prefer). Use RMPrepUSB v 2.1.710 or later.
FAT32 is recommended for USB Flash drives, however if you know that you have ISO files that are over 4GB, then you must use NTFS. exFAT is not recommended because some XP-based ISOs and Windows XP/Vista SP0 Install ISOs will not work and you may find some systems won't boot.
Fig. 2 RMPrepUSB partition&format options
Note: If you have a small USB flash drive, I would recommend you use FAT32 as it is easier to defrag the files on it using WinContig (Press Ctrl+F2 in RMPrepUSB) and it can be accessed by most OS's. However, if you have a large USB flash drive or a USB HDD, then use NTFS. NTFS will also give faster file I/O performance in most cases.
Tip: Use FAT32 if you want to boot Hirens or DLC1 as it may not be able to access the folders on the USB drive once it boots (unless you use the .isomem file extension for the iso file).
If you have a USB Hard disk, you can create multiple partitions (e.g. using EaSeus Home Partition Manager or Windows Disk Manager), but do not create more than 1 Primary+1 Extended OR 2 Primary partitions. E2B needs the 3rd and 4th MBR partition table entries free (the 3rd ptn is used by some linux+persistence .mnu files that are available in the \_ISO\docs\Sample mnu files folder).
Make sure that your USB Flash drive is listed by RMPrepUSB as a (Removable) and not as (Fixed Disk). If you have a new USB Flash drive (e.g. certfied for WinToGo) that is listed by RMPrepUSB as (Fixed Disk) or 'Local Disk' by Windows Explorer, then your USB Flash drive will appear to Windows as if it was a hard disk and not a removable flash drive. In this case, if you want to use E2B to install Windows Vista/7/8 ISOs you will need to add another auxiliary USB flash 'helper' drive when you boot from a Windows install ISO - otherwise you won't get the blue FiraDisk console window. Follow the instructions here.
2. Untick 'No User Prompts' and click the Install grub4dos button (see '2' =>' in Fig. 2 above) and install grub4dos to the PBR (answer 'No') and copy over the grldr file (optional). You must use the version of grldr that comes with E2B and so this grldr will be overwritten in step 3 below anyway.
Extract the files the root (top level) of the USB Flash drive using 7Zip. Always use the latest (most recent) version of grldr if prompted to overwrite the grldr file. Your USB drive should now contain a \_ISO folder in the root plus many sub-folders and a few odd files in the root.
4. (optional) - If you want to install XP from an XP Install ISO to AHCI/SATA/RAID/SCSI systems and you did not download the E2B+Windows XP Mass Storage Drivers [30MB] download in step 3, you can add the Mass Storage drives at any time later on - see Tutorial 72b for details.
5. You can now test that it boots and you can see the E2B menu by pressing F11 in the latest version of RMPrepUSB (answer 0 for the hard disk size and up to 1000 MB for the memory size if prompted). Some things may work (e.g. memtest), but to test ISOs you will need to test on a real system as they may not work under QEMU (and will be slow too)! Oracle Virtual Box can be used to successfully boot most ISOs from E2B (see Tutorial 4 for details).
The latest versions of RMPrepUSB (v2.1.708 or later) have full read/write support for USB drives under QEMU and will boot ISOs much more successfully than the older versions of RMPrepUSB or QEMU Manager.
Note: If you find that some systems do not boot and display a 'BOOTMGR is missing' message, repeat Step 2 but install to the PBR as well as the MBR (thanks to llbranco for this tip!).
If you are using a 2013 or later computer to boot from the USB E2B drive (for example, a computer that was originally pre-installed with Windows 8), you may need to change the BIOS Setup Menu boot option to set it to BIOS Legacy or CSM boot mode - otherwise it may not list the E2B USB drive as a bootable drive in the BIOS drive list.
2. Run WinContig:
For linux users, 'danboid' suggests using defragfs to make the ISO files contiguous.
Be aware that a 'Disk Defrag' is NOT the same as making all files contiguous - in fact some disk defrag utilities will make previously contiguous files non-contiguous. Do NOT run disk defrag on the Easy2Boot USB drive once all files are contiguous or you may start to get Error 60 again.
Now boot from your USB drive! That's it!
Tip: Any payload (e.g. .ISO) files that you add will just be listed by their filename in the menu. You can easily change the menu entry for each ISO by adding a small .txt file of the same file name but with a .txt extension - see here for details.
This means if you have an .ISO file plus it's .mnu file, do NOT put them both at the 2nd \_ISO\xxxx level because both the ISO and the .mnu file will be added to the menu!
Instead, place both files at the 3rd \_ISO\xxxx\yyyy level - then the ISO file will not be listed in the menu, but the .mnu file will be added to the menu.
Note: This rule does not apply to the \_ISO\WINDOWS and \_ISO\AUTO folders which are 'special'.
Please note: If testing using a VM - Windows Vista/7/8 installs from an ISO will not work when using an emulator such as QEMU or a Virtual Machine. You will get a 'CD/DVD driver required' message - see here for details on how to install Windows Vista/7/8 to a virtual harddisk from E2B when using a VM.
Note: To speed up the loading of the Main menu, enable caching using FASTLOAD.
To change the E2B menu, look in the \_ISO\Sample_MyE2B.cfg for details of the configuration options available (these are always updated with each new version).
If you have any problems or need more information, then keep reading...
I have used a .mnu file for persistence with a linux ISO, but I don't get persistence.You MUST run WinContig after preparing the USB drive and making the ext2 file - all files including the ext2 file need to be contiguous.
Check that you have created the ext2 file according to the instructions in the .mnu file (you can now use the latest RMPrepUSB version 2.1.711+ which allows you to set the filename and volume name separately).
I have updated to version 1.06 and now I get duplicate Main menu entries!
Delete the old \_ISO\MAINMENU\SubMenuxxx.mnu files and the mainmenu.mnu file.
How do I add an XP/Server2003 Install ISO?
Copy the ISO file to \_ISO\Windows\XP folder. To install it, you can either use the Step1/2 menu entries or use the WinPE install method (requires another WinPE ISO to be added).
How can I install XP/Server2003 to an AHCI/SCSI/RAID PC using a standard Install ISO?
You need to copy the Mass Storage driver pack files to the E2B USB drive (the Install ISO files can remain unaltered)- see here for details.
How do I add a Windows 7 Install ISO?
Copy the ISO to \_ISO\Windows\Win7 folder
How do I add a Windows 8 ISO?
Copy the ISO to \_ISO\Windows\Win8 folder
I made a USB Hard disk with Easy2Boot, but when I try to install Windows 7/8, it asks for a CD drive driver
E2B requires a USB 'removable' flash drive for Vista/7/8 installs. You will need to also make and connect a small 'Helper' USB Flash drive if you want to use a USB Hard disk for E2B.
How do I add a Hirens Boot CD ISO and get it all working?Most Hirens menu items will work just by renaming the .iso file to .isowinvh but most of the DOS Utilities require the \HBCD\Dos folder on the E2B drive. Kon-Boot won't work if booting from an ISO because hd0 will be the USB drive and not the internal HDD - use the HirensISO.mnu file in the \_ISO\docs folder for better ISO booting. To get the HBCD Menu program in MiniXP working, browse to the Hirens ISO on the e2B USB drive - right-click and Mount as ImDisk Virtual Disk. Then run \HBCDMenu.cmd from the mounted ISO.
How do I add YLMF/Ubuntu/Fedora/StartOS/Porteus/pclinuxos/Backtrack5/kali-linux/Tails ISOs and have persistence?
See the relevant .mnu file in the \_ISO\docs\Sample mnu files folder
How do I add the ERD2005 ISO?
Copy the ISO file to \_ISO\UTILITIES\Windows folder and also the ERD2005.mnu file. Read the ERD2005.mnu file in the \_ISO\docs\Sample mnu files folder for more details. You can also try using the .isope01 extension.
How do I change the menu position, colours, headings and background, etc.?To use your own image, copy to the \_ISO folder your own mybackground.bmp or mybackground.bmp.gz file (you can compress a .bmp to a .bmp.gz using 7Zip and by selecting gzip as the compression type – this greatly reduces the file size).
OR - Rename the \_ISO\Sample_MyE2B.cfg file to MyE2B.cfg. Change the MyWBMP entry or the MyWBMPGZ entry to the location of your background file. See here for more details. The MyE2B.cfg file also allows you to change the default text colours and menu position.
When I boot my E2B USB drive on some systems I get an error - but on others it is OK - why?
This is usually due to a 'bad' BIOS. First check if there is a more recent BIOS for that system on the manufacturers web site. Next, check the BIOS settings to make sure it is booting the USB drive as a Hard/Fixed Disk. Also check that your BIOS Setup menu is set for Legacy/CMS mode and not UEFI mode. If the 'check last sector' test is causing a problem, reformat using RMPrepUSB v2.1.714 or later. You can just delete the \_ISO\E2B\grub\checkaccess.g4b file (but be aware that the BIOS is still bad and so you may get other problems!).
Can I use Plop with E2B?
In a word No! In more words - Plop is a read-only USB driver that does not support writes to a USB device. As most functions of E2B (e.g. boot from ISO) involve writing to the E2B boot drive or E2B helper Flash drive, writes need to be supported for E2B to work it's magic. Therefore if you install Plop and then try to run E2B, you will probably see a 'write error' message.
How can I change the order of the menu entries listed in each E2B menu?
All items (files and folders) are sorted alphanumerically. Just rename any payload and .mnu files. Use Windows Explorer to sort the files by name (click on the top of the Name column in Explorer) and that will be the order that the files will be listed in, in the E2B menu.
Can I use E2B on my Zalman VE200/300/400 DVD emulator drive?
Yes. Install grub4dos using RMPrepUSB and add the E2B files. See this section for details of how to avoid having to rename iso file extensions. When booting E2B, the Zalman will be seen as a Fixed Disk and so you will need a USB 'Helper' flash drive for some functions (e.g. Windows 7/8 Install isos).
There are lots of possible extensions that E2B supports for .iso files - how can I find out which one is best for my iso? First search this page for the name of your particular version. If you are still having problems, name your .iso file as .isoask - you will then be prompted by E2B and asked how you want to run the .iso file. Once you find an extension that works, rename the file from .isoask to whatever entry worked best.
How do I get my WinPE ISO (e.g. WinBuilder) to see the ISO as drive letter Y: ? See the section below on WinPE ISOs.
E2B seems to pause for several minutes on boot when checking the 'last sector' or when looking for WINHELPER.USB - Re-partition the USB drive using RMPrepUSB v2.1.710 or later.
E2B won't boot .iso files on 'some' (e.g. HP) systems but works fine on all the others - Try v1.12
E2B USB Flash drive won't boot on some systems even using v1.12 - try installing a Standard MBR using the RMPrepUSB - BootLoaders tab and installing grub4dos only to the PBR. If that doesn't work, try preparing a USB flash drive using flashboot - see Tutorial 113
Most ISO files will need to be contiguous. In most filesystems, files are stored in 'clusters'. So a single file can occupy for instance, clusters 234, 235 and 236 on a disk or it could occupy clusters 99, 278 and 1081 on the disk. In the first case (234-236) we have a contiguous file because all the clusters are sequential. In the second case (99,278,1081) the file is not contiguous as it is spread across the disk in 'chunks' with gaps inbetween. To make all files on your USB drive contiguous, run RMPrepUSB and select the USB drive in the drive list, then press Ctrl+F2 to run WinContig. Alternatively download and run WinContig.
Sometimes WinContig may be unable to make all the files contiguous. This is usually because there is not enough free space on the volume.
In this case, you can either delete some large, unwanted files and run WinContig again OR it is often quicker to:
1. Copy all files from you USB drive to an empty folder on your hard drive
2. Re-partition your USB drive and re-install grub4dos
3. Copy all the files back again (use Explorer but do not use multiple copy sessions at the same time)
In some cases, if using NTFS, you may find that you cannot get a large ISO file to be contiguous on a smallish drive, even if you copy over the files to a freshly formatted NTFS USB Flash drive. In this case please read my blog here about this issue and how to fix it.
I have spent months and many hours of hard work developing and testing E2B.
Some users have generously made a PayPal contribution for E2B and so in order to reward them for their generosity, I will email them a link to any new E2B Upgrade Package before it becomes generally available.
At the moment there are no Upgrade Packs available however - all previous Upgrade Packs are currently included in E2B v1.04 and later versions.
Packages are cumulative, you only need to add the latest one to your base E2B USB drive.
I will email anyone who has kindly made a donation, with details of the latest version of the E2B Upgrade Package when one becomes available.
Tested ISO files that work with E2B are listed below - just copy the ISO files to the \_ISO\MainMenu folder - entries in bold type have been tested by me personally (note: you may need to change the file extension of a few ISOs - see here for more details). Unless a .mnu file is required, any release or version of a named ISO should work (i.e. if Kasperksy 10.0.31.4 is listed below, then any version of Kaspersky should work). If a .mnu file is required, you may need to edit the iso filename in the .mnu file to match your iso filename.
Please note: E2B is not version specific. So if say, version 4.3.2 of a particular ISO listed below works, then so should all other versions of that ISO!
tip: The ISO file names are displayed 'as-is' in the E2B menu but you can rename any ISO file to whatever name you like (or make an additional .txt file with a new menu title for each ISO).
latest version - check the Downloads at the bottom of this page for the latest version!
Once you have booted from your USB Easy2Boot drive on a REAL SYSTEM, just use the UP/DOWN/LEFT/RIGHT cursor keys to select a menu item and press ENTER or 'b' to run it. You can use the first menu item (0) to set any of the Main menu items as the default one which will be selected and highlighted when Easy2Boot first boots or reloads the Main menu. You can also set a countdown time-out to auto-run that menu entry. An invalid menu number will cause menu entry 0 to be selected.
Note: If you add more files to your Easy2Boot drive or delete files, then the menu numbering may change - this will cause the default menu item to also change. In this case you will need to use menu 0 again to set the default menu item again. If you have FASTLOAD caching enabled, then menu option 0 will also refresh the FASTLOAD cache.
Also note: Changing the default menu and enabling FASTLOAD may not work in an ordinary Virtual Machine environment which does not allow disk writes to an external USB drive - use a real system for testing! New: try DavidB's Virtual Machine USB Boot from reboot.pro which allows full rd/wr access when booting from USB using Virtual Box!
Please keep reading to learn how to add your own files and change Easy2Boot to suit you!
Always run WinContig to ensure all files are contiguous (quickly done in RMPrepUSB, just press the keys Ctrl+F2).
Note: If a folder is empty (contains no sub-folder or file), the menu entry won't appear in the E2B menu.
As a general rule:
Payload files should be copied to one of the main folders (at the \_ISO\xxx level).
If your payload file requires a .mnu file, then copy both the payload file and .mnu file to a folder UNDER one of these folders - e.g. \_ISO\LINUX\Linux (i.e. the files should both go at level 3 - \_ISO\xxxx\yyyy\fred.mnu and fred.iso).
The MAINMENU, ANTIVIRUS, BACKUP, DOS, LINUX, UTILITIES and WINPE folders all have the same function - they just exist so that you can organise your payload files nicely into sub-menus. You can copy any payload file to any of these folders and they will still work - for instance you can copy a Ubuntu linux .iso file to \_ISO\DOS and it will still boot just fine from the DOS menu.
However, .mnu files usually need to go in a specific sub-folder - for instance you can place a .mnu file that is designed to go in \_ISO\xxxx\Linux in any of these 7 folders as long as the sub-folder is named Linux (e.g. \_ISO\DOS\Linux or \_ISO\LINUX\Linux or \_ISO\MAINMENU\Linux, etc.). The variable MFOLDER will be automatically set to the second folder level \_ISO\xxxxx.
The \_ISO\AUTO folder is only for payload files and so it is special in that all .mnu files will be ignored if placed in or under this folder. However all payload files in this folder and any sub-folder under \_ISO\AUTO will be listed in the DIRECT BOOT menu. i.e. You can place 50 of your ISOs under 10 sub-folders of your own choosing and they will all be listed in the DIRECT BOOT menu.
The \_ISO\WINDOWS folder is used only for Windows Install ISO files. For instance, you must place your XP Windows Install ISOs in the \_ISO\WINODWS\XP folder and can be any name you like. If you put a Windows 7 Install ISO in \_ISO\MAINMENU, for instance, it won't work properly!
The Main Menu folder
\_ISO\MAINMENU <--- Payload files (except Windows Install ISOs) that you want listed in the Main Menu go here (and you can also add .mnu files to sub-folders below here)
Sub-menu folders: (these folders are listed as menu entries in the Main menu, if populated) - mnu files+payload files should go at level 3.
\_ISO\ANTIVIRUS <--- for any AV payloads
\_ISO\BACKUP <--- for any BACKUP payloads
\_ISO\DOS <--- for any DOS payloads
\_ISO\LINUX <--- for any LINUX payloads
\_ISO\UTILITIES <--- for any UTILITIES payloads
\_ISO\WINPE <--- for any WINPE payloads
Special payload-only sub-menu:
\_ISO\AUTO <--- for payload files only (you can use sub-folders of any name) - all .mnu files are ignored.
Windows Install ISO folders: (if any .ISO files are present a Windows entry will be listed in the Main menu)
\_ISO\WINDOWS\SVR2012 <-- Server 2012 Install ISOs go here
\_ISO\WINDOWS\SVR2K8R2 <-- Server 2008 R2 Install ISOs go here
\_ISO\WINDOWS\VISTA <-- Wndows Vista Install ISOs go here
\_ISO\WINDOWS\WIN7 <-- Winodws 7 Install ISOs go here
\_ISO\WINDOWS\WIN8 <-- Windows 8 Install ISOs go here
\_ISO\WINDOWS\XP <-- XP Install ISOs go here
e.g. If you have a linux ISO file such as ubuntu-13.04-desktop-amd64.iso and you want it to boot as a LiveCD - just copy it to the \_ISO\MAINMENU folder - that's it!
If however, you want to run this ISO with persistence, you need to also add a special .mnu file (available from the \_ISO\docs\Sample mnu files folder). Simply copy the ISO file and the .mnu file which you want to be listed in the Main menu, into the correct sub-folder under \_ISO\MAINMENU - for instance if you have ubuntu-13.04-desktop-amd64.iso and it's .mnu file Ubuntu13.04_x64_Persistent.mnu, then copy both files into \_ISO\MAINMENU\Linux (always read the .mnu file for instructions).
The \_ISO\AUTO folder, if populated by payload files, will be listed in the Main menu as DIRECT BOOT Menu. Any payload files (e.g. ISO files) and .txt files placed under this folder (or it's sub-folders) will be listed in the DIRECT BOOT menu. You can make your own sub-folders if you wish. .mnu files are ignored. This allows you to organise a large number of .iso files in different sub-folders but they will all be listed in the DIRECT BOOT menu.
The various options are described in more detail below:
Add any number of OEM/System Builder Windows install ISO files to the correct folders under \_ISO\Windows\sub-folder and name them as you wish.
Multi-language Win7 ISO files can be downloaded from Digital River (see Useful Links on this site).
You can rename the ISOs and use spaces in the ISO filenames to make them look better in the menu if you wish (or add a .txt file - see below).
NOTE: Always run WinContig to ensure all files are contiguous after copying them over (Ctrl+F2 in RMPrepUSB).
Add a .txt file to change the text in the menu
For Vista.SVR2K8R2,7,8 and SVR2012 ISOs (not XP ISOs), you can also add a .txt file of the same filename and add an alternate title (rather than have the filename listed in the menu).
If you also add a .txt file of the same filename containing a single line of text such as: title some_text_here\nsome_help_text_here, then that text will be used as the menu title instead of the name of the file itself (note that the line must start with the lower-case word 'title'). See here for more details.
Note: .iso files of 0 length are not listed (but may add to the total file count displayed in the menu!).
Add a .key file to hold Product Keys
For Win8/SVR2012, the product key can be typed in manually by the user, after selecting an ISO in the Easy2Booty menu. To use your own pre-defined set of Product Keys, make lots of .key files (copy the format from the other files) - OR if you have lots more product keys you can add all the keys to the CHOOSE FROM A LIST.key file. You can delete any .key files you don't want. Another alternative is to make a .xml file with your Product Key already in it and not use .key files at all.
Add an .xml file to automate an install
You can also have your own unattend.xml files in the same folder. This can contain all your settings and a product key - you can just choose any xml file and run the ISO. If you delete all .xml files from the Vista/7/8/SVR2012 folders, then the default unattend.xml will be automatically used and the user will not be prompted to select an xml file.
Note: For Windows XP Intall ISOs, when using the helper WinPE method, you can also define an unattend.txt file to automate the XP install (there is an example file in \_ISO\Windows\XP for an Asus EeePC install).
You can download Windows 7 Install ISO files from the link on the Useful External Links page.
IMPORTANT: For more details on how to install Windows XP using the 2-step FiraDisk method see the instructions in Tutorial #30 (hint: if you get BSOD in Step 1, try without pressing F6). You should also add the DriverPack Mass Storage drivers - details here.
For details on how to install XP using a WinPE ISO see below. This is a different, single-boot method of installing XP direct from an ISO file using a WinPE ISO 'helper' file (WinPE v2 or v3 or v4 or a Vista Install DVD or Win7 or Win8 Install DVD). If your XP ISO has been modified with driver packs or nLite or if your ISO has $oem$ folders then it may not install correctly using the STEP1/2 method, so use the WinPE Install menu instead.
For more details on how to install Windows Vista and later OS's see Tutorial #43.
After you have selected a Win8/SVR2012 ISO, E2B will prompt you to select any unattend.xml file that is present in the \_ISO\Windows\Win8 folder from a list or CHOOSE A PRODUCT KEY or from any *.xml file or NO KEY.
You can define your own Unattend.xml files which should contain the correct product key and can contain your own settings too. These must contain a special entry for LOADISO.CMD (see below). Any extra .xml files will also be automatically listed. If you delete all .xml files from the Vista/7/8/SVR2012 folders, then the default unattend.xml will be automatically used and the user will not be prompted to select an xml file.
CHOOSE A PRODUCT KEY - Alternatively, you can use the Easy2Boot default Unattend.xml file and then pick a key from a list of user predefined product keys using the Select a Product Key file menu. Product keys can either be contained in separate .key files and/or in one single 'CHOOSE FROM A LIST.key' file (see above for an example of the contents). You can tailor the CHOOSE FROM A LIST.key file to show only the product key entries that you want to allow (you can edit it using NotePad - see above for details).
The pre-defined .key files can be deleted or altered or added to. These can be selected by using the E2B menu (items 2-6 in the example above).
If you select the CHOOSE FROM A LIST.key menu option (1) then you will be presented with a pre-defined list of different keys:
NO KEY - No product key will be set in the unattend.xml file - the user will be able to pick any version of Windows 8 to install that is contained in the ISO file and can enter the Product Key manually during installation.
Note: The keys pre-defined in E2B are sample keys for installation only and will not activate. If you organisation has volume licence keys, you should edit the CHOOSE FROM A LIST.key file to use your own legal Product Keys.
Where there is only one choice of XML or .key or ISO file, E2B will automatically pick that file. If you delete the example files and leave just one file, then that single file will be selected automatically. If there is only one Windows XP ISO, then that file will be automatically selected.
Copy your favourite bootable payload/'LiveCD' files (e.g. .ISO, .img., ima, etc.) to the \_ISO\MAINMENU folder, these will be individually listed in the first main menu when the USB drive is booted.
If you also make and add a .txt file of the same filename containing the single line of text title some_text_here\nsome_help_text_here, then that entry will be used as the menu title instead of the name of the file (must start with the lower-case word 'title'). See here for more details.
Note: Any payload file placed in a sub-folder below the \_ISO\MAINMENU or any of the menu \_ISO\xxxxx folders will not be listed in the Main menu (it will require a .mnu file). For this reason, if you have a .mnu file, the payload file for it (e.g. ISO file) must be placed in a sub-folder below \_ISO\xxxxx.
For instance, if we want to boot Ubuntu directly from an ISO file with persistence, we need a .mnu file (you can find one in \_ISO\docs\Sample mnu files) and we need the Ubuntu ISO file. If we want the menu entry to be listed in the Main menu we would place the files here:
If however, we wanted the menu entry to be listed in the Linux sub-menu, we need to place the files here:
NOTE: Always run WinContig to ensure all files are contiguous after copying them over (Ctrl+F2 in RMPrepUSB).
Note that the file extension determines how the file will be executed by grub4dos and E2B. For instance, if you have an .iso file and it does not boot correctly, rename the file extension and try a different extension - for example
Some other file extensions you could try if the normal extension does not work are:
Tip: If you are not sure what ISO extension will work, or want to try a variety of methods to boot an ISO, rename the ISO file to .isoask - you will be offered a choice of boot options before it is booted - see the screenshot below. Once you have determined which extension works best, rename the ISO to that extension.
Add any bootable files that you want to be listed in a sub-menu and not the Main menu, to the \_ISO\XXXX folder (I have already made pre-defined ANTIVIRUS, BACKUP, DOS, LINUX, UTILITIES and WINPE folders). The payload files will be listed when you choose the corresponding menu entry in the main menu. For example, if you copy a linux LiveCD ISO file to the \_ISO\Linux folder, then the ISO file will be listed in the Linux submenu when you select the Linux option from the Main menu (or press Ctrl+L).
Note: if you also add a file of the same filename but with a .txt extension and containing a single line of text such as: title some_text_here\n some_help_text_here , then that entry will be used as the menu title instead of the name of the file (note that the line must start with the lower-case word 'title'). The file can be saved in UTF-8 format and can contain special characters and you can also define a hotkey that will run this menu item too (see below for details on how to specify a hotkey). See here for more details.
If required, you can also change the file extension of the payload file too (see above).
NOTE: Always run WinContig to ensure all files are contiguous after copying them over (Ctrl+F2 in RMPrepUSB).
For those payload files which do not work using the above direct boot method (even with a renamed file extension) or have special requirements such as they use a persistent filesystem to store changes, etc. you will need to use a special grub4dos menu file for each of these payload files. For Easy2Boot these extra files have the .mnu file extension and they contain a grub4dos menu that has been specially written for a particular ISO or payload file. For example, for a linux ISO that requires a .mnu file, you need to add the payload file (e.g. ISO file) and it's matching .mnu file to the \_ISO\LINUX\Linux folder (note that the correct sub-folder may need to be created to match the one specified in the .mnu file, so you may need to make a new 'Linux' folder - also note that this is case sensitive so use Linux and not LINUX for the new folder name). The .mnu files can be downloaded from the Easy2Boot tutorial web page or copied from the \_ISO\docs\sample mnu files folder contained in the download. Once added, the .mnu file entries will be listed in the sub-menu once it has been selected from the Main menu.
Instructions on how to use a .mnu file are included as text comments inside each .mnu file - please read the instructions for details. You may also need to edit the .mnu file if you are using a slightly different version of the ISO so that the ISO filenames are correct.
NOTE: (did I mention this before?) Always run WinContig to ensure all files are contiguous after copying them over (Ctrl+F2 in RMPrepUSB).
E2B menus are dynamic and are started off by the \_ISO\E2B\grub\menu.lst file which looks at the contents of the \_ISO\MAINMENU\ folder and sub-folders for *.mnu files and for any other payload files in the \_ISO\MAINMENU folder.
The main action of Easy2Boot is to pick a folder (defined by the variable %MFOLDER%) and then for that folder, it will do the following (starting with the \_ISO\MAINMENU folder):
1. Alphabetically sort all files and folders in MFOLDER
2. If any file in MFOLDER is NOT a .mnu file, a .cmd file, a .txt file or a file with no extension - list the file in the menu as an 'autorun' entry
3. If any file in MFOLDER or any sub-folder of MFOLDER is a .mnu file, add the contents of the .mnu file to the menu
Then .mnu files in the \_ISO\MAINMENU folder run this process again for other folders, e.g. \_ISO\MAINMENU\ZZSubMenuAntiVirus.mnu sets MFOLDER to \_ISO\ANTIVIRUS and then enumerates the files in and under that folder (as in steps 1-3 above) to make a sub-menu entry in the Main E2B menu.
You can place .mnu files in a sub-folder under the \_ISO\MAINMENU folder and the .mnu file entries will be added to the main menu. If you wish, you can copy or rename a .mnu files to something else (keep the .mnu extension) and then make changes to the new file (be aware that any subsequent new update will write a new .mnu which you will need to delete again).
Please note: E2B V1 is mainly intended to be used on a flash drive because most Windows installs from ISO files won't work from a USB hard disk (unless a small auxiliary USB Flash drive is also used) - also Easy2Boot should be used on real hardware (for many situations - E2B will not work correctly in a VM).
Again: Linux ISOs and the Windows Vista/7/8/2012 installs WON'T ALWAYS WORK CORRECTLY under an EMULATOR/VM.
To get Windows installs working by booting from an Easy2Boot USB HDD - see below.
If you don’t see the E2B main menu when your USB drive boots – please ensure that your \menu.lst file has the 'configfile /_ISO/E2B/grub/menu.lst' command in it.
0 Set default menu entry and timeout - use can set Main menu entry default selection and automatic timeout (unless set DEFMENU=0 is in MyE2B.cfg - v1.09+)
Note: if no Windows ISOs are detected under \_ISO\Windows then the 'Install Windows' menu entry will not be listed. If any of the sub-menu folders are empty, then the sub-menu entry will not be listed in the main menu.
AUTOMN.g4b - grub4dos batch file, used by easy2boot.lst and menu.lst and ZZSubMenuxxx.mnu files
Background.bmp.gz - aurora 800x600 bmp wallpaper compressed to .gz
backup.lst - used for debug – don’t delete!
CountFiles.g4b - helper batch file which counts files
E2B.cfg - default config file (used before \_ISO\MyE2B.cfg is called)
FASTLOAD.MNU - the cached Main menu is written to this file if \FASTLOAD.YES is present
firadisk.gz - floppy image containing firadisk driver
isobackup.lst - used for debug – don’t delete!
KBDxxxx.g4b - specify one of these in your MyE2B.cfg config file for your keyboard layout (default=US)
LstFExt.g4b - helper file to list files with a specified extension (e.g. all .iso files)
MAIN.hdr - header used by grub\menu.lst as precursor for the dynamic main menu
memdisk - executable to load a ramdrive
MENU.LST - this starts the whole thing off!!! – called by \menu.lst
menusetting.gz - grub4dos executable for menu position and border
MenuWinInstall.lst - this is the main Windows menu
menu_defaults.txt - this holds the default menu number and timeout values set by the user
PCIID.ima.gz - used by XP install – do not remove
PickaFile.g4b - batch file used to ask user to pick a file from a numbered list
QRUN.g4b - this determines what action is taken based on the file extension.
ReadMe.txt - guess!
RunVista.g4b - batch file used for Vista, Win7 and SVR2K8R2 installs
RunWin8.g4b - batch file used for Win8 and SVR2012 installs
SVR2012.hdr - header code for the SVR2012 menu
SVR2K8R2.hdr - header code for the SVR2K8R2 menu
unifont.hex.gz - unifont font file (required for non-ANSI character sets/languages)
VarsLeft.g4b - counts the number of variables left in the environment (for debugging)
Vista.hdr - header code for the Vista menu
VistaMn.g4b - batch file used to install Vista, Wk8/7 user input
Win7.hdr - header code for the Win7 menu
Win8.hdr - header code for the Win8 menu
Win8Mn.g4b - batch file used for the Win8/2012 user input
winvblock.ima.gz - used by XP install – do not remove
winvblock.img.gz - FDD image used by QRUN - do not remove
XPStep1/Step2/Step2LowRam.g4b - used by XP menu system
XPWINNT.g4b - used by the 'XP install from WinPE' menu to select which ISO you want, etc.
Some payload files are included in the download - you can just delete these to save space if you don't want or need them:
Note that if a file/folder is present (of any sort) in the ANTIVIRUS, BACKUP, DOS, LINUX,UTILITIES or WINPE folders, then that sub-Menu will be listed in the Main Menu
All .ISO files larger than 0 bytes in a folder will be listed - note that these ISO files should not be modified to auto-install or they may or may not work!
The ISO files can be any name and should be placed in the appropriate folder (look at the sub-folders under \_ISO\Windows to see where they should go).
Note: Most OEM Windows 7 and 8 install ISOs contain all SKUs, so for instance a Windows 7 Home Basic DVD will usually contain Starter, Home Basic, Home Premium, Professional and Ultimate SKUs. You will be able to choose any of the these versions. So if you have a Windows 7 SP1 64-bit Ultimate ISO, simply rename this to Win7_64_SP1.ISO and it will be listed in the menu system and you can choose any of the versions inside it.
Note that Retail ISOs usually contain a single SKU and a single language. These are smaller than the OEM ISOs (e.g. Win7_64 is only 2GB instead of 3GB+) and the ISO \Sources folder contains the word 'Retail' in the EI.CFG file. If you have an OEM multi-lingual Vista/7/8 ISO it should contain all SKUs.
You can use the Install Windows XP using WinPE menu to pick any XP ISO to install and also pick an unattend.txt file. A WinPE v2/3/4 ISO or Windows Install ISO is also required. Only a single boot to the Easy2Boot USB drive is required with this method. This method will also work if booting from an exFAT formatted Easy2Boot USB drive using a Win7/8 WinPE or Install DVD. This method can also be used with XP install ISOs that contain $oem$ folders.
Although you are asked for a partition size, you can later skip over partitioning and formatting of the drive. If you specify a partition size and an unattend.txt, when you later confirm with Y - the disk will be wiped, re-partitioned, re-formatted and the whole XP build will continue automatically without further user input being required.
The XP ISO should have any mass storage drivers already integrated (nLite'd) as required by the system (e.g. AHCI drivers).
You can automate Windows XP installs by using unattend.txt files and using the WinPE install option in the Windows XP menu - see here for more details.
To automate Windows Vista/SVR2K8R2/7/8/SVR2012 installs - refer to the section below on xml files.
r bootable binary and want to quickly test it, just copy it to one of the folders on the Easy2Boot USB drive as below:
\_ISO\XXXXXX folder - e.g. \_ISO\MAINMENU for it to be listed in the Main menu (do not place in a sub-sub-folder under \_ISO\XXXXX\ as it won't be automatically listed unless you also have a .mnu file too!).
To change the way it will be executed by grub4dos, change the file extension. Most are special 'Easy2Boot' file extensions (non-standard) which will be recognised by Easy2Boot. if you are not sure what file extension will work best and it is an ISO file, use .isoask so that you can test all of them until you find one that works!
If you place any file (except .txt, .cmd, .mnu and files with no extension) in these folders, they will all be listed in a menu even if they are not bootable files. When selected from the E2B menu, if the extension is recognised, the file will be executed. The file extension determines how it is executed by grub4dos; recognised file extensions and their run actions are listed below...
.iso - maps the ISO file (if contiguous) and also creates a new partition containing the ISO contents - use for linux ISOs and others
.isomem - loads the whole ISO file into memory and also creates a new partition containing the ISO contents (if contiguous) - use for non-contiguous linux ISOs and XP-based ISOs and Hirens ISOs
.isowin - as .isomem but does not load ISO into memory unless it is non-contiguous and boots from /i386/seupldr.bin or ntldr if possible - use for WinPE ISOs - e.g. Symantec Recovery ISOs
.isolinux - tries to boot from ISO using isolinux.bin or /boot.isolinux.bin or /boot/syslinux.bin if possible
.isogrub - tries to boot from grldr within the ISO
.isoforce - loads firadisk floppy disk image and forces grub4dos to boot from the ISO even if it doesn't think it is bootable - use for CentOS ISOs
.isofira - maps the whole ISO file (if contiguous) or loads it into memory (if not contiguous) and also loads the firadisk floppy image as fd0 - use for BartPE\Hirens XP PE based ISOs
.isomemfira - loads the whole ISO file into memory and also loads the firadisk floppy image as fd0 - use for BartPE\Hirens XP PE based ISOs
.isowinv - loads the ISO and also WinVBlock as a floppy image + swap hd0 and hd1 - useful for booting ERDCommander and other XP PE based ISOs
.isowinvH - loads the ISO and also WinVBlock as a floppy image - does not swap hdo/hd1 - useful for booting Hirens CD and DLC multiboot ISOs
.isomemwinv - loads the ISO into memory and also WinVBlock as a floppy image - useful for booting ERDCommander, BartPE and other XP PE based ISOs if they are not contiguous
.isogz - loads the ISO into memory - use for a gzip compressed ISO.
.isoe0 - used to boot Windows PE ISOs which give a blank screen after booting on some systems that have a buggy BIOS. - e.g. some Dell PCs - see here for details.
.isomemE0 - as .isoe0 but loads ISO into memory. - e.g. some Dell PCs - see here for details.
.isowinvE0 - as isowinv but with a special e820cyles=0 patch to boot WinPE-based ISOs that give a blank screen after loading - e.g. some Dell PCs - see here for details.
.isowinvHE0 - as isowinvH + e8020cycles=0 patch (see above)
.isoPE - use for WinPE v2/3/4 (Vista and later) WinPE ISOs. If the extension is .isoPE then when wpeinit is run by WinPE, it will mount the .isoPE file as a virtual CD/DVD drive letter. Note: This requires a USB Flash drive (or 'Helper' flash drive) - E2B v 1.07Beta and later versions only. The drive letter can be changed too.
.isoPE01 - as .isoPE but swaps hd0 and hd1 over so that the internal hard disk is hd0 - useful for diagnostic WinPE's that expect to be booted from a CD.
.isoask - asks the user each time which of the above options should be used - useful to determine which extension works best
.isodd - same as .iso (so even if ISOASK variable is set then E2B will not ask how you want to run it and it will boot in the same way as a .iso file).
.iso01 - same as .iso but swaps over hd0 and hd1 so hd0 will be the internal HDD. (v 1.11 and later)
.isoDOS - use for DOS-emulation boot ISOs, all CD contents will be found on the B: volume once booted to DOS.
.isoDOS01 - as .isoDOS but swaps over the USB boot drive with the internal hard disk so that the internal HDD is drive 0 - use for Win98 Install ISOs, etc.
.gzmd - loads memdisk and then the .gzmd file using initrd
.vhd - a bootable virtual hard disk image (must not be a dynamic vhd) - boots vhd as hd0.
.vhdmem - as for .vhd but the whole vhd file is loaded into memory (use if .vhd crashes and for faster operation once booted - obviously needs loads of memory!). E2B v1.09 and later.
.zip - uses memdisk to load a zip file into memory as a floppy disk (e.g. use for dos622.zip which contains dos622.ima)
.bin - use for binary executables such as memtest86.bin
.imghd - Swaps over hd0 with hd1, the image is directly mapped if contiguous or loaded into memory if not - image is mapped as hd0
.imgmemhd, .imgmem - Swaps over hd0 with hd1 and maps the file as hd0 in memory using --mem
.imgfd, .img, .ima, .imafd, .imz, .imgmem, .imggz, .gz, .imagz, .imagzmem, .gzfd, .imamem, .imgmemfd, .imgfd - These will all cause the file to be loaded into memory and be mapped as a floppy disk image
.imgfdhd01 - loads floppy disk img file as fd0 into memory and swaps hd0 with hd1 - use for KonBoot fdd image where hd0 needs to be the internal hard disk and not the USB boot drive (E2B v1.08 and later)
For instance, if you have fred.iso and it is a BartPE XP ISO, rename the extension to fred.isomemfira and it will be loaded into memory and a firadisk floppy image will also be loaded. If you just leave it as .iso, and it is contiguous, it will be directly mapped and no firadisk floppy image will be loaded and it may BSOD!
If you want a different menu title to be used (rather than the name of the file being used in the menu), then make a new .txt file using Notepad. For example, if you have DOS622.imagzmem and you want a different title, add a new file called DOS622.txt to the same folder and add your replacement title line in the file (must start with the lower-case word 'title') - e.g.
title MS-DOS 6.22 Floppy Disk\n This boots the file DOS622.imagzmem
More extensions can be supported by editing the \_ISO\E2B\grub\QRUN.g4b grub4dos batch file and adding your own new extension section of code to the batch file. Let me know if you want me to support a new extension in the QRUN.g4b file for the next version.
Tip: If you have an ISO file which does not boot correctly, rename it to .isoask - then you can try all of these options to see if any of them will work correctly.
If you are still having problems, check the \_ISO\docs\Sample mnu files folder to see if there is a .mnu file you can use (or modify slightly). You can also ask for help on the reboot.pro forum.
Finally, if all else fails, contact me and I will try to help.
I use Oracle VM Virtual Box. I install E2B onto a USB 3.0 stick or USB HDD using RMPrepUSB and then set up a virtual machine to boot from the USB stick directly (see Tutorial 4 for details on how to do this). Booting to E2B in this way takes just 1 second or so! Also, most linux ISOs seem to boot OK as the 'partnew' trick seems to work. I use DavidB's Virtual Machine USB Boot application - this allows full rd/wr access to the E2B USB drive under VBox - something that was not possible before!
If you only have slow USB 2.0 USB sticks, use a USB hard disk instead (for testing the menu system only!).
Even using Virtual Box and DavidB's USB Boot application, some payload files/ISOs may not boot successfully. Always test on real hardware - never assume that if it doesn't work on a VM, then it won't work on real system!
Having said that, most linux ISOs will boot successfully using Oracle Virtual Box from an Easy2Boot USB Flash drive (usind DavidB's VM USB Boot app) and I can install XP to a virtual drive using the XP STEP 1/STEP 2 menu of Easy2Boot when booting from a USB Flash drive under Oracle Virtual Box (with VT acceleration disabled for Step 1).
Several alternative 'theme templates' are included with E2B (Aliums, Blue, Jolene, TextMinimal and lastly GFXMenu) - you can check these out by copying the two files in one of the Template folders at \_ISO\docs\Sample E2B Templates\xxxx to the \_ISO folder and then boot from the USB drive to see what each looks like (you can use RMPrepUSB QEMU or Oracle Virtual Box to check the appearance or boot from a real system). Note that the GFXMenu has some limitations and requires extra .mnu files to be added to the \_ISO\MAINMENU folder from the \_ISO\docs folder.
To restore the default E2B menu, just delete the MyE2B.cfg file from the \_ISO folder.
When Windows Setup runs (Vista and later versions), Setup will look for a file called \AutoUnattend.xml on a removable drive. E2B relies on this feature. The AutoUnattend.xml file generated by E2B contains an entry which causes Windows Setup to run a utility (FiraDisk and/or ImDisk) which finds and then loads the Windows Install ISO file as a virtual DVD drive so that Windows Setup can access the files inside the ISO.
Note: Some modern (win 8 certified) USB flash drives can also appear as a hard disk to Windows. Run RMPrepUSB and select the USB flash drive - check that it is listed as a (Removable) drive. If not, you will need to follow these instructions and use a secondary 'removable' Helper USB Flash drive.
E2B Windows XP+WinPE (see section below), Vista and later OS installs will not work if you only use an Easy2Boot USB Hard Disk (you will get a 'Driver required' error).
To make Windows Vista/7/8/2012/SVR2K8 installs work from an Easy2Boot USB Hard/Fixed Disk (Local Disk in Windows Explorer), you must use an Easy2Boot USB Hard drive together with a spare, writeable, 'removable' USB 'Helper' flash drive, as follows:
1. Prepare your Easy2Boot USB Hard disk as described in this tutorial.
2. On any small spare USB Flash drive that you have available - this drive must be seen by Windows as a writeable, removable disk which is usually the case for small USB flash drives - check that RMPrepUSB reports it as (Removable):
3. To install Windows Vista/7/8/etc. (or XP via WinPE method) onto a target system, connect both the Easy2Boot USB hard disk and the USB flash drive - but boot from the Easy2Boot hard disk.
WARNING: If you use a multiple-partition USB flash drive and the xml files are not on the first partition then Windows Vista/7/8 installs will not work because Windows Setup only mounts the first partition of a flash drive and so cannot see any of the files on the other partitions of the flash drive!
Some Dell Optiplex systems (for instance) do not seem to support booting from a USB Hard drive. In this case, you can boot from the USB Helper flash drive and then run E2B from the USB Hard drive as follows:
1. Run RMPrepUSB and select the USB Helper Flash drive
2. Click on the Install Grub4dos button and install grub4dos and copy over the grldr file when prompted
3. Press F4 in RMPrepUSB to create a new menu.lst file on the USB flash drive and add these two lines to the file and save it:
See here for more details.
The here for details of how to add mass storage drivers to E2B which allows you to automatically install from unmodified XP ISOs to SATA/RAID/SCSI/SAS/AHCI systems (automatic mass storage driver detection) without needing to press F6.
If the Easy2Boot Windows XP two-step process is not working on some systems, try this WinPE method instead. With this method you can also automate the install.
This method requires two ISO files.
You can use pretty much any WinPE v2/3/4 ISO that you have on your Easy2Boot drive or a Windows Install ISO (e.g. an existing Windows 7 or 8 Install DVD ISO that is already on your E2B drive, but not an XP-based ISO).
You can make a 150MB WinPE ISO by downloading and using the >3GB Windows WAIK (use copype x86 c:\winpe3) and make an iso file using mkfsiso from the Windows command line.
A much easier and fully automated way to obtain a bootable WinPE3 ISO that is also useful as a rescue ISO (a download and then just a few mouse clicks!) is to follow Tutorial 107 and make a Macrium Reflect Rescue ISO. This ISO can then be used with this method to install XP and as a general purpose rescue ISO (you can put it in the \_ISO\MainMenu, \_ISO\MainMenu\Windows or any of the \_ISO\Windows\xxx folders).
1. Ensure you have an XP Install ISO file in the \_ISO\Windows\XP folder (any .iso filename can be used)
2. Make sure you have a Vista, 7 or 8 Install ISO or WinPE v2/3/4 ISO in one of the \_ISO sub-folders - the helper PE .iso file can have any filename you like.
3. The file at \_ISO\Windows\WINPE_INST.TAG should be already present (don't delete it!) - if you delete it you will not see the 'Install any ISO using WinPE' option in the menu!
4. You can add your own unattend.txt file to the \_ISO\Windows\XP folder (use any suitable filename but it must end in .txt). Use the sample one as a template. The sample one provided will run Setup without any user interaction.
5. Run WinContig (RMPrepUSB - Ctrl+F2) to ensure the PE ISO file is contiguous
6. If you are booting from an Easy2Boot USB Hard drive, you also need to prepare and connect an auxiliary 'Helper' USB Flash drive (see section above for details)
When you boot from the Easy2Boot USB drive, the Windows XP install menu will have the option:
When you select this option you will need to answer some user questions before it boots from the ISO file:
If you have an XP ISO with integrated AHCI drivers (e.g. using driverpacks.net or nLite), then it should work on an AHCI system.
If possible, use a 32-bit Windows 8 Install ISO as the WinPE installer OS as that will have the widest range of drivers and USB 3.0 support.
Tip: To automate the process further and remove the final prompt to reboot (see step 6 above), edit the \_ISO\E2B\firadisk\RUNWINNT.cmd file and add REM to the line near the end of the file as shown below:
See below for a description of how this process works...
You can specify your own unattend.xml file for Easy2Boot to use (Vista/WIn7/SVR2K8R2/Win8/Server2012) or unattend.txt files (for XP WinPE install method).
Note: If you delete all .xml files from the Vista/7/8/SVR2012 folders, then the default E2B unattend.xml will be automatically used and the user will not be prompted to select an xml file.
Add your unattend.txt files (any name ending in .txt) to the \_ISO\Windows\XP folder. Use the 'Install XP from an ISO using WinPE' menu option.
IMPORTANT: You must also add the special E2B RunSynchronous entry to your .XML file (see below for details). If you don't, then the blue console LOADISO window will not run and the ISO will not be loaded - Windows Setup will then complain about a missing CD drive driver as it will not be able to see the DVD (ISO)!
Loadiso.cmd will prompt you to repair the drive - if you don't want this prompt, copy \_ISO\e2b\firadisk\loadiso.cmd to loadiso1.cmd (for example) and then edit your unattend.xml file to load loadiso1.cmd. Then edit \_ISO\e2b\firadisk\loadiso1.cmd and add 'exit' to the file here:
If you don't want the 'Press a key to boot from CD/DVD' prompt, you must remake the Windows ISO and delete the \boot\bootfix.bin file.
If you use a configuration set in your xml file, include the path to the drivers folder - e.g.
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <UseConfigurationSet>true</UseConfigurationSet> </component> <component name="Microsoft-Windows-PnpCustomizationsWinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <DriverPaths> <PathAndCredentials wcm:action="add" wcm:keyValue="1"> <Path>%configsetroot%drivers\</Path> </PathAndCredentials> </DriverPaths> </component>
If you want to use the drivers inside the ISO file, try using <Path>%USBDRIVE%\drivers\</Path> (note there is a \ after %USBDRIVE%)
Note: I have not personally tested the configset driver path setting and it is rumoured not to work! You may have to define the path. e.g. <Path>F:\drivers>/Path> but the drive letter must match the USB drive that contains your drivers which will vary from system to system!
unattend.xml files to automate installs, then you can add them into the correct folder and can be selected instead of the default ones.
If you have a Windows 8 unattend.xml or a Server 2012.xml file, then you can also define a 5x5 (29 character) product key in your .xml file.
IMPORTANT: You must also include the special RunSynchronous entry that Easy2Boot requires to your .XML file. If you don't, then the blue console LOADISO window will not run and the ISO will not be loaded - Windows Setup will then complain about a missing driver as it will not ba able to see the DVD (ISO)!
See here for details of what can go in an xml file to automate the installs.
Note: If you delete all .xml files from the Vista/7/8/SVR2012 folders so there is no choice to be made, then the default unattend.xml will be automatically used and the user will not be prompted to select an xml file.
Note that your xxxx.xml files must contain both x86 and amd64 entries if the same .xml file is use for both 32 and 64-bit ISOs.
The entry below must go in the settings pass="windowsPE" section of the .XML file under component name="Microsoft-Windows-Setup".
You should also define a product key or use a configuration set (see a sample file for details).
<Path>cmd /q /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\_ISO\E2B\FIRADISK\LOADISO.CMD cmd /k %i:\_ISO\E2B\FIRADISK\LOADISO.cmd"
<Description>Detecting usb drive</Description>
Note: You must balance the XML text - every <xxx> section must be closed with a </xxx>. Look at the following xml file - can you see the mistake?
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Path>cmd /q /c "FOR %i IN (C D E F G H I J K L N M O P Q R S T U V W X Y Z) DO IF EXIST %i:\_ISO\E2B\FIRADISK\LOADISO.CMD cmd /k %i:\_ISO\E2B\FIRADISK\LOADISO.cmd"</Path>
<Description>Detecting usb drive</Description>
</component> <------------ end of component section - this line should be deleted
</component> <------------ another end of component section but no <component> section before it!
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
Alternatively, you can install WindowsToGo onto the USB drive first and then add Easy2Boot.
Win7ToGo is not that stable (especially on a Flash drive) and I recommend Win8ToGo and a USB HDD or USB 3.0 Flash drive for best results.
If you need an activated Win8ToGo, then it is best to use a volume licence version as this will work on more than one system (a retail version will only work on the system it is activated on).
Note that if you want to install Windows Vista/7/8 from the same E2B Flash drive, it needs to be a 'Removable' drive, however Windows8ToGo does not work well unless the drive is seen by Windows as a 'Local Disk' drive. To fix this, if you have installed Win8ToGo onto a Removable USB Flash drive, boot to Windows 8 and install a special driver which will treat the Removable Flash drive as if it was a 'Fixed Disk' drive - read the Win8ToGo Tutorial for more details. The same driver can also be added to Win7ToGo.
Now create a new .mnu file in \_ISO\MAINMENU\bootmgr.mnu (or wherever you want it) which will boot to Windows if it was installed on your drive:
OR use this for a Win7/Win8 menu that will only appear if the bootmgr Windows file is on the USB drive
Note: If the USB drive boots straight to Windows and does not boot to the E2B menu, then re-install grub4dos again using RMPrepUSB (twice - once to MBR - once to PBR).
Making changes to E2B
To change the E2B menu, look in the \_ISO\Sample_MyE2B.cfg for details of the configuration options available (these are always updated with each new version).
\_ISO\Sample_MyE2B.cfg contains many configurable settings - rename this to MyE2B.cfg to make your \_ISO\MyE2B.cfg file.
The recommended way to change Easy2Boot menus and settings is to use your own copy of E2B.cfg (which must be named /_ISO/MyE2B.cfg). This file can contain the settings for menu colours, background image name, menu position, some menu headings text and colours and the graphics mode. MyE2B.cfg is NOT contained in the Easy2Boot download and so it will not be overwritten if you update your Easy2Boot installation.
WARNING: Do NOT edit or copy the \_ISO\E2B\grub\menu.lst or \_ISO\E2B\grub\E2B.cfg files!
Click on the picture to enlarge it. This shows the HEADING and HELPTEXT positions (as defined in your \_ISO\MyE2B.cfg file). The 'title help text' is the individual menu item help text - it is different for each menu item. This text can come from a .mnu file or from a .txt file. A few of the menu items help text is pre-defined in the E2B code. The help text for the Sub-Menus and F7 and F8 all come from the \_ISO\MAINMENU\ZZxxxxxx.mnu files.
1. Rename the \_ISO\Sample_MyE2B.cfg file to \_ISO\MyE2B.cfg.
2. Edit the \_ISO\MyE2B.cfg - this new MyE2B.cfg file will be called by Easy2Boot after \_ISO\E2B\grub\E2B.cfg has run – you can now change the new MyE2B.cfg to make changes to modify Easy2Boot's appearance and behaviour. Save the file using NotePad in UTF-8 format for full character-set language support.
You can use the QEMU button in RMPrepUSB to test your menu but it is quite slow - I recommend testing the menu appearance by using Oracle VM Virtual Box as in Tutorial 4 so that you can quickly test any changes to your menu system.
Note: After editing a file on a USB drive, you may find that the VM does not see the file change until about 30 seconds later due to delayed writes by Windows! If the change appears not to have worked, close down the VM and try again after 30 seconds.
If you have any problems, simple rename MyE2B.cfg to something else so that Easy2Boot will use the standard settings.
If you wish, you can rename \_ISO\MAINMENU\*.mnu files to anything else (ending in .mnu) and then make changes to them (any subsequent version update will write a new .mnu file which you will need to delete).
If you update Easy2Boot with a newer version - you may need to also check for changes and then update your MyE2B.cfg file by comparing it with the newer version of Sample_E2B.cfg - do not use an old .cfg file if the version has changed as you may get strange results!
There is an example of a Blue Menu MyE2B.cfg file + blue.bmp.gz background that is included with the download (in \_ISO\E2B\docs folder) which you can try (just copy the two files to the \_ISO folder):
The default background image is located at \_ISO\E2B\grub\Background.bmp.gz – this is a 800x600 24--bit colour image but it will also work if you switch to 640x480 graphics mode using GMODE=640 (see below). Do NOT change this file.
To use your own image, copy to the \_ISO folder your own mybackground.bmp or mybackground.bmp.gz file (you can compress a .bmp to a .bmp.gz using 7Zip and by selecting gzip as the compression type – this greatly reduces the file size).
Alternatively, rename the \_ISO\Sample_MyE2B.cfg file to \_ISO\MyE2B.cfg and change the following entries
If you have a .bmp file then change the MYWBMP= line, if you have a compressed .bmp.gz file then change the MYWBMPGZ= line. E2B will look for and use the bmp.gz file if it can be found, otherwise it will look for the .bmp file. If neither can be found it will use the default background.
If you wish to use your own bitmap (e.g. 640x480 or 800x600 or 1024x768) please ensure that the .bmp size is exactly correct (e.g. 800x600 and not 800x599 or 799x600).
You may also need to change the
line in your MyE2B.cfg file if the bitmap that you use is not 800x600. Note that 640x480 and 800x600 bitmaps are automatically supported by Easy2Boot as long as you also set the GMODE value - the menu size and help text position will be re-calculated for you (there are some extra lines of code added to the MyE2B.cfg file which do this). I strongly recommend you do not use higher than 800x600 as not all systems can support these higher resolutions (e.g. early netbooks).
You can specify any name for the image file in \_ISO\MyE2B.cfg file - it does not have to be "mybackground.bmp.gz".
Tip: Choose a bitmap that has a clear area at the bottom so that help text is easily visible. Avoid a multi-coloured, high-contrast picture (e.g. lots of different bright colours and dark blacks) as it will be difficult to choose a text colour that will stand out against all of the colours in your picture! Another idea is to use a bitmap editor and draw a filled rectangle over the picture so that the menu can be displayed within the rectangle. You can also add any other items (e.g. your name or company name or company logo) to the bitmap.
You can use the settings in MyE2B.cfg to change the menu position and the menu size, text and border colours.
You can, of course, make a plain single colour 800x600 bitmap for the background.
If you do not want a fancy picture (which may take a second or two to load) but prefer to use the standard grub4dos text mode - edit your MyE2B.cfg file as follows:
You can set the colours in the usual way but you can also specify background colours as well as foreground colours when in text mode - e.g.
specify a light grey menu background using the following menu as MyE2B.cfg...
# set bottom text position 24 lines per screen (note: help text disappears when a user presses a cursor key)
# set colour for heading
# set colour for footer
# set text colours
Standard grub4dos supports the US keyboard layout. If you are entering text using the keyboard, you may need to change the keyboard layout mapping.
To do this, simply make a MyE2B.cfg file (see above) and specify one of the KBD_xxx.g4b files in the \_ISO\E2B\grub folder. e.g.
If you have any .mnu files, these will be listed depending on the name of the .mnu file itself (not the payload file or title which is used inside the .mnu file). If you have Ubuntu.mnu it will therefore be listed after dplite.mnu. To change the order, simply rename ubuntu.mnu to $ubuntu.mnu.
Note that folders will also be searched alphabetically. If you have:
MENU will be:
note that the menu entry for PassPass will be listed after the menu entry for Ubuntu because .\Ubuntu.mnu alphabetically precedes .\Utility. If you want PassPass to be listed before Ubuntu, rename Ubuntu.mnu to ZUbuntu.mnu.
Note that E2B has several \_ISO\MainMenu\ZZSubMenuxxx.mnu pre-defined menu files. As these begin with 'ZZSub' these menu entries will be listed alphabetically and so will be listed at the end of all other menu items. If you want the sub-menu entries listed first in the Main menu, rename the ZZSubMenuxxxxx.mnu files to $ZZSubMenuxxxx.mnu.
set HEADING=\x20 EASY2BOOT V1 - MAIN MENU \x20
can be changed to
set HEADING=\x20 STEVE’s (sehr güt!) MAIN MENU \x20
Tip: \x20 is the code for a space character and must be used at the start of the line to add padding.
The very bottom help text can also be changed (displayed on most menus):
Different headings for each of the sub-menus are defined in each individual ZZSubMenuXXX.mnu file.
# at the start of a line is used to comment out the line.
Tip: Using NotePad you can save the MyE2B.cfg file as UTF-8 unicode. You can then add text (menu headings, etc.) using the character set of your language (e.g. chinese glyphs, etc. )
set HEADING=\x20 (重启) € á¡ü test UTF-8
Alternatively, you can specify the colours in text/background pairs and use black for a transparent background: e.g.
You can also use a full 24-bit colour value 0xrrggbb - e.g. color border=0xFF3377 (be aware that using 0xrrggbb always sets a black\transparent background)
You can also change the colour of the Menu Heading by changing the
line in the \_ISO\MyE2B.cfg file (read the text in MyE2B.cfg for an explanation of what the numbers mean).
FCOLOUR changes the bottom footer help text colour.
To remove the border set the border width to 0 (e.g. set bdwidth=0).
As Easy2Boot changes the tophelp and noitems automatically, I suggest you do not change those but just change rstart and menuw to suit your background. There is some extra code in the \_ISO\MyE2B.cfg file which may override any tophelp and noitems settings you make. You can delete or change this code if you wish.
To change the main menu bottom message, change the HELPTEXT setting in\_ISO\MyE2B.cfg (or just use \x20 to remove it completely), two examples are:
set HELPTEXT=Please select an item using the cursor keys or press a number key
Note: You cannot easily suppress or hide the individual menu help text displayed at the bottom of the menu border (the text that changes when you highlight each menu entry with the cursor keys).
If you wish to hide the menu help text then it is easiest to make the colour of the help text exactly match the menu background as follows:
here for an example of what you might see as E2B runs).
E2B version 1.05 and later versions allow you to suppress the E2B menu file enumeration messages. To do this add this line to your \_ISO\MyE2B.cfg file:-
If you also want to suppress the early E2B startup messages (not recommended as they may be useful on systems with bad BIOSes) then add this line:
See the \_ISO\Sample_MyE2B.cfg file on the E2B drive (bottom of file) for an example of these two lines (note there is a space between the > and nul text).
You can hide the (initial) cursor by adding this line to the top of your MyE2B.cfg
You can use the examples in the Sample_MyE2B.cfg file to change the behaviour on startup, for instance to just have a blank screen right up until the Main menu is displayed use this in your MyE2B.cfg file:
call Fn.70 0 ;; clear ;; call Fn.5 0 128 ;; set redirp=> nul ;; set redir=> nul
If you want to blank out the grub4dos boot/startup messages to make your Easy2Boot USB drive look more professional when it boots, please do the following:
1. Boot up the Easy2Boot USB flash drive on a real system (not a VM or under QEMU unless writes work or the patch may not take effect!)
2. Press C to get to the grub4dos console - if nothing happens press P and enter the password (e.g. easy2boot), then press C
3. Type /_ISO/docs/patchme - this will patch the flash drive boot sectors and the grldr file on the E2B USB drive. You can also choose to remove the GRUB4DOS version header which is briefly displayed when a each new menu is loaded and when you go to the console command shell (though if you do you won't be able to see what version you are using!).
4. Hit a key to reboot when prompted.
Note that if you re-install grub4dos to the USB drive or overwrite the grldr file, you will need to run patchme again.
Easy2Boot v1.19 and later is written in (UK) English. To translate the English text to your own language...
Typically, text is output by 'title', 'iftitle', 'pause' or 'echo' commands in the grub4dos code.
For .mnu files, I suggest you do not edit the E2B .mnu files but make a new copy with a different name and edit that - so that if you update E2B with a newer version, you simply need to delete the standard E2B .mnu files again. Save your .mnu file as a UTF-8 file (using Windows NotePad) if you use special characters such as...
Tip: An easy way to translate the files to your own language is to use WinMerge as follows:
Now you can double-click on any file and WinMerge will open one file in a left pane and the other in a right pane.
You can now edit the words in the 'Spanish' pane whilst keeping the 'English' file unchanged. Click the small cross in the top right to save changes and go back to the main file/folder view. Now you can see which files you have already changed.
(click to enlarge)
v1.18 and later only - You can change the font used for the menu text by setting the FONT variable in the \_ISO\MyE2B.cfg file (rename the Sample_MyE2B.cfg file to MyE2B.cfg).
Please note that you cannot change the size or style much (it must use an 8x8 or 8x16 dot matrix for each character). See my blog for details.
The Aliums Theme in \_ISO\docs\Sample E2B Templates\Aliums demonstrates using an Antique font for the menus.
If you want to use the BIOS font for normal ASCII characters but also want the unifont font (for chinese characters or the £ sign, etc.) then use 'set BIOSFONT=1' in your MyE2B.cfg file.
Various font files for just the ASCII characters 32-127 are available in the \_ISO\docs\Fonts folder. If you want to see what these fonts look like when used with your E2B menu, add the file $FontTest.mnu to the \_ISO\MAINMENU folder.
Alternatively, you can run the grub4dos ShowFonts.g4b batch file from the grub4dos command line to display a sample line in each font. The Windows batch file MakeShowFonts.cmd generates this file from all the fonts available in the same folder. If you make your own fonts, add them to the folder and run MakeShowFonts from Windows to generate a new ShowFonts.sg4b file.
You can make your own font file as follows:
1. Use the RasterFontEditor.exe program to load a font file - see here for the program and where to obtain extra font files.
e.g. In rasterFontEditor, use File - Import From TTF - select a non-TrueType font from the list (scroll up)
2. Save the font using File - Save Font As... Text Files (*.txt) - .txt is the HEX format we need.
3. Drag and drop the .txt font file onto Wonko's Fonttxt2uni.cmd file (extracted from Font_Bitmap.7z) - this will make a .uni font file
4. Try the font out in Easy2Boot (e.g. load the E2B main menu, go to the command prompt, type font and then type font /myfont.uni to load your new font and press ESC to get back to the E2B menu)
5. Edit the file in Notepad and delete all lines for characters 0000-001F and 007F-00FF. Also delete any lines after 0020 if the contents are just a line of 00's.
6. If you wish you can use 7Zip to compress the .uni file using GZip to a .uni.gz file
Note: the default password to gain access to grub4dos is 'easy2boot'. This is set by the E2B.cfg file.
If no password was set, then any user could edit any of the Easy2Boot menu entries by pressing 'e' or the user could reach the grub4dos command line by pressing 'c'.
If the user presses 'e' or 'c' by accident, they might not understand what has happened or know how to get back to the menu again and you may not want them to access the USB drive in this way, so I set a default password is set.
You can set or change or remove the password as follows:
1. Copy the \_ISO\Sample_MyE2B.cfg to \_ISO\MyE2B.cfg
2. Change the password line in \_ISO\MyE2B.cfg - base it on one of the three examples below:
# this will set a pasword of easy2boot (encrypted so the used won't know what it is!)
3. Save the \_ISO\MyE2B.cfg file.
set pwd=--md5 $1$1$okAQ3AJUdhqf3TVrwKvJP1 will set a password of 'easy2boot' and will prevent the user from accidentally getting access to the menu editor or the grub4dos command prompt.
If you want to use a different password, then you can either use a plain, unencrypted password, e.g.
or you can use an MD5 hashed password so that if the user looks at the MyE2B.cfg file, he will not know what the password is (in this example it is 'mypwd'), e.g.
set pwd=--md5 $1$4$tsiiC/23IOf0pifS.6ttc.
To find the MD5 password for any word, you can download the md5crypt program from here and generate your MD5 hash code.
Run the md5crypt.exe program, type in a password (e.g. mypwd) and then cut and paste the md5 hash into your \_ISO\MyE2B.cfg file.
Note that the value of pwd should start with --md5 (two minus signs followed by md5 and then a space).
Tip: To hide the password from prying eyes and prevent it's removal by someone using NotePad, use 7Zip to compress the MyE2B.cfg file to GZip format (you must keep the filename the same - i.e. as MyE2B.cfg, not MyE2B.cfg.gz). E2B will still work fine as long as the filenames are the same as they were before. If you wish, you can also do this to the \menu.lst file and the menu.lst and E2B.cfg files in the \_ISO\E2B\grub folder too (or even all .mnu files, .txt files and .g4b files!). Do not do this with .ISO (payload) files though!
For an easy way to encrypt a load of files and save having to rename them afterwards using 7Zip, download LZMA.zip and unzip the three files inside it to your Desktop (or to any folder or even to your E2B USB drive). To 'encrypt' the menu.lst, MyE2B.cfg, etc. files on your USB drive, simply select them all in Windows Explorer and drag and drop them onto the LZMA_ENCODE.cmd file. A backup called .orig is also made on the source folder, which you can choose to keep or delete. To decompress the file(s), simply drag and drop them onto the LZMA_DECRYPT.cmd file. A backup of the original compressed file is made called .comp which you can choose to keep or delete. Note that if you select more than one file, you will only be asked the question to delete the original file(s) once and then that answer will be applied to any more files you have selected.
Note: Files created using lzma.exe can be decrypted by 7Zip if you give them the .zip file extension.
You can set a master password by uncommenting the 2 lines in the MyE2B.cfg file, e.g.:
OR (use an encrypted password and reboot if the user gets it wrong):
This prevents Easy2Boot from running unless the user knows the master password.
When the Main Menu loads, you can make E2B beep to signal that it is ready. This is useful if the menu takes a long time to load as it will tell you when it is ready. 1-3 beeps are supported. The computer must have an internal speaker fitted (most notebooks don't!). To the MyE2B.cfg file add:
The following instructions can be used to make any number of additional folder entries in the Main menu (e.g. Diagnostics, Special, MSDart, etc.).
Easy2Boot only has several sub-menu folders pre-defined (e.g. ANTIVIRUS, BACKUP, DOS, etc).
Let us say you have some ISOs which you often use to make a backup, and you also have an ISO (ping.iso) which you use to make an automated backup, but it requires some special commands, and hence it requires a .mnu folder. And let us suppose that you want all of these in a folder called SPECIAL and a separate menu entry in the Main menu called SPECIAL . e.g.
1. Copy the ZZSubMenuDos.mnu file in the \_ISO\MAINMENU folder and rename it to \_ISO\MAINMENU\ZZSubMenuSpecial.mnu
2. Edit the ZZSubMenuSpecial.mnu file in NotePad and change the first few lines to your own text and own folder name, e.g. change this...
Note: The original title line defined a hotkey using ^Ctrl+D and the [Ctrl+D] which indicates to the user that there is a hotkey assigned to this menu entry. You can add and change these two parts of text f you want a hotkey for your menu item. Note that GFXMenus does not support hotkeys.
4. Create a new folder at \_ISO\SPECIAL
5. Now place your ISO files, etc. in this folder. If you have .mnu files you can place these in the same folder or any sub-folder that you make. For instance, if you want to use an Ubuntu.mnu file and Ubuntu.ISO file, place both of these in \_ISO\SPECIAL\Linux folder (if the .mnu file is expecting the ISO to be in %MFOLDER%\Linux).
You can repeat these instructions for any other folder you want to create.
If the heading at the top of the menu is not aligned correctly, make sure it is padded with enough spaces.
You can also have sub-sub-menus. For instance, copy your ZZSubMenuSpecial.mnu file to your \_ISO\SPECIAL folder and rename it to ZZSubMenuSPECIAL_USEFUL.mnu and edit it as follows:
iftitle [ls (bd)/_ISO/SPECIAL_USEFUL/ > nul] ^U SPECIAL USEFUL TOOLS Menu [U]\n My useful backup tools
Now create a folder call \_ISO\SPECIAL_USEFUL and put any ISO files or .mnu files under there. Do NOT create sub-folders for sub-menus under the \_ISO\SPECIAL folder!
Your SPECIAL menu will now have a new menu entry in it called SPECIAL USEFUL TOOLS Menu with a hotkey of U.
You can use a similar menu to move back to the previous folder menu - see \_ISO\UTILITIES_MEMTEST\ZZBackTo_Utils.mnu for an example.
If you want to add a Main menu entry to install a specific Windows ISO directly from the Main menu (to save having to go to the Windows menu and then the Windows 7 menu), you can add a .mnu file to the \_ISO\MAINMENU folder as below (this example contains one Win7 and one Win8.1 ISO):
See the \_ISO\docs\Sample mnu files\$$AddWin2Main.mnu file for the XP entries if you also want to add the XP PE install menu entries (individual menu entries for XP ISOs are not supported though). You can make separate entries for each non-XP ISO or combine them into one .mnu file. Menu entries will be arranged alphabetically according to their filenames, so change the name to ZZZZZZ.mnu if you want it added last in the Main menu. You can also add a hotkey for each one by adding it to the title line (search this page for 'hotkey').
To prevent a Windows XP/Vista/7/8 sub-sub-menu from loading the Windows Install sub-menu, use this setting in your MyE2B.cfg file (v1.14 and later):
Empty folders will not be listed in the Main menu, so just ensure that these folders (e.g. \_ISO\DOS, \_ISO\BACKUP and \_ISO\UTILITIES) are completely empty of any files or folders.
For instance, if you have an ISO file at \_ISO\MAINMENU\LinuxTails_x86_2012_11_02.iso, it will be displayed in the main menu just as the filename+extension:
However, if you also specify an alternative title in a .txt file of the same name and in the same folder, then that title will be used instead (note the line of text in the .txt file must start with lowercase grub4dos command title)
where \_ISO\MAINMENU\LinuxTails_x86_2012_11_02.txt could contain the text :
title ^T Tails 2 Nov 2012 (32-bit) [T]\n Press ENTER to launch the GUI once it has booted\nPassword is toor
A hotkey of T has been defined for this entry. If you don't want a hotkey or if you use a GFXMenu, omit the ^T characters. See below for more details about hotkeys.
Text that follows \n will appear as help text at the bottom of the menu when the item is selected. Any more \n's on the line will start a new line of help text.
If you delete the payload file (e.g. linux.iso) you do not need to delete the .txt file - it will just be ignored.
Note: the text in a .txt file must start with the lower-case word title or you will see errors reported by E2B as it boots.
Tip: Save the file as UTF-8 using NotePad and any special characters such as ü will be displayed correctly.
As soon as the user presses a hotkey (e.g. presses the T key), the menu entry with a T hotkey assigned will immediately run (they don't need to press Enter).
Avoid using P, C, E or B for hotkeys as these are used by grub4dos for password entry and editing, etc. You can use Ctrl+B or Alt+C or Shift+D, etc. instead.
When you use a title command (e.g. in .mnu and .txt files), you can also specify a hotkey, e.g.
Will be displayed as:
Tails linux ISO [Ctrl+T]
You use the up-arrow symbol to specify a non-displayed hotkey.
Alternatively, you can use square brackets to define hotkeys - in which case the square brackets and the hotkey character(s) will be displayed in the menu, e.g.
title [T] Tails linux ISO\nPress T to boot to Tails
Will be displayed in the menu as
You can use numbers (best avoided as menu items can be selected by entering their number too!) or letters for a hotkey, as well as F1, F2, etc and Ctrl+F1 (e.g. ^Ctrl+F5). Hotkeys are not case sensitive, you can't have ^t and ^T.
You can also use iftitle - e.g.
GFXMenus do not understand this hotkey notation (and may even cause GFXMenu to crash!), so if you are using a GFXMenu, you must copy the ZZGFXSubMenuxxxx.mnu files from the \_ISO\docs\ZZGFXSubMenu Files folder to the \_ISO\MAINMENU folder (you can delete the \_ISO\MAINMENU\ZZSubMenuxxxx.mnu files if you are only using GFXMenu).
In E2B version 1.13 and later you can define global hotkeys in your MyE2B.cfg file. See the Sample_MyE2B.cfg file for examples.
These hotkeys do not use a menu entry and so are invisible to the user. If you want the user to know what they are, add text to the HELPTEXT or to your background bitmap. The hotkeys that you define will be active for all the menus. See \_ISO\docs\Sample E2B Templates\TextMinimal\MyE2B.cfg for an example.
Note for Advanced Tweakers only!: Any global hotkey that is set will exist for ALL menus and you cannot change or remove a hotkey command unless you add a new hotkey command to the top of a menu hdr or .lst file so that it is executed when that menu loads or add a .mnu file that is loaded first (e.g. starts with $$$ so it is added before other payload and .mnu files)
For Example:. If you wanted CTRL+F9 to automatically run Ubuntu when you are in the LINUX menu, but did not want the menu entry to appear in the menu,
1. Create a \_ISO\LINUX\Linux\$$$HotkeyUbuntu.mnu file with this single line:
2. Add your MyUbuntu.iso file to \_ISO\LINUX\Linux folder
Note that once the Linux menu is loaded, the Ctrl+F9 hotkey will now work in every menu unless you redfine the hotkey or clear it. For instance, if you added (bd)/%grub%/hotkey [Ctrl+F9] > nul to the top of \_ISO\e2b\grub\main.hdr, then when the Main menu was loaded the Ctrl+F9 hotkey would always be cleared.
In your MyE2B.cfg file add (v1.14 and later):
The Main menu entry is caused by the \_ISO\MAINMENU\ZZZF7BootHdd.mnu file. You can rename and edit this file to alter the F7 entry in the Main menu, For instance, to make it invisible (but still occupy a blank line in the menu), change the first line to:
Note that if you delete the .mnu file, the hotkey will no longer work and the menu entry will be removed.
To remove the entry from all other menus use set NOF7HD=0 in your MyE2B.cfg file.
This entry is caused by the \_ISO\MAINMENU\ZZZF8ReloadMenu.mnu file. You can rename and edit this file to alter the F8 entry in the Main menu, For instance, to make it invisible (but still occupy a blank line in the menu), change the first line to:
iftitle [if "%GFX%"==""] ^F8 \n
Note that if you delete the .mnu file, the hotkey will no longer work unless you specify a global hotkey in your MyE2B.cfg file.
To remove the entry from the Windows Install menu use set NOF8B=0 in your MyE2B.cfg file.
Note: You can add your own 'Back to Main Menu' into any menu by adding a Reload.mnu file into the \_ISO\xxx folder. To load the Main Menu quickly, use the cached version at (md)0xa000:
Use set NOF9R=1 in your MyE2B.cfg file (v1.11 and later). Change the HELPTEXT setting in MyE2B.cfg too.
Use set NOF10H=1 in your MyE2B.cfg file (v1.11 and later). Change the HELPTEXT setting in MyE2B.cfg too.
Menu entries are alphabetically sorted. To add a blank line (separator) in the Main menu between say Acronis.iso and Backtrack5.iso, for instance, create a file at \_ISO\MAINMENU\AZSeparator.mnu:
You can have as many of these files as you like, but note that each menu item will be counted by grub4dos, so when you set a default menu item (using menu 0) then you must also count these blank lines even though they are not numbered. The small number at the top right of the menu box actually indicates the menu number you need to use when setting a menu default.
1. Make a new file \_ISO\MAINMENU\$$$JumpToWinMenu.mnu
2. To \_ISO\MyE2B.cfg add:
3. (optional) Delete all ZZxxxxxxx.mnu files in \_ISO\MAINMENU
to the root Easy2Boot folder (i.e. \FASTLOAD.YES). This will cause the Main menu to be cached for a quicker boot the next time.
The main menu is normally built up in memory on booting and it enumerates (detects) all the files under the \_ISO folder - this can take some time if you have lots of files. If FASTLOAD is enabled, this menu is copied (cached) to the FASTLOAD.MNU file. On the next boot, if \FASTLOAD.YES is present, the FASTLOAD.MNU file will be loaded as the main menu instead of Easy2Boot needing to re-detect all the payload files again and building a new menu in memory.
When Easy2Boot is in FASTLOAD mode, and if you then change the contents of the USB drive, you need to use the REFRESH option to update the cached copy of the menu so that the Main menu will be updated with the new contents.Fig. 4 Use this option if you change the contents of the Easy2Boot drive
Note: For Information only: The FASTLOAD.YES file must be at least 1K in size or larger - otherwise it won't work if it is on an NTFS partition. If it contains the word REFRESH then Easy2Boot will build a new menu in memory and write it to the FASTLOAD.MNU file and then remove the word REFRESH from the FASTLOAD.YES file so that on the next boot, Easy2Boot will use the contents of the FASTLOAD.MNU file as the Main menu. When you choose the REFRESH menu option, it writes the word REFRESH to the \FASTLOAD.YES file and re-runs menu.lst to restart Easy2Boot.
Note that you can edit the FASTLOAD.MNU file to change the Main menu order or contents to whatever you like (just don't 'Refresh' the menu or you will lose the changes!).
E2B enumerates files and displays progress information as it starts up. Displaying text messages and scrolling of the screen can delay things by a second or two on some systems. To disable these messages, add the following to your \_ISO\MYE2B.cfg file:
If you also want to suppress the initial E2B startup messages (not recommended), use:
Easy2Boot counts all .iso files under the \_ISO\Windows folder during startup. If you have a lots of files under \_ISO\Windows, this may take several seconds.
If you do not want to enable FastLoad, then you can speed up the Windows folder enumeration by presetting (hard coding) the number of Windows ISOs that you have.
The following procedure is NOT RECOMMENDED as it will alter an Easy2Boot file and a later E2B update will overwrite the file.
Edit the \_ISO\E2B\grub\CountFiles.g4b file as below (choose numbers to fit the number of files you have in each folder):
If you set a value to 0 then the menu item will not be listed - e.g. if CXP=0 then the Install Windows XP menu will not appear.
The value that you set will appear next to each menu item e.g. (9 present). CALL must be set to a number greater than 0 or the main Install Windows menu will not be listed.
If you don't need to use non-ASCII characters in your filenames or .mnu and .txt files, then there is no need to load the unifont.hex.gz 1MB font file on startup. To suppress this, edit your \_ISO\MyE2B.cfg file and add a NOUNIFONT=1 setting (actually any value will work!):
To use a non-graphics text mode menu, use set GFX=NONE in your MyE2B.cfg file. See the TextMinimal example in the \_ISO\docs\Sample E2B Templates folder for an example.
E2B wipes two large (100K) .xml files every time it boots by filling them with spaces.
If your USB drive is a USB HDD (not a 'Removable' Flash drive), then you can delete the \AutoUnattend.xml and \Unattend.xml files from the E2B USB HDD - this will save some time on every boot. These .xml files are not used if you are booting from a USB HDD.
If you are not going to use the Install XP via WinPE feature, or install Vista/7/8/SVR2012 from Windows Install ISOs or use .isoPE or .isoPE01 files (e.g. you only want to boot linux ISOs using E2B) then you can delete these two .xml files even if your Easy2Boot USB drive is a USB Flash drive.
If however, your E2B USB drive is a flash drive and you want to boot 'Windows things' then leave them alone!
only for people who want to make a new .mnu file for a new ISO file (or any type of payload file). This is normally not necessary unless the normal Easy2Boot automatic process needs some special additional commands. There are many working examples in the \_ISO\E2B\docs\Sample mnu files folder.
A .mnu file just contains valid grub4dos menu entries and comment lines. They are added to E2B's own menu which is held in memory.
1. Create a file in the same folder as your ISO file and name it the same as the 'payload' file but with a .mnu extension (it actually can be of any name but it just makes sense to match the name to the payload file).
For instance, if it is for YLMF linux and the ISO file is called Ylmf_OS_3.0.iso then name the file Ylmf_OS_3.0.mnu and place both files in the \_ISO\MainMenu\Linux folder or the \_ISO\LINUX\Linux folder.
You can have more than one menu entry in the same .mnu file or you can have more than one mnu file for the same ISO (perhaps there is more than one way to boot the ISO?).
e.g. files are:
4. Edit the .mnu file by adding some information for the user as comment lines - the easiest way to explain this is to see a before and after file:
menu.lst example taken from this site (before changing to .mnu format)...
iftitle [if exist /_ISO/Linux/Ylmf_OS_3.0.iso] Boot YlmF 3.0 (Windows Like OS) Non-Persistent\nThis OS boots directly from the ISO file at /_ISO/Linux/Ylmf_OS_3.0.iso
find --set-root /_ISO/Linux/Ylmf_OS_3.0.iso
The converted Ylmf_OS_3.0.mnu file...
# Download ISO file from http://www.ylmf.org/en/download.html
iftitle [if exist %MFOLDER%/Linux/Ylmf_OS_3.0.iso] Boot YlmF 3.0 (Windows Like OS) Non-Persistent\nThis OS boots directly from the ISO file at %MFOLDER%/Linux/Ylmf_OS_3.0.iso
Note that a few lines of comments (starting with #) have been added to indicate where to get the source file and the MD5 or SHA1 hash values have been added so the user can check this.
The other thing to note is that %MFOLDER% is used for the top level folder. This will be set automatically to /_ISO/XXXX if the .mnu file is placed in that folder or under it, e.g. MFOLDER=/_ISO/MAINMENU if the .mnu file is placed in the \_ISO\MainMenu\Linux folder. The variable MFOLDER is set automatically by Easy2Boot to the 'mother' 2nd-level folder.
Note that as the .mnu file specifies %MFOLDER%\Linux, we must place the ISO file in a Linux sub-folder or the menu entry will not be listed (because iftitle looks for the file in %MFOLDER%\Linux - e.g. \_ISO\LINUX\Linux).
Also note that for Linux we MUST get the case correct - I use Linux for most .mnu files not LINUX or linux!
Tip: If you use a non-ANSI character set, don't forget to save the file as UTF-8 format!
5. Boot the USB drive (use the QEMU button in RMPrepUSB for a quick check) and ensure that the menu entry is listed and at least starts to boot. if not check the paths you use in the .mnu and check for upper/lower-case letters.
6. Finally check that it works on a real system (or several real systems!).
Note: .mnu filenames can have spaces in them and do work but try to avoid filenames with spaces in them if possible.
If the original ISO file has spaces when downloaded, then you will need to use "\ " in the menu for each space character, e.g. for "My Big ISO.iso" you need to use, for example:
iftitle [if exist %MFOLDER%/My\ Big\ Iso.iso] Run My Big ISO.iso
map %MFOLDER%/My\ Big\ Iso.iso (0xff)
7. The User Instructions should be along the lines of:
Note that the .mnu files can be anywhere under the main (MFOLDER) folder - they do not have to be in the same folder as the ISO (payload) files. However, the .mnu files MUST be under the MFOLDER in order to be detected. If your .mnu file contains %MFOLDER% paths, then the main payload file must also be under the main MFOLDER. Also, the .mnu file does not have to contain the %MFOLDER% path reference - you can hard-code the path (e.g. /boot/bootmgr) in your .mnu file, but you must tell the user that they can only place the payload files in those specific folders on the Easy2Boot USB drive.
Always use iftitle rather than just title if at all possible to avoid misleading the user - when using iftitle with if exist - if the payload iso does not exist or is not in the correct folder, then no menu will be displayed for that file.
Menu titles can also be assigned a hotkey. See the hotkey section above for details.
Why not send me your .mnu files and I will add it the downloads at the bottom of this page or to the Easy2Boot Sample folder for others to use and enjoy (put your name in them for perpetual fame)!
You can create a .mnu file in the \_ISO\MAINMENU folder to have the Windows 7 install entry listed in the Main Menu, instead of needing to select 'Install Windows' from the Main menu and then select 'Install Window 7'. The first menu below is for a GFXMenu system, the 2nd one is for non-GFXMenu (normal) E2B systems. If you don't use GFXMenu's then just use the 2nd menu. The .mnu file you make can be any name you like (it will be alphabetically listed in the Main menu). C7 is the count of the number of ISOs in the WIN7 folder.
These menu entries can be found in the \_ISO\e2b\grub\MenuWinInstall.lst file. You can copy any of them to make your own .mnu file in the MAINMENU folder if you wish.
Many builds of WinBuilder have a special feature which will load the ISO file automatically as drive Y: on boot if an .INI file is found
For example, if you have a recent WinBuilder Win7PESE ISO, just place a file in the root of the E2B drive called Win7PESE.ini with the path and filename of you ISO you are using - e.g.
The filename may vary depending of what PE build you are using.
Alternatively, E2B recognises a special file extension of .isoPE and .isoPE01. These can be used for WinPE v2 (Vista), v3 (Win7) and v4 (Win8) based .iso files. If you use the .isoPE file extension AND the E2B boot drive is a 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:
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 be 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:
For WinBuilder PE ISOs, you can force it to load the Desktop icons by having a .cmd file on the E2B flash drive containing the correct commands - e.g.
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.
This functionality is in v1.07Beta03 and later versions.
Note: If you also add a .txt file for each ISO, then you can change the menu text displayed for each file.
If you set the ISOASK variable to 1 in E2B however, E2B will always ask the user how to boot every .iso file (just as if the iso file had a .isoask extension). To do this, edit the \_ISO\MyE2B.cfg file and add the line
to the end of the file (see \_ISO\Sample_MyE2B.cfg - bottom of file). This is only supported in v1.07Beta03 and later versions.
Note: If you set the file extension to .isodd then you will not be asked and E2B will boot from the .isodd file just the same as if it was a .iso file.
Another alternative (v1.07 and later) is to create a .mnu file for each iso file that requires a different extension for E2B. For instance, if you have a Hirens iso file and you want to run it with the .isowinvh file extension in E2B, but leave the hirens iso file with a .iso extension on the E2B drive, use this .mnu text:
Note: In this example, the .iso file and .mnu file should be in a \_ISO\xxxx\Utility folder (e.g. \_ISO\UTILITIES\Utility or \_ISO\MAINMENU\Utility).
The force.isowinvh is a dummy filename (any filename will do!) + extension. Whatever extension is specified in this first dummy parameter will be used to run the .iso file that is specified in the second parameter. So in this case, the Hirens .iso file will be run by E2B as if it had a .isowinvh file extension.
Easy2Boot can use a GFXMenu. A sample GFXMenu 'message' file is included in the download (\_ISO\docs\Sample E2B Templates\GFXMenu folder) together with a MyE2B.cfg file. Just copy these to the \_ISO folder to test them out. You can make you own GFXMenu (which has to be compiled each time you change it) by following Tutorial 21 here.
Your GFXMenu file must be in the /_ISO folder and you must specify the name in your MyE2B.cfg file, e.g.
This is the sample GFXMenu message file included in the download (with some extra ISOs added).
Note that hotkeys are not supported in GFXMenu, so you will need
to copy the ZZGFXSubMenuxxx.mnu files to the MAINMENU folder.
Using a GFXMenu has disadvantages:
If using your own compiled GFXMenu menu file (e.g. message), I strongly advise you to get your USB E2B drive tested and working first, without using your GFXMenu file - and then when it is all working correctly, try your GFXMenu. Some GFXMenus have been known to crash E2B (and display a small 'debug' box at the top left). You can instead try the sample GFXMenu file included in the \_ISO\docs folder in the E2B download.
Do not use hotkey entries (e.g. ^P) in any of the .mnu files or .txt menu files if using GFXMenu - it may cause the menu to crash when it loads!
Please don't ask me for any help making a GFXMenu - ask reboot.pro forum members instead or look here for a tool. I will only support grub4dos menus.
GFXMenus do not understand this hotkey notation, so if you are using a GFXMenu, you must copy the ZZGFXSubMenuxxxx.mnu files from the \_ISO\docs\GFXSubMenu Files folder to the \_ISO\MAINMENU folder (you can delete the \_ISO\MAINMENU\ZZSubMenuxxxx.mnu files if you are only using GFXMode). If you don't copy the ZZGFXSubMenuxxxx.mnu files, you will not see the ANTIVIRUS, BACKUP, DOS, etc. folders in the Main menu!
Tip: The Windows console mode menu's will look better if you change the standard console background colour to black in MyE2B.cfg e.g. color standard=0x%black%%%lcyan%
.Mnu files are simply normal grub4dos menu entries which are copied by Easy2Boot into one large temporary grub4dos menu which is held in memory. The %MFOLDER% variable is used to hold the main path (e.g. \_ISO\MAINMENU or \_ISO\BACKUP, etc.) so that the .mnu file can be used under either location. The file name of the .mnu file does not matter and can be changed - all .mnu files are collected. It is best to use the 'iftitle' command inside .mnu files so that the user can delete the 'payload' file and leave the .mnu file on the USB drive. The sub-folder names which have been pre-set under these two folders have no particular significance - but .mnu files are usually designed so that the payload file is in a specific sub-folder. Look at a .mnu file in the docs folder to see how they work.
These must go under the \_ISO\Windows folder in the correct sub-folder.
Vista and later OS Install ISOs also require an AutoUnattend.xml file to be on a removable drive (i.e. a USB Flash Drive). WinPE v2/3/4 picks up the AutoUnattend.xml file automatically as it searches all Removable drives for that filename.
See Tutorial 43 for more details of Vista and later OS installs.
Note: Your Windows XP Install ISO file must be in the \_ISO\WINDOWS\XP folder.
When using the 2-Step XP install option (see here for more details): Don't forget to download and add the Mass Storage drivers for automatic installation to AHCI/SATA/RAID/SCSI systems - see here for details.
The following instructions only apply if you answer 'No' to the 'Auto-detect DPMS' question in step 2a below.
If you are using DPMS2 then please follow the instructions here instead of the ones below.
1. Boot from your E2B drive, press W for the Windows menu and then Alt+1 for Step 1
2. Choose from the list of XP ISOs
2a. You will be asked if you want to use auto-driver detection (DPMS2) - say N=No
3. You will be prompted for 2 seconds to press Y if you want the ISO to be loaded into memory - for most systems this is not required.
4. You will see some instructions about pressing F6 - on some systems pressing F6 during Windows XP Setup is not necessary. So try not pressing F6 first.
5. Continue with the text mode setup and allow the system to reboot after the copy-files stage has completed
6. Reboot back to the E2B USB drive (do NOT allow the computer to boot from the internal HDD). Select W and Alt+2 for Step 2.
7. The system should now boot from the internal HDD and continue the GUI Setup phase of the XP install. It may be necessary to confirm the loading of some drivers during this phase.
8. Once XP has been fully installed, you can delete the storage drivers which show up as errors in Device Manager and then install all drivers for your hardware in the usual way.
These installs work in a similar way to Vista/7/8 installs, but only ImDisk is used:
The grub4dos batch file \_ISO\E2B\grub\QRUN.g4b (.g4b = grub4dos batch file) is run when the menu item is selected by the user. The QRUN.g4b batch file looks at the file extension of the payload file and performs a set of grub4dos commands depending on the file extension. If the file extension is not recognised by the QRUN.g4b batch file, no action is taken (as the correct label is missing - see below).
There are code sections in QRUN.g4b which are run depending on the file extension. The most common action occurs when an ISO file is selected and the code section for .iso is shown below:
Line 1 - The batch file label - a colon followed by the file extension. You can have more than one label so that the same commands will be run if (in this example) the extension is .isoxx or .iso.
Line 2 - The 2nd batch file label
Line 3 - This is the main reason why lots of linux ISO files can be booted. The partnew command creates a new partition entry on the boot drive (in the last table position of the 4 available on the Master Boot Record). The start sector of the partition points to the start of the ISO file (which must be contiguous). When linux boots, it searches for filesystems to mount. Linux sees the 4th partition as a CDFS filesystem and so mounts the 'ISO' as a CD/DVD. Now when linux goes on to look for more files (e.g. squashfs, etc.) it will find the files it needs on the mounted CDFS filesystem and proceed just as if it had booted from a CD/DVD. The partnew command actually writes to the MBR sector and so physically alters the MBR sector. The 4th partition table entry is checked by the main Easy2Boot menu to ensure it is empty first - if it was not empty then the 4th partition would be destroyed by this command and all data in it lost! As physical drive writes are involved, some emulators or VMs may not boot linux ISOs successfully using this technique.
Line 4 - This maps the ISO to BIOS device 255. The 2nd part of the command will never be executed as Line 3 would fail if the file was not contiguous.
Line 5 - This maps the firadisk floppy image to floppy device 0. If an XP ISO is booted, it will pick up the firadisk ramdisk driver from this floppy image. If a linux or DOS ISO is booted, it will just be ignored by the OS.
Line 6 - The BIOS mapping is hooked so that it takes affect
Line 7 - The (0xff) device is set as the root device. This has the affect of setting some CPU registers which some ISOs may require. If the root command fails, the rootnoverify is run instead.
Line 8 - This loads the ISO bootcode into memory ready to boot
Line 9 - This returns back to the grub4dos menu that originally called the QRUN.g4b batch file - the next line in the Easy2Boot menu will be 'boot'
If you wish, you can invent new file extensions (e.g. .iso_dave ) and add a new entry for it! Do not change the existing code as this will affect all files that have the same file extension, so copy new code below your :.iso_dave label and ensure it ends with 'exit'.
This partnew method for linux ISOs was originally mentioned by 'cdob' on reboot.pro, tested by me and closely followed by a loud cry of 'Eureka'!
I also discovered that you can map an ext2 file to a partition using partnew, so that linux will find and mount the ext2 file and use it for persistence (e.g. casper-rw) without needing to use special cheat codes. Some .mnu files use this trick and so (hd0,2), the 3rd primary partition is used for the ext2 file. So Easy2Boot USB drives requires both the 3rd and 4th partitition table entries to be unused. This also allows us to have multiple linux ISOs all using casper-rw as a persistent filesystem but actually using different files for the persistent file. For instance, we can use partnew (hd0,2) 0x0 /fileext2a for one ISO and partnew (hd0,2) 0x0 /fileextb for a different linux ISO (or even the same ISO but with a different persistence file!). As long as the ext2 files were created with the volume label of casper-rw (or whatever the linux version is looking for) then the linux ISO will mount the ext2 filesystem and use it.
Note that many linux editions will not automatically mount a persistent (e.g. casper-rw) file if it is on an NTFS filesystem volume. However, if you use this partnew trick then it will work and you can have persistence even on an NTFS volume!
IMPORTANT: you MUST run WinContig (RMPrepUSB - Ctrl+F2) before booting E2B. This is because ext2 files need to be contiguous - if they are not then partnew will not work but you may not see any error message.
RMPrepUSB v2.1.711 and later versions allow you to specify the filename and the volume name of the ext2 file separately - e.g. you can specify the filename as say BT5-rw and the volume label as casper-rw.
Note that because grub4dos loads the initial ram drive files, and linux then mounts the new partition(s), even if the linux SKU that is being booted does not support the NTFS file system at all, this technique should still work if the ISO is also mapped to a partition using partnew. This means you can also boot linux ISOs from exFAT Easy2Boot USB drives too!
Here is the BackTrack 5 .mnu file for reference:
Please let me know what you think of Easy2Boot and how it can be improved - Thanks!
If you already have a syslinux or grub4dos multiboot USB drive, you can add E2B to your USB drive as follows:
1. Download, extract and copy the E2B files to your existing multiboot USB drive. If you already have a \menu.lst file then do not overwrite it with the E2B menu.lst
2a. If you have a grub4dos menu.lst file, add in a menu entry to run E2B as follows:
2b. If don't already have a \menu.lst file and have a syslinux boot pen, add this to your syslinux menu
If you just want to use the same method of autorunning any payload file but don't want the E2B menu system, use QRUN.g4b in your menus, e.g.
You can also force qrun to run an iso as if it had a different extension, e.g. this will run the iso as if it had the .isowinvh file extension
Note: The %grub% parameter must be set by you to point to the folder that contains Qrun.g4b, so at the top of your menu.lst put
Don't get too excited though because many things won't work!
Simple ISOs like KonBoot, dban, plpbt or WinPE ISOs will work though. Hirens Mini XP will work if you use an extension of .isomem (.isoWinvH does not fully work with Mini XP).
The CD\DVD that you make will also support FASTLOAD so it does not have to enumerate all the ISOs each time it boots.
Here is what you need to do to turn your E2B Flash memory stick into a bootable CD/DVD:
1. Make a USB Flash drive (or USB HDD) with E2B
2. Add your payload files and test as normal
3. (optional) If you want FASTLOAD enabled on your final CD/DVD then copy FASTLOAD.YES to the root of the USB drive
4. (optional) If you have FASTLOAD enabled, boot the USB drive on a real system. Then reboot it to check that it loads the menu from cache correctly.
5. Run RMPrepUSB and select the USB drive - then type Ctrl+M (File - Make grub4dos ISO from drive). This will make a bootable ISO file.
6. (optional) Test the ISO using RMPrepUSB Ctrl+F11 (File - Boot from ISO using QEMU Emulator)
7. Burn your ISO (or copy it to a Zalman ZM VE-200/300/400 or IsoStick for testing).
I strongly suggest that you search all files on the USB drive for .mnu files that you are using and check that they don't use the partnew command - otherwise you could accidentally delete a partition on a hard drive!
I recommend testing E2B using Oracle Virtual Box and using DavidB's great new Virtual Machine USB boot application which allows you to add a USB drive to a VM and allows the VM full read/write access to the USB drive. QEMU from RMPrepUSB can also be used but it is rather slow (but has rd/wr access). Unless you have write access under the VM, some functions of E2B will not work.
To use DavidB's Virtual Machine USB Boot application - first make a VM in Oracle VBox with just one SATA virtual hard disk at SATA Port 1 and leave SATA Port 0 free. Then run VMStarter and create a new entry and set your E2B USB drive as the First USB drive. When you click on Start in VMS, the USB drive will be dismounted and the VM will then gain full read/write access to the USB drive.
If using VBox, you can set up a VM with VT-x/AMD-V acceleration when testing most features of E2B. However, you may find that the VM won't run XP Setup unless VT-x/AMD-V acceleration is first turned off. Once the text-mode stage has completed, you can turn on VT-x/AMD-V acceleration to run the 2nd GUI stage.
Note that Vista/Win7/Win8 (NT6) installs will not work correctly if you attempt to use a VM and install Windows to a virtual hard disk. You will see the message 'A required CD/DVD drive device driver is missing'. This occurs because Windows Setup will only load an Unattend.xml file from a Removable disk and any USB drive which is attached to a VM will be seen by Windows as a Fixed Disk. Therefore LOADISO.CMD will not run and the Windows ISO file will not be loaded as a virtual DVD before Setup starts to look for it.
To use E2B to install Windows Vista/7/8 in a VM, you will need to run LOADISO.CMD manually as follows:
1. Run the VM and boot to E2B
2. As soon as Setup loads and asks you for a language/country, press the key combination SHIFT+F10 - a black console window should open (if not, answer the next question and try SHIFT+F10 again)
3. In the console window, type dir C:\_ISO and press the ENTER key - if the folder is not listed, try dir D:\_ISO etc. until you find the E2B USB drive letter - let us assume that 'dir E:\_ISO' worked - then the USB drive letter must be E:
4. Now run loadiso by typing E:\_ISO\e2b\firadisk\loadiso,cmd - a blue console window should open - if then prompted to Repair Windows, just hit ENTER
5. The blue console Window should close - now continue with Windows Setup in the normal way.
This is not fully supported and there are some problems. Note that all files and file extensions are case sensitive in an ext2/3 grub4dos environment, so use .iso not .ISO, .txt not .TXT or .Txt.
Here is how I made an ext2 USB flash drive under Windows 7 64-bit
Note: Windows installs won't work as Windows cannot access the ext2/3 USB drive.
If you have payload files (but not Windows Install ISOs) in other partitions or even on other drives, you can add a new .mnu file for them and create a new menu entry for each partition/folder.
For instance, if you are using E2B from a USB hard disk that has two Primary partitions and you have payload files (e.g. ISO files) in the \_ISO folder on the 2nd partition of the USB hard disk, use the PTN2_Menu.mnu file (in the \_ISO\docs\Sample mnu files folder) and copy it to the \_ISO\MAINMENU folder.
The contents of the .mnu file are shown below for reference:
You can have two formatted Primary partitions on a USB Flash drive too - e.g. NTFS for E2B and large 4GB+ linux ISO files and .FAT32 for various DOS filesystems.
The PTN2_Menu.mnu file is only for payload files that will auto-run, such as linux liveCD ISOs or floppy disk images, etc.
Windows Install ISOs must be on the same partition as the Easy2Boot \menu.lst file and the rest of the Easy2Boot files. If you have large ISOs, you therefore need to place the E2B files and the Windows Install ISOs on the NTFS partition (i.e. use Config 1 or Config 4 below).
(hd0,0) PTN1 - NTFS - \menu.lst and \_ISO folder containing E2B files - Windows Install ISOs must be under \_ISO\WINDOWS\xxxx folders
PTN2 - FAT32 - \_ISO folder can contain payload files that will autorun using the PTN2_Menu.mnu file
(hd0,0) PTN1 - Primary FAT32 - \menu.lst and \_ISO folder containing E2B files - Windows Install ISOs must be under \_ISO\WINDOWS\xxxx folders (must be <4GB)
(hd0,1) PTN2 - Primary NTFS - \_ISO folder can contain payload files that will autorun using the PTN2_Menu.mnu file
If you modify the PTN2_Menu.mnu file and change (hd0,1) to (hd0,0) and change the name to PTN1_Menu.mnu then you can have:
(hd0,0) PTN1 - Primary FAT32 - \_ISO folder can contain payload files that will autorun using the PTN1_Menu.mnu file
(hd0,1) PTN2 - Primary NTFS - \menu.lst and \_ISO folder containing E2B files - Windows Install ISOs must be under \_ISO\WINDOWS\xxxx folders (must be <4GB)
--- OR ---
(hd0,0) PTN1 - Primary NTFS - \_ISO folder can contain payload files that will autorun using the PTN1_Menu.mnu file
(hd0,1) PTN2 - Primary FAT32 - \menu.lst and \_ISO folder containing E2B files - Windows Install ISOs must be under \_ISO\WINDOWS\xxxx folders
Note: the partition that has the \menu.lst file is considered by grub4dos to be the 'boot partition' (bd). That partition is expected to contain the E2B files and the \_ISO\WINDOWS\xxxxxx folders.
If you have some bootable files (e.g. DOS OS files) that need to be on a FAT32 partition (e.g. extracted files from the Hirens Boot CD), then you can copy and modify a .mnu file so that it will find the correct partition and set it as the root partition - e.g.:
We can make use of the fact the normal Windows systems can only access the first partition (first entry in the partition table is not necessarily the first partition on the disk) of a Removable drive - e.g. a USB Flash drive that is classed as 'Removable' (which is most USB Flash drives except for newer 'certified Windows8ToGo' USB Flash drives).
This means we can make an E2B USB Flash drive that will appear to contain a normal partition if anyone looks at it in Windows Explorer, but the other (hidden) partition will contain E2B and all our payload files.
1. Format a USB Flash drive using RMPrepUSB FAT32 - Size = xxxx (where xxxx is the size in MBs that you want for the E2B partition) - do NOT tick the 'Boot as HDD' box in RMPrepUSB as we don't want to add a small 2nd partition. Give it a volume label of E2B so you will know which one it is.
2. Add E2B and grub4dos etc in normal way and get E2B working with all your payload/ISO files, etc.
3. Use Easeus Home Partition Master to create a 2nd PRIMARY partition using remaining space on the USB Flash drive. It can be FAT32 or NTFS - it is up to you.
4. In RMPrepUSB - press CTRL+O and enter 2 when prompted. This re-orders the partition table so that the new empty partition is the first in the partition table
Now Windows will only see the empty partition but it will still boot to E2B! The user can add files to this partition in the normal way using Windows Explorer or whatever. Even if the end-user re-formats the partition it won't affect the E2B partition.
If you want to change the files on the E2B partition, just run RMPrepUSB - Ctrl+O and enter 2 to make the E2B partition the first one. After making your changes, run Ctrl+O again so that the other partition is the first one and visible to Windows.
If you want to have an E2B menu entry which will change the partitions over for you, add the E2B_PTN_SWAP.mnu file to the \_ISO\MAINMENU folder.
This will allow you to Hide or UnHide the E2B partition when booting to E2B. You can use this menu entry to unhide the E2B partition, then run Hirens or Win7/8 installs (these need E2B to be the first entry in the partition table) and then reboot back to E2B and hide the E2B partition again afterwards.
PassPass is a grub4dos batch file which patches a Windows DLL so that any user password will be accepted when you boot to Windows (written by Holmes.Sherlock, Wonko and co. from reboot.pro). The original batch file can be found here.
The version I made for E2B is here and contains the payload and .mnu files (read the .mnu file for instructions on how to add it to E2B).
With PassPass, you can take a backup of the DLL (optional), then permanently patch the DLL, then boot to Windows XP->8 and get into any user account (any password is accepted) and then change passwords to fix the problem. Then boot back to E2B and run PassPass again and either restore the original DLL from the backup or choose 'UnPatch' from the menu.
Technical details: The script tries to locate all existing Windows installations and corresponding Windows editions as well. Thereafter, it replaces the CMP instruction responsible for password verification with a ‘benign’ sequence of bytes. For reverting back the changes, the process is just the opposite. The whole idea is derived from WindowsGate and Astr0baby’s tutorial.