• Categories
• Unidad flash USB
• Archivo de computadora
• Arranque
• Bios
• Sistema de archivos

Citation preview

Boot all your ISO's from one USB drive! Contents 1. 1 Introduction 1. 1.1 Three ways to add 'payload files' to E2B 2. 2 E2B Version History 3. 3 Thanks for your help, feedback and support! 1. 3.1 Easy2Boot Introductory video 4. 4 How to make a new Easy2Boot USB drive 1. 4.1 Quick Instructions (video) 2. 4.2 Quick Instructions (text) 3. 4.3 Really Detailed Instructions 4. 4.4 3. Download E2B 5. 5 Getting Started - How to add payload (.ISO) files to Easy2Boot 1. 5.1 TWO GOLDEN RULES FOR E2B PAYLOAD FILES 2. 5.2 FAQs 3. 5.3 Error 60: File not contiguous 4. 5.4 E2B Upgrade Packages 5. 5.5 List of tested ISO files that just work! 6. 6 Easy2Boot - Detailed Description and Help 1. 6.1 Using the Easy2Boot menu 2. 6.2 Adding your bootable payload files 3. 6.3 Where to add your (.iso, .ima, etc.) files 7. 7 TroubleShooting (and Error Messages)! 1. 7.1 Common problems with payload files 8. 8 The Easy2Boot folders and menu system 1. 8.1 Main Menu Appearance 2. 8.2 Easy2Boot Folder Structure 3. 8.3 Included payload files 4. 8.4 Windows Install ISO files 9. 9 E2B File Extensions used for Payload Files 1. 9.1 Suggested File Extensions to use for different ISOs 10. 10 Testing E2B v1 1. 10.1 Themes included in the latest E2B download 11. 11 Installing Windows from an E2B Hard Disk (instead of an E2B Flash drive) 12. 12 Installing Windows XP using the two-step FiraDisk (Setup/F6) method 13. 13 Install Windows XP using the WinPE method (winnt32.exe) 1. 13.1 How to make a WinPE ISO 2. 13.2 Using the 'Install XP using WinPE' menu option 3. 13.3 Booting to WinPE 14. 14 Advanced (unattended) Windows Installs 1. 14.1 Unattend.txt files for XP installs 2. 14.2 Unattend.xml files for Vista\Win7\SVR2K8R2 installs 3. 14.3 Unattend.xml files for Win8\SVR2012 installs 4. 14.4 Modifying User Unattend.xml files to work with Easy2Boot 15. 15 Add WindowsToGo to your USB drive 16. 16 Setting your own preferences (MyE2B.cfg) 1. 16.1 Changing the background/wallpaper image 2. 16.2 Removing the background image or using text mode 3. 16.3 Change the Keyboard Layout 4. 16.4 Specifying the Main menu order and/or the menu items 5. 16.5 Change the menu headings 6. 16.6 Change text colours and border colours 7. 16.7 Change the menu box size and position 8. 16.8 Remove grub4dos and E2B startup messages 9. 16.9 Changing the Language 10. 16.10 Menu password protection 11. 16.11 Beep 12. 16.12 Add a new folder entry to the Main Menu

13. 16.13 Adding 'Install Windows xxx from ISO' menu entries to the Main menu 14. 16.14 Removing the DOS, BACKUP and UTILITIES Main menu entries 15. 16.15 Change the way that payload files are listed in the menus 16. 16.16 Hotkey support 17. 16.17 Prevent the menu items from being automatically numbered 18. 16.18 Remove or change the 'Boot to first HDD [F7]' menu entry 19. 16.19 Remove or change the 'Reload Main Menu [F8]' menu entry 20. 16.20 Remove the 'Reboot [F9]' menu entry and function 21. 16.21 Remove the 'Power Off [F10]' menu entry and function 22. 16.22 Add blank lines as separators to a menu 23. 16.23 Remove the 'Set default menu entry and timeout' Main menu entry 24. 16.24 Only show the Windows Install menu 17. 17 Speed up loading of the Main Menu 1. 17.1 Suppress text messages on startup 2. 17.2 Counting Windows ISO Files 3. 17.3 Don't load the font file on start-up 4. 17.4 Don't use a graphics bitmap 5. 17.5 Delete the xml files from the root 18. 18 How to make an Easy2Boot .mnu file 1. 18.1 Example: Adding the Windows 7 menu entry to the MAIN Menu 19. 19 Adding WinPE (WinBuilder) v2/3/4 ISOs 20. 20 Using a Zalman USB Hard Disk caddy 21. 21 GFXMenu Support 22. 22 Easy2Boot - How it works 1. 22.1 .MNU Files 2. 22.2 Windows Install ISOs 3. 22.3 .ISO/.IMA/etc. Booting 23. 23 Adding E2B to your own multi-boot USB drive 24. 24 Convert your E2B USB drive into a bootable CD or DVD 25. 25 Testing E2B using an emulator or Virtual Machine 26. 26 Using E2B on an ext2/ext3 USB drive 27. 27 Including payload files from other drives or partitions 1. 27.1 More than two partitions 28. 28 Make a 'secret' E2B partition on a USB Flash drive 29. 29 PassPass - Bypass the Windows User Account Password 30. 30 Downloads

