Steve's blog about RMPrepUSB, Easy2Boot and USB booting. Please tick one of the 'Reactions' boxes if you enjoyed a post.
Visit www.rmprepusb.com for over 130 Tutorials on USB booting or www.easy2boot.com for a unique USB multiboot solution.

Instructions are basically the same as for memstick images - see here (bottom of page).

For instance, you can MBR-boot to OPNsense ISOs (OPNsense-17.7.5-OpenSSL-dvd-amd64.iso) by creating a dummy .imgPTN file and removing the file extension from the ISO file so it is also loaded as a partition image.

To check if your ISO is compatible, load the ISO into 7Zip and look for a \boot\loader file inside the ISO.

Note: FreeNas .ISO files do not work using this method. You must use FreeNAS memstick images instead.

Geek notes

It is not possible to boot directly from the ISO using a simple menu such as:

Sunday, 29 October 2017

If you have a sufficient knowledge of Windows to be able to repair a damaged or infected Windows system, you will know that it is not that easy.

For instance, although you may be able to boot to the infected Windows system, it may not allow you to run any .exe executable or use any browser.

So i just wanted to make you aware of Carifred's software for technicians. Not only do they offer free versions with very few limitations, but it also seems to provide the exact tools that an experienced Windows repair technician needs. The full licences are also very reasonably priced too.

This blog post is just a 'heads-up' to draw your attention to this software if you haven't come across it before.

P.S. v1.96 could report a !BAT missing error under some conditions (e.g. no MyE2B.cfg), so I have released a bugfix version called 1.96A. If you already have v1.96, just download v1.96A and click the Update_E2B button to update your 1.96 E2B drive.

Tuesday, 17 October 2017

Early versions of Ubuntu (pre-v14) and Ubuntu-based linuxmint distros (pre-v17.03) could be set up with persistence with no problem.

As long as you added the 'persistent' boot parameter, the kernel script would look for either:

1) a 'casper-rw' file (formatted internally as ext2/3/4)

- OR -

2) a FAT or ext partition with a volume label of 'casper-rw' which has been formatted as ext2/3/4.

Ubuntu bug!

However, Ubuntu 14.04 and linuxmint 17.03 and (all?) later versions have a bug in the casper boot script which means that they may fail to boot when a casper-rw partition is present and if that partition is located after the filesystem partition in the partition table. This bug does not apply if you booted from an ISO file (only from a 'flat-file' partition), so the .mnu files used by E2B which boot from ISOs are not affected by this bug.

So there is no problem if you use a casper-rw file (except it must be on the same partition and it must be a FAT32 or ext partition). So you can create a very large (>4GB) ext3 file on the E2B NTFS USB drive and use a .mnu file to get persistence - but this only works in MBR\Legacy mode.

For UEFI-booting, we need to create a FAT32 .imgPTN file. However, this issue does affect E2B when using .imgPTN partition images...

Tuesday, 10 October 2017

In this version, if you have created a matching .txt file for your payload file, then E2B will not suggest an alternative file extension (unless SCROLL LOCK is on) and will boot straight to the payload file with no delay.

e.g.
\_ISO\LINUX\Ubuntux64.iso
\_ISO\LINUX\Ubuntux64.txt

I have reasoned that if you have taken the trouble to make a .txt file, then you have already tested it and it works and so has the correct file extension.

This message and delay is now suppressed if a .matching txt file exists.

If you don't like this new feature, please let me know and I will remove it.

E2B 1.96d is available from Alternate Downloads Areas as usual (see side panel on this page).

Wednesday, 4 October 2017

Following on from my previous blog post on PEStartup, I have written Tutorial #143 on how to use PEStartup to configure any ready-made WinPE OS such as Strelec, Hirens, DLC, Dium and Gandalf WinPEs.

In fact, standard Win10PESE WinBuilder builds including the latest Gandalf Redstone 2 WinPE and Bob Om's PEs 'just work' and will automatically run PEStartup when they boot, if you follow the Tutorial (you just extract files from a .zip file onto your E2B drive!).

If the WinPE does not have the correct plugin already, you just need to double-click on the \TheOven_Startup.cmd script to run PEStartup and configure your WinPE Desktop.
Many thanks again to Tứ Nguyễn for his PEStartup utility.

Tuesday, 3 October 2017

Download from here. It is based on WinBuilder and ChrisR's Win10PESE project.

To add to E2B, just copy the .iso file to a menu folder (e.g. \_ISO\WINPE) and run \MAKE_THIS_DRIVE_CONTIGUOUS.exe to make it contiguous.

To suppress the tips and extension suggestions made by the QRUN.g4b script when you run it, just add the letter Q or q to the end of the filename. e.g.
Gandalf'sWin10PEx64Redstone2_10-01-2017q.iso

Do not uses spaces in the filename. If you want to change the menu entry and have spaces in the filename, use a .txt file - e.g. Gandalf'sWin10PEx64Redstone2_10-01-2017.txt

To change keyboard locale press CTRL+TAB.

Tip: if you add PEStartup to your USB drive and PortableApps.com (Start.exe) to the Desktop as Startup options. you can use the Shutdown/reboot button in the PortableApps GUI to shutdown/reboot (as the Start Menu Shutdown\Reboot does not work). You can also add lots of PortableApps apps easily too. Gandalf Redstone 2 will automatically run PEStartup 20 seconds after it loads the Desktop.

In a chat session with 'Nathan' today, he explained how he uses VBox to install Windows to a Virtual Machine using ISO files on an E2B USB drive.

Testing E2B's 'Install Windows from ISO' method in a Virtual Machine is problematic because Windows needs to detect a Removable drive (e.g. CD\DVD or USB flash drive) in the system - Setup will only pick up the \AutoUnattend.XML (or \Unattend.XML) file from removable drives.

However, under a VM, a USB drive is 'mapped' as a virtual (IDE\SATA etc.) hard disk when using a .vmdk file (so the drive is not seen as a Removable drive once WinPE\Windows Setup runs).

This means the Product Key and other settings in the XML file are not used by Windows Setup when testing in a VM.

We can get around this by booting in two stages and by adding a USB WinHelper drive: