Using QEMU or Virtual Box for testing
TEST USING A REAL SYSTEM IF A VM DOES NOT APPEAR TO WORK AS EXPECTED.ALWAYS RE-TEST USING A REAL SYSTEM TO ENSURE IT WILL WORK CORRECTLY IN REAL LIFE!
If testing Windows Install ISOs using a Virtual Machine, ensure that you set 2GB RAM or more in the VM.
QEMU_MENU_TEST (run as admin).cmd
- You can use this to select a .imgPTN file from the E2B menu and switch to it (or just use \SWITCH_E2B.exe). If Windows Explorer does not show you the new USB drive contents after switching to a .imgPTN image, unplug and reconnect the E2B USB drive.
- 64-bit OS's cannot be run.
- Because QEMU emulates a CPU, it is quite slow to run.
- File writes to USB are temporary - e.g. any files that are changed whilst running under QEMU will not be permanently changed.
QEMU (in RMPrepUSB)
Oracle Virtual Box
I highly recommend using Virtual Box v5.2 + VMUB (I use this for all my E2B boot testing!).
Setup VBox using these instructions --> How to use Da vidB's Virtual Machine USB Boot application.
Download VMUB h e re.
Tip: Create an Administrator shortcut on your TaskBar for VMUB. Always launch Oracle VBOX Manager using the button on VMUB.
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 VMUB and create a new entry and set your E2B USB drive as the First USB drive. When you click on Start in VMUB, the USB drive will be dismounted and the VM will then gain full read/write access to the USB drive.
Make sure you run VBox and VMUB with Administrator privileges - I suggest you set up shortcuts for each one with the Run as Admin box ticked.
I reccomend you do not use VBox v6 until a new version of VMUB is available, use VBox v5.Workaround for VBox v6 (--startvm error):
VMUB - Options - VirtualBox - Exe Path = C:\Program Files\Oracle\VirtualBox\VMUB.cmdSee blog post here.
Running E2B under VBox+VMUB or QEMU
- The E2B USB drive will appear as Drive 0 even after booting to Windows or Linux.
- The E2B USB drive will appear as a IDE\SATA\RAID drive in the VM and not as a USB drive
- The E2B USB drive will appear as a Fixed disk and not as a Removable device.
- XML files will not be automatically used by Windows Install ISOs because the USB drive is not seen as a 'Removable' drive by WinPE ('CD/DVD drive driver required' message is seen). If E2B uses WIMBOOT however, the XML file will be used (E2B v1.A8).
- Add set NOHELPER= to the end of the MyE2B.cfg file
- The QEMU\VBox virtual BIOSes do not have the 137GB USB access BIOS bug - but some real systems do!
Do not use Plop! - Plop! uses a read-only USB driver stack. Unless you have write access under the VM, E2B will not work, which is why Plop! is not suitable to use to boot from an E2B USB drive - see FAQ for more details.
If you boot to E2B using Plop! then hold down the SHIFT key as E2B boots to load the grub4dos USB 2.0 driver or see here for more details on using Plop!
Windows Vista/7/8/10 Installs under a VM
- The system should contain more than 1300MB of RAM (system memory).
- The ISO must be a standard Microsoft Windows Install ISO.
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.
Note that the XML file contents will be ignored in this case.
Note that Windows may overwrite the MBR and PBR of the E2B USB drive if it is HDD0 in the VM.
Installing Windows 7/8/10 using XML files
If you want to use a Product Key or unattended install settings, please see this page.
If using a 'DiskWipe' automated unattend XML file, when the virtual hard disk is configured as HDD1 and the USB drive as HDD0 (as with VBox+VMUB) you will need to use a 'WipeDisk1' XML file because a 'WipeDisk0' XML file will cause the E2B drive to be erased by Windows Setup!
Recommended for Easy2Boot (fastest!) - SanDisk Extreme SDCZ880-128G-G46