Translate this Tutorial >>> NEW! v1.15e - see bottom of page. How to make an E2B USB drive, click here. Then just copy over all your ISO files and boot! List of tested ISOs here. Example themes, see here. Easy2Boot Forum is here.

Please subscribe to my blog for changes, bug fixes and news. Any Problems? - Contact Me Various Downloads are at the bottom of this page. New YouTube video I have put a lot of hours of hard work into Easy2Boot and it is totally free! 4GB with FAT32!) 5. Copy OS Files - Extract='NO' - set to the path of the Easy2Boot .zip file you downloaded in step 2 6. Click 6 Prepare drive (this will erase all contents) 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 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. Really Detailed Instructions PLEASE NOTE: If you going to use an existing USB drive without re-formatting it, please run Windows Disk DEFRAG on it first, followed by WinContig to defragment all files (use RMPrepUSB - Ctrl+F2) BEFORE you start to copy your large ISO files to it. If you do not do this, you may find that some of the files on the drive are not contiguous and you will get 'Error 60: file not contiguous' if you try to boot from them! Defragging and running WinContig can take a long time on a nearly full drive. I would recommend that you copy all your files to a folder on your internal hard disk, follow the partition+format procedure below to prepare a USB drive for Easy2Boot, and then copy all your files back again - it will be MUCH quicker if there is not much free space on your USB drive! If you want to put E2B on your mobile phone's SD card then check that the SD card is formatted as FAT32 (use the RMPrepUSb DriveInfo button) and then use RMPrepUSB to install grub4dos to the SD card (when in USB Mass Storage mode). Then simply unzip and copy over the E2B files. Now add your payload files and you then will have a mobile phone that will allow you to boot a PC from it and run any linux LiveCD or WinPE or Hirens, etc. etc. To make a new bootable E2B USB drive: The steps below in outline are: 1. Partition+Format a USB drive (at least for initial testing, I recommend using a USB Flash drive rather than a USB hard disk) 2. Install grub4dos 3. Download and extract the E2B files to the USB drive 4. (optional) Add Mass Storage drivers from DriverPacks.net (if XP install ISOs are added)

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. 1. Make the following selections (numbered 1 to 6) in RMPrepUSB 1. Partition Size - MAX (or whatever size you want for the partition, e.g. 2000 for 2GB) 2. Volume Name - Easy2Boot (or whatever name you like!) 3. Bootloader Options - WinPE v2 4. Filesystem and Overrides - FAT32 + Boot as HDD, or use NTFS +Boot as HDD if you have files larger than 4GB exFAT+Boot as HDD can be used instead if you want to format as exFAT (but is not recommended) 5. Copy OS Files - (leave unticked) - or tick it and set this to the path of the E2B zip file and skip step 3 6. Click 6 Prepare drive (this will erase all contents) 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). Note: If you are using a USB Hard Drive and you want to install Windows from an ISO - You need to also follow the instructions here to make an additional 'Helper' Flashdrive. 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) 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. Note: If you find that it does not boot to grub4dos on some systems, repeat the grub4dos install but this time install grub4dos again to the MBR (answer 'Yes' instead of 'No') - this may improve compatibility with different BIOSes of different systems (solves 'flashing-cursor' on boot that is seen on some systems) or it has been reported that on some systems it prevents booting! Note that installing to the PBR on exFAT filesystems is not supported, so as you can only use MBR, you may get a 'flashing cursor' bad boot on some systems if you use exFAT. 3. Download E2B Now extract the files from either: Easy2Boot download [6MB] OR E2B+Windows XP Mass Storage Drivers [30MB] if you want E2B + XP Mass Storage drivers already added - see Tutorial 72b for more details). Note. The features described in this Tutorial relate to the latest version of E2B. The download links above may not always be the very latest version. Check the bottom of this page for the latest vesion and the blog for recent change details. 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.

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. Getting Started - How to add payload (.ISO) files to Easy2Boot It's as easy as: 1 - Copy file to E2B drive 2 - run WinContig 3 - Boot 1. Copy: If you just want to get going - simply copy a payload file (e.g. a linux Live CD ISO) to the \_ISO\MAINMENU folder or if it is a Windows Install ISO... copy all Windows Install ISO files to the relevant folders under \_ISO\WINDOWS (e.g. if it is a Windows 7 Install ISO, copy the ISO to the \_ISO\WINDOWS\WIN7 folder). 2. Run WinContig: IMPORTANT: After adding any of your own payload files (e.g. ISO files) - remember to run WinContig (Ctrl+F2 in RMPrepUSB) to make all files contiguous and avoid the dreadedError 60: File not contiguous error! 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. 3. Boot: Now boot from your USB drive! That's it!

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

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. TWO GOLDEN RULES FOR E2B PAYLOAD FILES  E2B will only detect payload files that are in folders at the \_ISO\XXXXX level  E2B will automatically detect .mnu files that are in folders at the \_ISO\XXXXX level AND any subfolders underneath that level. 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... FAQs 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 Install ISO? Copy the ISO file to \_ISO\Windows\XP folder. To install XP 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 to an AHCI/SCSI/RAID PC using a standard XP Install ISO? You need to copy the Mass Storage driver pack files to the E2B USB drive (the XP 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.

If you only have one Hirens iso and if you want all functions to work it is best to extract the files from the Hirens ISO and use a FAT32 formatted USB drive: Extract the contents of the Hirens iso to the root of the E2B drive using 7Zip. Copy the \_ISO\docs\Sample mnu files\HirensBootCD_Extracted.mnu to \_ISO\MAINMENU (or any E2B folder below \_ISO). If booting from an NTFS E2B USB drive, some DOS utilities will not work - to fix this, boot to Hirens miniXP find and run the \HBCD\Dos\dosimg.cmdfile - follow the instructions to make a new Dos .img file. How do I add YLMF/Ubuntu/Fedora/StartOS/Porteus/pclinuxos/Backtrack5/k ali-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, 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: ? - rename the ISO file to .isoPE (or .isoPE01 if you want the USb drive swapped over with the hard disk). Use a USB Flash drive for E2B - OR - if using an E2B hard disk, add a 'Helper' flash drive before booting the PE ISO from the E2B menu. 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 Error 60: File not contiguous 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. E2B Upgrade Packages 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. Try

FlashBoot

for

99%

Bootability!

RMPrepUSB can make a USB drive bootable, but some older BIOSes may have problems. I recommend FlashBoot if you need to create a USB drive that will boot on 99% of systems. Please click here to test a trial version and see if it works for you. Click here for a Tutorial on how to use FlashBoot with Easy2Boot. List of tested ISO files that just work! 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. 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). 1. Windows XP Home/Pro, Windows Vista, Windows 7, Windows 8, Server 2012, Server 2K8R2 2. raring-dvd-i386.iso Edubuntu 13.04 Alpha 1 Test Build 3. systemrescuecd-x86-3.1.2.iso SystemRescueCD 4. xbmcbuntu xbmcbuntu-12.00-RC1.Intel-NVIDIA.iso (see end of this page for .mnu file for persistence) 5. AVG Rescue CD 120.120823 AVG Rescue Toolkit CD ISO here 6. Kaspersky Rescue CD 10.0.31.4 Kaspersky Rescue Disk ISO here (also .mnu file available so can have updates stored on USB drive) 7. Bitdefender Rescue CD 2.0.0 Bitdefender ISO here (.mnu available for persistency - keeps downloaded updates in memory - see Tutorial 10 for details) 8. Dr Web AV CD 9. Rising AV CD 10. VBA Rescue CD 11. EScan Toolkit 12. Anvi Rescue Disk 13. Panda Safe CD 4.4.3.0 Panda Security ISO here 14. GParted Live CD 0.14.0-1 Gnome Partition Editor ISO here 15. PartedMagic 2012_11_30, 2012_11_30.iso 2013_05_01.iso Parted Magic ISO here 16. Partition Wizard Bootable CD 7.6.1 Partition Wizard ISO here 17. EaseUS Todo Backup Free 5.0 EaseUS Todo Backup Free ISO here

