1. Emulate a WinHelper USB flash drive
Before booting from the IODD 2531 to E2B, use the jog switch to load the file:
Now boot from the IODD 2531 to E2B.
You will see the new virtual Winhelper USB Flash drive, USB CD and real USB HDD appear as boot options in a BIOS menu.
Pick the IODD 2531 USB HDD option.
E2B will now 'see' a second removable USB drive containing the WinHelper flash files, so we can now install Windows using Windows 7/8/10 ISOs without needing to connect an extra flash drive to the system or use .imgPTN files. Neat eh?
E2B v1.84+ contains the file: \_ISO\docs\USB FLASH DRIVE HELPER FILES\E2B_WinHelper_&DW.zip
From this file you can extract E2B_WinHelper_&DW.RMD.
2. Boot to WinPE and run WinNTSetup (with write-protected real HDD)
If you want to boot to UEFI-boot and install Windows 7/8/10 using WinNTSetup, then instead of switching to a .imgPTN file (which may not be possible if you have no Windows system available) and then booting to that UEFI image, you can just load the IODD 2531 with the WinPE file (ISO file or VHD or .DSK).
This means you can boot straight to UEFI WinPE and run WinNTSetup directly from the real HDD.
You will need to use the &D filename suffix (e.g. WinPEx86_&D.ISO or WinPEx64_&D.iso) so that the real hard disk is also accessible but write-protected.
If you want the real HDD to be write-enabled, use a &DW suffix - e.g. WinPEx86_&DW.VHD or WinPEx64_&DW.VHD
You can, of course, MBR-boot in the same way and have a write-protected real HDD. For instance, you could safely test any WinNTSetup diskpart scripts without fear of zapping the real HDD inside the IODD 2531 (though you could zap the VHD file).
You can choose one of the SDI_CHOCO XML files from the E2B \_ISO\WINDOWS\xxxxx folders and run an automated installation if you wish.
Note: If you load an .ISO file into the IODD 2531, the real HDD will not be write-protected unless you press-and-hold the top function button whilst you connect it (or use the Advanced menu via the jog switch). The padlock icon will tell you the state of the real HDD (locked symbol=wp, unlocked=write-enabled).
3. Make a virtual E2B Removable USB drive
The IODD appears as a Fixed Disk, but E2B works best on a Removable drive (or else you need to add a Helper flash drive - see #1 above).
If you make an image of a complete E2B USB drive as a .RMD file, the IODD can load it as a removable USB drive. You can then edit it, add payload files, etc. just as if it was a real flash drive.
You can use RMPrepUSB to capture a raw image of any E2B USB drive. The size of the USB drive will determine the size of the image file.
RMPrepUSB - Drive->File - - start=0 - end=PALL* - filestart = 0
*Note that for best bootability, you should capture both the first E2B partition and the hidden small partition that was made by the E2B make script.
Copy the E2B.RMD file to the IODD hard disk (e.g. \_ISO\E2B.RMD).
When you load the E2B.RMD file into the IODD, it will create a rd\wr virtual E2B drive, but the whole real HDD will be hidden. This means that the worst damage you can do is to destroy the E2B image file, but all other files on the HDD will be inaccessible (or you can make them accessible but write-protected). It also means you can test E2B as a removable USB drive.
If you use a .DSK file extension, then the E2B USB drive will appear as a Fixed disk.
If you add a &DW suffix (e.g. E2B&DW.RMD) then the whole HDD will also be accessible and not write-protected (or use &D if you want it write-protected).
Note that E2B cannot handle payload files that are on a different drive (because of the way it uses the grub4dos partnew command to make partitions on the E2B drive, the payload file must be on the same drive). Also, it needs a write-enabled drive, so you cannot enable write-protection on an E2B drive without severely limiting it's function.