Grub2 menu system for E2B - early Beta available

The first Beta (Beta1  v0.01) is available for testing!

Please contact me if you want a copy to test. You will need a E2B USB HDD with a second partition.

It is possible to use this system on a Removable flash drive (but it is complicated because Windows cannot access the 2nd partition!).

Details are now published (in an early form) on the easy2boot website at http://www.easy2boot.com/uefi-grub2-ptn2/

Note that most of the linux menu items have been tested, but many of the other menus have not been tested with any payload at all yet.

MBR Main Menu

Grub2 support in E2B - progress report...

I have been spending quite a while thinking about the grub2 menu structure and it seems some people put E2B on the 2nd partition of their USB drive instead of the first partition. I don't advise this because of the 137GB BIOS bug, but as long as the 2nd partition ends before 137GB, it should work OK.

For payload files to be detected by the grub2 menu system, they must have specific lower-case names (e.g. avg.iso, konbootx64.efi). Files with names such as avg_arl_cdi_all_120_150814a10442.iso or "AVG AntiVirus.iso" will NOT be detected by the default grub2 menu system.

So there will be a large list of specific payload file names which I will document at a later date. As a consequence, you can only have one version of any ISO (though you can add your own uniquely-named payloadfiles and add your own grub2 menu for it).

Coming soon! grub2 UEFI-booting from linux ISO files using E2B

Currently you cannot directly boot from an ISO file via UEFI using Easy2Boot - you have to convert the ISO to a .imgPTN file first.

However, grub2 can UEFI-boot and can run linux ISOs (some of which will run even if the ISOs do not support UEFI-booting and do not contain an \EFI folder!).

The reason E2B does not use this mechanism is that some UEFI systems will only UEFI-boot from a USB disk containing both MBR and UEFI boot files - even if the system is set to boot from Legacy/BIOS devices.

This means that if you had grub2 UEFI boot files on your FAT32 E2B drive, then you can never boot to the E2B menu on these systems!

E2B not booting on GA-73PVM-S2H PC

Samir contacted me about a problem he had with his GA-73PVM-S2H PC.

He could boot from this PC to a USB drive prepared using Rufus (to Elemetary OS, for example), but not if it contained E2B.

The symptom was that the PC would just hang with no keyboard response or boot messages of any kind, as soon as he tried to boot from the E2B USB drive...

ESET + persistence from ISO

I finally figured out what the problem was with the ESET SysRescue ISO+Persistence menu that I did have working but then didn't work when I retested it. I had missed out the lines in the .mnu file which set the UUID of the 'live-media' - this meant that the live-media value was invalid and so it resorted to the CD updates. Also, you need to copy the ext3 partition from a working Eset flash disk (I cannot figure out what it is in a working ext3 image that is different from a non-working image made using RMPrepUSB 'Make ext2 FS' and copying over contents)!

I have also edited the menu now in the previous post (see lines in red).

So you can now boot from ISO with persistence if you wish, instead of using a .imgPTN file.

Add ESET antivirus with persistent updates to E2B with UEFI booting (Take 2!)

The method used in the previous blog uses an ISO with an ext3 file for the updates volume.

See also: ESET SysRescue 2020 with persistent updates and agFM UEFI support

Here is a different method using a partition image. The two methods are similar but you can add UEFI 64-bit booting if you use this method.

Note: Recent 2019/2020 versions of ESET use Ptn2 (488MB) for the persistence partition. Since the persistence partition must be at Ptn2 in the partition table, the method below will not work for the new partition arrangement because the old ESET used Ptn3.
For the 2019/20 version, the persistence partition must be labelled ESR-USB-DAT and must be ext3 and must be in Ptn2 (here is casper-bottom/12fstab init script extract: 

if ! /lib/udev/cdrom_id "$boot_device" > /dev/null; then
    # boot device is not a CD, so source the blkid info
eval $(blkid -o export ${boot_device%%[0-9]*}2)
if [ "$LABEL" = "ESR-USB-DAT" -a "$TYPE" = "ext3" -a -n "$UUID" ]; then
cat >> $FSTAB <<EOF
UUID=$UUID /mnt/eset-live-rw ext3 defaults 0 0
EOF
    fi
fi

Add ESET antivirus ISO with persistent updates to E2B (revised!)

For a different method using a .imgPTN file, please see the  next post!
______________________________________________________________________________

E2B can boot the ESET System Rescue ISO easily, but each time you have to download the latest updates which can take a while.

The current ESET disk eset-sysrescue.1.0.9.0.enu.iso does not support UEFI booting, but here is how to MBR-boot with persistence for updates, direct from the .iso file:

MPI Tool Pack v0.065

MPi Tool Pack 0.065 changes

• Add extra usb driver menu entry
• New grub4dos grldr version 20160326
• MakePartImage.cmd now searches all drives from C: to Z: for the ImDisk virtual drive (previously only searched up to U:).

Boot Ubuntu 32-bit via UEFI from Easy2Boot

The current Ubuntu 32-bit 'LiveCD' Desktop ISO does not include the 32-bit grub2 UEFI boot files, but you can use the procedure below to add the required boot files to allow you to UEFI-boot..

The procedure below can be applied to other 32-bit linux ISOs that use grub2, as long as a \boot\grub\loopback.cfg file is present (or you can add the relevant entries).

E2B 'Theme' in honour of Shakespeare

William Shakespeare was born around the 23rd April 1564 (his baptism was registered in the church records on 26th April) and died on 23rd April 1616 (400 years ago yesterday).

Here is an Easy2Boot theme to celebrate Shakespeare. Can you spot all the changes and hidden quotations?

Hope you like it!

Each menu entry has a different quotation. Do you know them all?

Note: Copy all files to your \_ISO folder (backup your own \_ISO\MyE2B.cfg file first).

The zip file contains a readme file and...

STRINGS.txt
MyE2B.cfg
Shaky.bmp

You can ignore the warning about STRINGS.txt being used for testing only. Just remember to delete it when you want to restore your own menu again.

Steve