18. EaseUS Disk Copy Free 2.3.1 EaseUS Disk Copy Features ISO here 19. EaseUS ToDo Emergency Disk 20. Partition Wizard Home Edition pwhe78.iso 21. PandaSafeCD.iso 22. Darik's Boot And Nuke 2.2.7 Darik's Boot and Nuke (DBAN) ISO here 23. Ophcrack XP Live CD 3.4.0 Ophcrack sourceforge ISO here Extra instructions here 24. Ophcrack Vista/7 Live CD 3.4.0 Ophcrack sourceforge ISO here Extra instructions here 25. KonBoot 2.1/1.1 Piotrbania Kon-Boot [Free] ISO here (requires .mnu file FD0-konboot-v1.1-2in1.mnu from docs folder) 26. Offline NT Password & Registry Editor 110511 Pogostick Offline NT Password & Registry Editor ISO here 27. Ultimate Boot CD 5.1.1, 5.2.3 Ultimate Boot CD ISO here [Mirror] 28. Ubuntu 12.10, 13.04 Ubuntu & Canonical ISO here - use .mnu file to run with persistence 29. HDT 0.5.2 HDT ISO here 30. Memtest86+ or latest passmark version (recommended) 31. WebConverger 16.0 Boots to a web browser 32. LPS DoD 33. Microsoft Windows Memory Diagnostic windiag.iso (made by mtinst.exe) 34. PING 3.02 - pdf manual - details on advanced menu for backup here 35. HDDGuru MHDD Magic Boot Disk (DOS based but works for non-SATA drives) 36. BootMed 37. Puppy Linux Precise ISO precise-5.4.3.iso Lucid Puppy Linux 5.1 (for Save/persistence on USB Flash Drive you need the Puppy_Precise_USB_Flash_Persistence.mnu file, forUSB HDD you need Puppy_Precise_USB_HDD_Persistence .mnu) 38. Knoppix V7.05 KNOPPIX_V7.0.5CD-2012-12-21-EN.iso 39. SeaTools Seagate HDD DOS ISO SeaToolsDOS223ALL.ISO (Press I for Ignore if using an emulator) 40. WD Drive Fitness Test dft32_v416_b00.iso 41. Acronis True Image 2013 (useful how to use Acronis here) 42. Tails (if booting from USB HDD or requiring persistence, you need to use the tails_HDD.mnu file - persistence only works on USB sticks (broken in 0.20 though!). (http://tails.boum.org/) 43. BackTrack 5 44. Mepis 11.0.12 SimplyMEPIS-1.5G_11.0.12_32.iso (SimplyMEPIS-1.5G_11.9.86_32.iso MEPIS 12 BETA requires a .mnu file) 45. ArchLinux 2012.12.01 46. Rescatux 0.30.2 ISO here 47. MultiSystem 12.04 ms_lts_precise_r6.iso 48. Ylmf OS - Start OS (press F2 for English when main menu displays) 49. Linux Mint 14 Nadia linuxmint-14.1-cinnamon-dvd32bit.iso 50. g4l 51. finnix 52. android_x86 android-x86-4.3-20130725.iso

53. pclinuxos-kde-fullmonty-2012.09.iso Full Monty pclinux KDE4 3.9GB (works from FAT32 or NTFS USB drive) 54. lglive-0.9.7-i686-hybrid-lite.iso live linux gamers iso 55. Zorin zorin-os-6.2-core-32.iso 56. openSUSE-12.3-GNOME-Live-i686.iso 57. Fedora-18-i686-Live-LXDE.iso (to boot from Fedora 18 LXDE ISO with persistence, download the Fedora_Persistent.mnu file at the bottom of this page) 58. Lightweight Portabile Security ISO LPS1.4.0_public.iso 59. MiniTool Partition Wizard Free boot CD (pwhe7.iso) 60. BitDefender Rescue CD 61. Boot It bare Metal - BootIt.iso 62. Linux Secure Remix Boot (linux-secure-12.10.1032bit) 63. Boot-Repair boot-repair-disk.iso 64. Kali kali-linux-1.0.2-i386.iso (with persistence if use .mnu file) 65. TinyCore-current.iso 66. Core-current.iso 67. CorePlus-current.iso 68. grml64-small_2012.05.iso grml-full_2013.02.iso 69. inx-1.1.iso 70. ttylinux-x86_64-16.0.iso 71. dls-4.11.rc1.iso 72. Windows Defender Offline ISO (download the latest mpam-fe.exe update and place in the root of the USB drive) 73. HP Vision Diagnostic ISO (must copy all folders except \BOOT and \SOURCES to the root of the E2B USB drive) and boot from ISO 74. Symantec Encryption Desktop 10.3Win32_WDE_Recovery.iso (rename .isowinv) 75. Windows 7 Recovery CD 76. easypeazy 1.6 (for netbooks) site 77. RIPLinux 13.7 ISO 78. Gentoo install-x86-minimal-20130423.iso 79. Falcon F4's UBCD - F4UBCD-4.6.iso (MiniXP will work if just use extension .isowinvH - but to get all working use the F4UBCD.mnu in the latest E2B download and follow the instructions) 80. Avira AntiVir Rescue System - rescue_systemcommon-en.iso and Restore CD SATA.iso 81. Joli OS ISO - web browser OS 82. LSoft ActiveBootDisk.iso Active@ Boot Disk - Must make the ISO using the utility. Use .iso or .isomem extension. Extract the BOOTDISK.KEY, _bootDisk.ini and bootcat.ini files from the ISO and put them in the root of the E2B USB drive or will get Serial Key prompt (note: the bootcat.ini file may not be required as it seems to work without it). 83. Mandriva mandriva-linux-PWP-2011-i586.iso - use as .iso - I got the 'No CDROM device found' message - but if you continue you can load the ISO....OK, Which driver should I try to gain MEDIA access? ---> Cancel, Please choose installation method. ---> Hard disk, Please select the disk containing the copy of the Mandriva linux Distribution --->sdb, Please select partition --> sdb4, Please enter directory ---> / . Alternatively use the mandriva-linux-PWP-2011-i586.mnu file in \_ISO\docs folder. 84. Windows For Legacy PCs (winflp) 85. PicoXP

86. 87. 88. 89. 90. 91. 92. 93. 94.

Windows 7 PE SMS (http://sms.it-ccs.com/) Hirens 8~15.2 use .isowinvh or .isomem file extension UBCD 5.2.2 (http://www.ultimateb...m/download.html) Phanton Clone 1.5.0 (http://www.phantomclone.com/) Gold Memory (http://www.goldmemory.cz/) iBoot (http://tonymacx86.bl...ac-os-x-on.html) PING 3.02 (http://ping.windowsdream.com/) System rescue CD 3.4.2 (http://www.sysresccd...scueCd_Homepage) 95. Spotmau Boot Suit 2011 (http://www.spotmau.c.../bootsuite.html) 96. 4mlinux http://4mlinux.com/news.html 97. brlix http://www.brlix.com/ 98. hdat2 http://www.hdat2.com/ 99. Slitaz 100. Debian 7 (NetInstall, Small/Tiny, Live) KDE, Gnome, LXDE, XFCE, Standard, Rescue) - debian-7.1.0-i386netinst.iso - when prompted for CD-ROM, select 'none' and enter in path of \dev\sda4 101. RIPLinux 13.7 (tiny x86 and x64) 102. POS2009 (rename .iso to .isowinv and extract \i386 and \win*.* to root of USB drive - see \_ISO\docs\sample mnu files for details) 103. PassPass - grub4dos batch file which can patch a Windows Dll so that any user password will be accepted (by Holmes.Sherlock and co. at reboot.pro) - see here for payload and .mnu file. 104. F-Secure Rescue CD (works on real system). 105. LUbuntu 13.04 (for persistence use the lubuntu-13.04desktop-i386.mnu file and follow the instructions inside it) 106. KDENLive debian-live-dvd-20090704.x32.iso http://www.poure.com/kdenlive/debian-live-dvd20090704.x32.iso 107. Strelec 108. GeexBox GeexBox-3.0-i386.iso - required rootfs file to be extracted from the ISO and placed in root of the USB drive. .mnu available for persistence (experimental!) 109. bg-rescue 3.0 http://www.giannone.ch/rescue/current/#Downloads 110. JonDonym https://anonymous-proxyservers.net/en/jondo-live-cd.html 111. Mageia 3 http://www.mageia.org/en/3/ 112. Slax (use a .mnu file provided and extracted ISO contents if you require persistence - FAT32 only) 113. AX64 Time Machine Recovery Media ISO file 114. VMWare ESXi 5.1 ISO 115. CentOS ISOs - use the .isoforce file extension 116. GeekSquad GS MRI 5.7.2.iso - for MRI PE: use 7Zip to extract 8 folders: \Compression utilities, \Diagnostics, \Disk Management, \Malware, \Web Browsers, \Windows tools , \MRI , \sources and the \mri.exe file to root of E2B drive. Use Daemon Tools Pro or similar utility to delete the first 7 folders from the 1.2GB ISO and re-save the ISO to reduce it to 184MB. The ISO files listed below do not 'just work' and may require a .mnu file and/or extraction from the ISO files.  Haiku - DOES NOT WORK!  Trinity Rescue Disk DOES NOT WORK unlesss type sdb4 (if USB drive is 2nd drive) (tip from saddlejib on reboot.pro - to list drives type blkid in linux bash prompt and then type reboot) - see tutorial #58 to see

     

how to get it to work automatically by making a FAT16 image. ReactOS LiveCD - must extract all files from the ISO and use the .mnu file in docs folder igel ISO DOES NOT WORK - see tutorial 38 for workaround. Arcanix AOSS OpenElec Installer - see my blog here for how to run this from E2B. OpenELEC LIVE - run XMBC direct from the Easy2Boot menu even on an NTFS USB drive - see here for instructions.

Easy2Boot - Detailed Description and Help Please Note: This will be for the latest version - check the Downloads at the bottom of this page for the latest version! Using the Easy2Boot menu 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!

Adding your bootable payload files Once you have made your bootable Easy2Boot USB flash drive, you can simply copy over more bootable ISO or other bootable files to the correct folder.  To start, just copy over your new payload file (e.g. a linux xxxxx.iso) into the \_ISO\MainMenu folder and it will be listed in the first (Main) menu when you boot from the USB drive. Try it now and boot from it - see if it works!  If you have a Windows Install ISO, they are a 'special case' and these must go in the correct \_ISO\Windows\xxxxx\ sub-folder  If anything does not work correctly, check the Troubleshooting section below.  For all files except Windows installs - once it is working, you can move the file (and it's .txt file if you made one) to one of the other \_ISO\XXX menu folders if you wish (under any sub-folder that is appropriate - see below) so that it is listed in a sub-menu. If you cannot get it to work even by changing it's file extension, see if there is a .mnu menu file for it in the docs folder and read the text in the .mnu file and the section below on how to use it. Once you have a .mnu file working (read the text inside it!) in \_ISO\MainMenu\xxxx, you can move it to one of the other \_ISO\xxxx\yyyy folders if you want it listed in a different sub-menu instead of the Main menu.  If you still can't get it to work - look in the reboot.pro forum or email me! Always run WinContig to ensure all files are contiguous (quickly done in RMPrepUSB, just press the keys Ctrl+F2). Where to add your (.iso, .ima, etc.) files Easy2Boot folders Note: If a folder is empty (contains no sub-folder or file), the menu entry won't appear in the E2B menu.  E2B will automatically detect payload files that are in folders at the \_ISO\XXXXX level  E2B will automatically detect .mnu files that are in folders at the \_ISO\XXXXX level AND in any subfolders under that level. 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 subfolder 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 nul 2. To \_ISO\MyE2B.cfg add: !BAT set NOF8B=0 set NODEFMENU=0

3. (optional) Delete all ZZxxxxxxx.mnu files in \_ISO\MAINMENU Speed up loading of the Main Menu If you find that the Main menu takes too long to enumerate all your files and create a new menu on every boot, copy the file \_ISO\FASTLOAD.YES 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!). Suppress text messages on startup 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: set redir=> nul If you also want to suppress the initial E2B startup messages (not recommended), use: set redirp=> nul Counting Windows ISO Files 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): !BAT set CXP=3 set CV=0 set C7=5 set C28=1 set CT8=9 set C12=0 set CALL=9 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. Don't load the font file on start-up 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!): set NOUNIFONT=1 Don't use a graphics bitmap 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. Delete the xml files from the root 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! How to make an Easy2Boot .mnu file This part is 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.

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).

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?).

