Add 'Ventoy for Easy2Boot'

Ventoy is a grub2-based menu system for MBR\Legacy and UEFI booting of ISOs, etc. similar to agFM.

 

You can add Ventoy to your E2B+agFM USB drive for both MBR\Legacy+UEFI32+UEFI64 and Secure UEFI64 booting.

By adding Ventoy to E2B+agFM it allows us to Secure UEFI64-boot to Ventoy via agFM - Mok Manager is not required for Secure Boot if we first boot to agFM.

 

Ventoy only enumerates files that are in the first partition. You must use standard file extensions only (e.g. .iso, .vhd).

 

Ventoy is particularly good at booting WinPE-based ISOs because it can inject code into WinPE to mount the original ISO as a DVD drive - e.g. drive Y:. This means that all the programs and Desktop icons should work correctly even if the ISO does not support the WinBuilder .ini file method of loading the ISO as a DVD drive. Ventoy may not be suitable if your system has limited RAM or you are booting very large ISO files.

 

'Ventoy for Easy2Boot' v1.0.32 and later supports Legacy, UEFI32 and UEFI64 (use agFM v1.69 or later).

 

First - you must update the E2B USB drive to agFM v1.66 or later using \eb2\Update agFM\Download and update agFM_v2.cmd.

Or update to the latest Beta of agFM (if available) by extracting the files from the .zip file directly to the root of the second partition of the E2B USB drive.

The 'Ventoy for Easy2Boot' version is an unofficial 'fork' of Ventoy which has been patched and recompiled to work on an E2B USB drive.

 

Windows 10 is required if you are using an E2B USB Flash drive because only Win10 (recent versions) can access Partition 2 of a flash drive.

 

1. Update your E2B+agFM USB drive to E2B v2.06 or later and update to agFM v1.66 or later.
    
2. Download an official Ventoy Windows .zip file from the Ventoy depository (v1.0.27 is the last unblocked version - later versions of Ventoy will not run from an E2B USB drive unless they are the E2B version!). You can instead download any 'Ventoy for Easy2Boot' zip file from the E2B Alternate Downloads archives (recommended).
    
3. Drag-and-drop the Ventoy .zip file onto the  \e2b\Update agFM\Add_Ventoy.cmd file on your E2B drive (in the agFM partition 2).
    
4. If you have downloaded an 'official'  Ventoy zip file - The latest Ventoy (blocked) version of core.img is fetched from the Ventoy server. This will not work when Legacy booting is tested. An older (unblocked) version of core.img file will be needed. You can directly download an older (unblocked) version of core.img from here for use with Ventoy v1.0.28 and later. The core.img file should be extracted and placed in the \ventoy folder on Partition 2 to support MBR\Legacy booting from the E2B Main menu. The file \ventoy\core.img is not present inside the official Ventoy .zip file but it is required for MBR\Legacy booting via the E2B menu system.
   If you are not online, you can download the current core.img file from https://github.com/ventoy/Ventoy/blob/master/INSTALL/grub/i386-pc/core.img and add it to the agFM Partition 2 \ventoy folder. You can directly download an older (unblocked) version of core.img from here. The core.img file should be extracted from this .zip file and replace the existing core.img in the \ventoy folder on Partition 2 to support MBR\Legacy booting (even if Legacy Ventoy v1.0.28 or later).

Windows XP/7/8 users can first switch to the 2nd partition (using Switch_E2B.exe - 'Access partition 2 on Removable drive' button) and then drag-and-drop the downloaded Ventoy .zip file onto the \e2b\Update agFM\Add_Ventoy.cmd file. Don't forget to switch back partitions 1 and 2 afterwards using the same button in Switch_E2B.exe!

Instructions for using Ventoy and for modifying the Ventoy menu system are on the Ventoy website.

 

Create a new \ventoy\ventoy.json on the first partition of the E2B USB drive to configure Ventoy.

See the Ventoy plugins pages for more details.

 

You can see sample  configuration files in the \ventoy\Sample Ventoy config files folder. These can be copied to the \ventoy folder on Partition 1 (the NTFS partition).

 

 

menuentry "Load agFM Menu" --class=custom {

if [ "${grub_platform}_${grub_cpu}" = "pc_i386" ]; then

linux ${vtoy_efi_part}/e2b/loadfm

initrd ${vtoy_efi_part}/e2b/grubfm.iso

else

    if [ "$grub_cpu" = "x86_64" ]; then chainloader ${vtoy_efi_part}/grubfmx64.efi; fi

    if [ "$grub_cpu" = "i386" ]; then chainloader ${vtoy_efi_part}/efi/boot/bootia32.efi; fi

fi

}

if [ "${grub_platform}_${grub_cpu}" = "pc_i386" ]; then

menuentry "Load Easy2Boot Menu" --class=custom {

insmod ntldr

set root=${vtoydev},1

ntldr ${vtoy_iso_part}/grldr

}

fi

submenu 'My Custom SubMenu -->' --class=customsub {        

    menuentry "My Custom Menu2" --class=custom2 {

        echo 'This is custom menu2 ... '

        sleep 1    

    }

    menuentry '<-- Return to previous menu [Esc]' --class=vtoyret VTOY_RET {

        echo 'Return ...'

    }

}

menuentry '<-- Return to previous menu [Esc]' --class=vtoyret VTOY_RET {

    echo 'Return ...'

}

 

menuentry "Boot Micron Firmware Updater" --class=custom {    

    isofile=/_ISO/LINUX/1300_revM5MU30_bootable_media_update.iso

    loopback microncd $vtoy_iso_part$isofile

    linux  (microncd)/boot/vmlinuz64 libata.allow_tpm=1 quiet base loglevel=3 waitusb=10 superuser mse-iso rssd-fw-update rssd-fwdir=/opt/firmware rssd-force-update

    initrd (microncd)/boot/corepure64.gz    

}