Ventoy Forums

https://www.prime-expert.com/embootkit/

Download .exe and extract .iso file using 7Zip - Open inside #.

The 2.ISO boots OK using Easy2Boot legacy grub4dos and grubfm/agFM (Legacy partnew option and UEFI64), 

On Legacy and UEFI64 with Ventoy, I get the error

62089216 62089608 392
The size of the iso file "62089608" is invalid. File corrupted ?

(08-30-2021, 10:11 AM)Steve2926 Wrote: [ -> ]https://www.prime-expert.com/embootkit/

Download .exe and extract .iso file using 7Zip - Open inside #.

The 2.ISO boots OK using Easy2Boot legacy grub4dos and grubfm/agFM (Legacy partnew option and UEFI64), 

On Legacy and UEFI64 with Ventoy, I get the error

62089216 62089608 392
The size of the iso file "62089608" is invalid. File corrupted ?

skip file size check in grub.cfg function iso_common_menuentry

(08-30-2021, 10:11 AM)Steve2926 Wrote: [ -> ]https://www.prime-expert.com/embootkit/

Download .exe and extract .iso file using 7Zip - Open inside #.

The 2.ISO boots OK using Easy2Boot legacy grub4dos and grubfm/agFM (Legacy partnew option and UEFI64), 

On Legacy and UEFI64 with Ventoy, I get the error

62089216 62089608 392
The size of the iso file "62089608" is invalid. File corrupted ?

What is the exactly size of the 2.iso?  62089608 ?
This is a simple precheck in the grub.cfg script. 

According to the specifications of the ISO9660(ECMA119), an ISO file size must be multiple of 2048.
If the 2.iso file size is NOT multiple of 2048, it's invalid. Maybe it can work, but it doesn't meet the specification.
If the .exe always extract an iso file with size not multiple of 2048, then the .exe should do some change to meet the specification.

You can also use some other tool (e.g. UltraISO) to edit the ISO file to make an new/valid iso file.

Some user get a corrupted ISO file during copy, and run into problem when boot with Ventoy. So I add this simple check.

pre-check should warn user - and then allow you to try to boot the ISO anyway. It should not just fail?

'WARNING: VENTOY FILE SIZE CHECK FAILED - ISO FILE MAY BE CORRUPT...'

then user presses ENTER to try boot anyway.

(08-31-2021, 08:46 AM)Steve2926 Wrote: [ -> ]pre-check should warn user - and then allow you to try to boot the ISO anyway. It should not just fail?

'WARNING: VENTOY FILE SIZE CHECK FAILED - ISO FILE MAY BE CORRUPT...'

then user presses ENTER to try boot anyway.

Sounds reasonable.
I have commited the modification.

If I remove 'return' from grub.cfg in iso_common_menuentry, the ISO still does not boot
I get 'alloc magic is broken at..'
then I get 'Fatal error: sha256sum of kernel is not as expected (boot media corrupt).'

but same ISO boots OK using grub4efi and grubfm.

Does Ventoy require the ISO to be a multiple of 2048?

NO.
After test, I find ventoy has a bug  when do hook for this iso file.
But actually this iso file is a selfcontain LiveCD, so there is no need to do hook for it.
So you can press Ctrl+i to enter Compatible Mode and boot it.
I will add some check for this distro and auto enable compatible mode for it in the next release.

BTW, I run the .exe and get .iso file with size 62089216 which is multiple of 2048 and I don't get the warning message with Ventoy.
So I don't know why the .iso file size is 62089608 in your environment.

This CI release should work.
https://github.com/ventoy/Ventoy/actions...1185973047

ventoy 1.0.43 boot Emergency Boot Kit.iso ok

@nguyen ha thai trong
In this video, the VM is i386 arch (because it load /boot/32-bit/kernel)
It will fail if the VM is x86_64 arch (when it try to load /boot/64-bit/kernel).