Also note that for Linux we MUST get the case correct - I use Linux for most .mnu files not LINUX or linux!

e.g. files are: /_ISO/MNU/Linux/Ylmf_OS_3.0.mnu /_ISO/MNU/Linux/Ylmf_OS_3.0.iso 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 map /_ISO/Linux/Ylmf_OS_3.0.iso (0xff) map --hook root (0xff) kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper iso-scan/filename=/_ISO/Linux/ylmf_OS_3.0.iso floppy.allowed_drive_mask=0 splash initrd /casper/initrd.img The converted Ylmf_OS_3.0.mnu file... # Download ISO file from http://www.ylmf.org/en/download.html # MD5: 919794E3D9B035A5A895C3E1D1818F95 # SHA1: 6E672A667155E442A612F69CCBA1BF6C44752D8D # INSTRUCTIONS: Copy this file and Ylmf_OS_3.0.iso to the /_ISO/MainMenu/Linux folder or /_ISO/MNU/Linux folder 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 find --set-root %MFOLDER%/Linux/Ylmf_OS_3.0.iso map %MFOLDER%/Linux/Ylmf_OS_3.0.iso (0xff) map --hook root (0xff) kernel /casper/vmlinuz file=/cdrom/preseed/ubuntu.seed boot=casper isoscan/filename= %MFOLDER%/Linux/ylmf_OS_3.0.iso floppy.allowed_drive_mask=0 splash initrd /casper/initrd.img 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.

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) map --hook root (0xff) chainloader +1 7. The User Instructions should be along the lines of: # Download xxx.iso from here # Copy the xxx.iso and the mnu file to /_ISO/xxxx/yyyy folder on your Easy2Boot USB drive # Check the MD5 hash of the ISO file is correct - it should be MD5=aaaaaaaaaaaaaaaaaaaaa # Run WinContig to ensure the file is contiguous AFTER you have copied it to the USB drive (use RMPrepUSB Ctrl+F2). 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)! Example: Adding the Windows 7 menu entry to the MAIN Menu 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. iftitle [if %C7%>=1 && if not "%GFX%"==""] Install Windows 7\n Install Windows 7 from an ISO file. set LBACKMENU=/%grub%/MenuWinInstall.lst /%grub%/VistaMn.g4b .automenu Win7 configfile (md)0x3000+0x50 boot iftitle [if %C7%>=1 && if "%GFX%"==""] ^7 Install Windows 7 (%C7% present)\n Install Windows 7 from an ISO file. set LBACKMENU=/%grub%/MenuWinInstall.lst /%grub%/VistaMn.g4b .automenu Win7 configfile (md)0x3000+0x50 boot

