By special request, you can now make an ISO run as if it had a different file extension under E2B by changing it's filename...
v1.A9c allows any extension to be used (not just ending in .iso) and does not display the ._xxxxx part in the menu either (so Ubuntu 64-bit_.imgptn23auto.imgptn appears in the menu as Ubuntu 64-bit).
ubuntu64_.isodef.iso will run without prompting the user.
Filename format: filename_.forceextension.iso
Note: _. is mandatory, forceextension can be any extension recognised by E2B.
v1.A9c allows any extension to be used (not just ending in .iso) and does not display the ._xxxxx part in the menu either (so Ubuntu 64-bit_.imgptn23auto.imgptn appears in the menu as Ubuntu 64-bit).
ubuntu64_.isodef.iso will run without prompting the user.
Force a different file extension (E2B v1.A9+)
Note: _. is mandatory, forceextension can be any extension recognised by E2B.
Examples: msdart6_.isoPE01.iso (runs as if .isoPE01)
Windows8_x64_.isodef.iso (does not prompt user with suggestions)
For example, if you have an ISO file but you want it to run as if it had a .isofira01 file extension, you can add _.isofira01 as a file override to the end of the filename but before the file extension of .iso.
A file 'myxp.iso' can be run as if it had the .isofira01 file extension if you give it a name myxp_.isofira01.iso.
Windows8_x64_.isodef.iso (does not prompt user with suggestions)
For example, if you have an ISO file but you want it to run as if it had a .isofira01 file extension, you can add _.isofira01 as a file override to the end of the filename but before the file extension of .iso.
A file 'myxp.iso' can be run as if it had the .isofira01 file extension if you give it a name myxp_.isofira01.iso.
This means that the file will keep the .ISO extension which may be more convenient if you are using a Zalman\IODD device as your E2B drive or if you want to keep the file extension unchanged for other reasons such as loading it into ImDisk or an ISO editor or mounting it with Windows Explorer.