was called \_ISO\WINPE\Winpe\123.iso, then here are 4 different examples of what could be in your 123.cmd file: set ISOLETTER=S: REM run \_ISO\WINPE\Winpe\123_Custom.cmd after the ISO file has been loaded as a virtual drive set POSTCMD= %~pn0_Custom.cmd set ISOLETTER=S: REM run \_ISO\WINPE\Winpe\xyz.cmd after the ISO file has been loaded as a virtual drive set POSTCMD= %~p0xyz.cmd set ISOLETTER=S: REM Run a cmd file from the E2B USB drive after the ISO file has been loaded as a virtual drive set POSTCMD=%USBDRIVE%\xxx\yyy\zzz.cmd set ISOLETTER=S: REM Run a cmd file from the ISO after the ISO file has been loaded as a virtual drive set POSTCMD=S:\xxx\yyy\zzz.cmd

[7]

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.

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. Adding WinPE (WinBuilder) v2/3/4 ISOs 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.

This functionality is in v1.07Beta03 and later versions.

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 \_ISO\MAINMENU\PE3x86.isoPE01

the

iso

was

Note: If you also add a .txt file for each ISO, then you can change the menu text displayed for each file. Using a Zalman USB Hard Disk caddy If you have a Zalman USB Hard Disk, then it can load any .ISO file located under the \_ISO folder and emulate a CD/DVD drive. That is why E2B specifically uses the \_ISO folder to store it's payload files. You may find that you need to rename the file extension of an ISO file in order to get it to work in E2B - for instance, you may need to rename a WinPE .iso file to .isoPE. However, if you change the file extension, then the Zalman will not recognise the file and so the Zalman software will not list the ISO 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 set ISOASK=1 to the end of the file (see \_ISO\Sample_MyE2B.cfg - bottom of file). This is only supported in v1.07Beta03 and later versions.

at

The .cmd file should contain a line similar to the one below: set ISOLETTER=S: In this way, you do not need to remember what drive letter each different ISO uses, once you have made the .cmd files for each of your WinPE ISO files. If you require a .cmd file to 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

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:

title Hirens ISO\n Boot direct from Hirens ISO\n Boot Hirens from ISO /%grub%/qrun.g4b force.isowinvh %MFOLDER%/Utility/Hiren's.B ootCD.15.2.iso boot 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. GFXMenu Support 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. set GFX=message

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:  Any error will take you to the grub4dos textmode menu  Hotkeys don't work  No titles at the top of the menus  No help text is displayed for each menu item  No menu footer text at the bottom of the screen  Cannot set the default menu entry or timeout  Cannot show the number of files present in each folder  When it switches to the text-mode console to list files, etc. it looks a bit messy.



You cannot define the resolution, wallpaper, text colours or menu position in the MyE2B.cfg file (must be done in the GFXMenu file and recompiled)  Password protection does not work  Uses a larger font so less items per screen.  Cannot use the cursor keys to scroll from end to beginning (cursor stops on last item)  Variables are not translated to text in menu entries, so you can't use a variable in a title xxxx line. 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% Easy2Boot - How it works 1. Easy2Boot starts from \_ISO\E2B\grub\menu.lst. The number of files under \_ISO\Windows are counted - if no files are found, then the Install Windows entry is not shown in the Main menu. 2. All files (except .cmd, .txt and . ) in the \_ISO\MainMenu folder are then enumerated in alphanumeric order and added to the Main menu (subfolders are also searched for .mnu files) 3. If there are one or more ISO files in \_ISO\Windows or below, the Windows Install menu is added to the Main menu. .MNU Files .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. Windows Install ISOs 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. Sequence for VISTA and later OS’s (e.g. Win7/8) 1. Easy2Boot overwrites \AutoUnattend.xml with correct contents (and changes Product Key if required) 2. Windows Setup PE boots 3. WinPE looks for \AutoUnattend.xml file on any REMOVABLE DRIVE (e.g. USB Flash drive or CD/DVD) 4. Runs WindowsPE RunSynchronous command 5. Finds and runs \_ISO\E2B\FiraDisk\LoadIso.cmd (or if, in Win8PE, this fails to load, ImDisk is used instead) 6. Windows ISO is loaded as a new virtual DVD (e.g. J: ) 7. User asked if they want to Repair Windows (answer N for Windows Install) Note: If you answer No, you may be offered to run Startup Recovery (StartRec.exe), OS Repair (RecEnv.exe) or MSDart32 if they are present in the ISO. 8. Setup.exe is run 9. Setup can find \Sources\Install.wim file on virtual DVD drive and will list all OS versions inside the Install.wim 10. Note that after a reboot and in the final 'Completing installation' phase - Setup will look for a \Unattend.xml in the root of all removable media. For this reason, the \Unattend.xml is filled with an empty but valid .xml entry. If a blank Unattend.xml is seen, Setup will complain about an invalid Unattend.xml file! See Tutorial 43 for more details of Vista and later OS installs. Windows XP Installs using the 2-Step + F6 method 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 instructions here instead of the ones below.

follow

the

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. Only press Y if you get a BSOD when using Step 1. 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. If you get a BSOD in Step 1 or XP cannot detect your internal hard drive, then reboot and press F6 and select FiraDisk32+WinVBlock32. If you have a system which uses a SATA AHCI HDD controller, also add that driver too. See Tutorial 30 for how XP ISO installs work using FiraDisk/ImDisk. See here for a list of AHCI drivers included with the F6 XP install process used in E2B. You can identify your AHCI controller using the List Disk Controller PCI IDs [L] menu. 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. Windows XP install using Vista/7/8 WinPE 'Helper' ISO These installs work in a similar way to Vista/7/8 installs, but only ImDisk is used: 1. Easy2Boot overwrites \AutoUnattend.xml and \Unattend.xml with \_ISO\E2B\FiraDisk\auwinnt.xml 2. Windows Setup or PE boots 3. WinPE Setup looks for \AutoUnattend.xml file on any REMOVABLE DRIVE (e.g. USB Flash drive or CD/DVD) WinPE looks for \Unattend.xml when wpeinit runs. 4. PE runs the WindowsPE RunSynchronous command from the .xml file which then looks for and runs LoadIsoW.cmd 5. \_ISO\E2B\FiraDisk\LoadIsoW.cmd loads the XP ISO as a virtual drive and then runs \_ISO\E2B\FiraDisk\RUNWINNT.cmd 6. RUNWINNT.cmd prompts the user and formats, or wipes and partitions the target drive and runs winnt32.exe with the correct command line parameters. .ISO/.IMA/etc. Booting Payload files (e.g. .ISO. .IMA, etc) which are placed in the \_ISO\MAINMENU folder (not sub-folders under \_ISO\MAINMENU) and in other \_ISO\XXXX folders (not subfolders) are automatically listed in a dynamic menu which is made in memory. Files which have .txt, .cmd, .mnu and . (no extension) are not listed in the menu. If a .txt file exists that exactly matches the payload filename, the text from inside the .txt is used as the menu entry title instead of just the payload filename (so the text in the .txt file should always start with the word 'title' followed by the grub4dos menu text that you want displayed). 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: 1. :.iso 2. :.isoxx 3. partnew (hd0,3) 0x0 %1 4. map %1 (0xff) || map --mem %1 (0xff) 5. map --mem /grub/firadisk.gz (fd0) 6. map --hook 7. root (0xff) || rootnoverify (0xff) 8. chainloader (0xff) 9. exit 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'! Booting linux ISOs with persistence

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.

partnew (hd0,3) 0x0 0 0 0 if not exist (bd)/BT5-rw echo WARNING: /BT5-rw persistence file not found! && pause errorcheck off if "%check%"=="0x00" partnew (hd0,2) 0x0 (bd)/BT5-rw errorcheck on

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!

Please let me know what you think of Easy2Boot and how it can be improved - Thanks!

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: # For persistence, create an ext2 file called casper-rw in the root of the boot drive using the RMPrepUSB - Create ext2 FS button # Then rename the file to BT5-rw (do NOT create a file called BT5-rw - you MUST create a file called casper-rw and then rename it!) # Place ISO in \_ISO\Mainmenu\linux or \_ISO\XXXX\Linux (and this .mnu file too) # DOES NOT WORK UNDER VM!!! Run WinContig after copying all files to the USB drive. iftitle [if exist %MFOLDER%/Linux/BT5R2-GNOME-32.iso] BackTrack 5 (1024x768) Persistent\nType startx to run GUI once booted #enable parttype output debug 1 # make empty table entry in 3rd position in ptn table parttype (hd0,2) | set check= debug off set check=%check:~-5,4% if "%check%"=="0x00" partnew (hd0,2) 0 0 0 if not "%check%"=="0x00" echo WARNING: PTN TABLE 3 IS ALREADY IN USE! && pause debug 1 #clear ptn 4

map %MFOLDER%/Linux/BT5R2-GNOME-32.iso (0xff) map --hook partnew (hd0,3) 0x0 (bd)%MFOLDER%/Linux/BT5R2-GNOME32.iso root (0xff) kernel /casper/vmlinuz file=/cdrom/preseed/custom.seed boot=casper persistent text splash noprompt vga=791-initrd /casper/initrd.gz

Adding E2B to your own multi-boot USB drive 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: title Run Easy2Boot set grub=_ISO/e2b/grub configfile /%grub%/menu.lst 2b. If don't already have a \menu.lst file and have a syslinux boot pen, add this to your syslinux menu LABEL Easy2Boot MENU LABEL Easy2Boot BOOT /grldr 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. title Run xxxx.iso /%grub%/qrun.g4b ()/_ISO/MAINMENU/xxxx.iso title Run Hirens /%grub%/qrun.g4b ()/_ISO/MAINMENU/Hirens.isowinvh 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 title Run Hirens /%grub%/qrun.g4b force.isowinvh ()/_ISO/MAINMENU/Hirens.iso 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 set grub = _ISO/e2b/grub Convert your E2B USB drive into a bootable CD or DVD

You can easily make an ISO from the drive which you can then burn as a bootable E2B CD or DVD. Don't get too excited though because many things won't work!  Windows XP via WinPE installs and Win8/SVR2012 installs won't work (Vista/7 and XP step1/2 may work but I have not tested them!).  Many linux ISOs won't work unless you use a .mnu file which has special cheat codes in it - this is because I can't use the partnew command on a CD! WARNING!!!: If you have used any of the old sample .mnu files for linux ISO's - remove them before you boot from the E2B CD!!!! These .mnu files will wipe the 4th partition of your hard disk without warning if you boot from an E2B CD/DVD!!!!! 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! Testing E2B using an emulator or Virtual Machine 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. Using E2B on an ext2/ext3 USB drive 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 64bit 1. Download and install Ext2Fsd to add ext2/3 filesystem support to Windows 2. Download and run Easeus Home Partition Master and format your USB drive as ext2 or ext3 3. Run Ext2Fsd and allow write-access to the USB drive 4. Run RMPrepUSB and install the WEE bootloader to the USB drive (Ctrl+W) 5. Extract the E2B files onto the USB drive 6. Add your payload files 7. Make all files contiguous (I am not sure how to do this under Windows as the Ext2Fsd driver seems to make all files non-contiguous!) Note: Windows installs won't work as Windows cannot access the ext2/3 USB drive. Including payload files from other drives or partitions 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: # EXAMPLE .MNU FILE FOR 2ND PARTITION # You can add payload files under \_ISO on partition 2 and they will be included in the menu # EDIT lines 1 and 3 to match the name of your folder and partition # Add this file to the /_ISO/MAINMENU folder iftitle [ls (hd0,1)/_ISO/ > nul && if "%GFX%"==""] ^Ctrl+2 PARTITION 2 Payload Files Menu [Ctrl+2]\n Run payload files in Partition 2 \\_ISO folder set LBACKMENU=(bd)/%grub%/menu.lst (bd)/%grub%/QAUTO.g4b .automenu (hd0,1)/_ISO configfile (md)0x3000+0x50 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. 1. Prepare the USB Flash drive using RMPrepUSB but enter a reduced Size (e.g. 40GB for a 64GB Flash drive) and format it as NTFS but do NOT tick the 'Format as HDD' box. 2. Then install grub4dos (to MBR and PBR) and copy over the E2B files. 3. Then add the second FAT32 or NTFS partition using EaSeus Home Partitions Master. 4. Then in RMPrepUSB, press Ctrl+O to swap Windows access over to partition 2 (choose 2). 5. Now create a _ISO folder on the 2nd partition and copy over any payload files that you want to run automatically. 6. Then press Ctrl-O again to swap back to the E2B NTFS partition (choose 2 again). 7. Add the PTN2_Menu.mnu file to \_ISO\MAINMENU folder 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). Config 1 (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 --- OR --Config 2 (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