Legacy BIOS Access Range Limitation
There is an access limitation in some Legacy BIOS of some vendors. For example, some Legacy BIOS can't read the disk beyond 137GB.
If you search "Legacy BIOS 137GB" in the internet, you will get many informations about that.
So if that's the case with the BIOS in your machine and you install Ventoy into a USB drive with large capacity(eg. 256GB), you will run into problem when booting.
- Typical behavior
1. This problem is Legacy BIOS only, UEFI is OK.
2. Directly dropped into a grub shell when boot Ventoy
3. Works fine with a small USB drive(eg. 32GB)
- Why no problem with other tools (eg. Rufus)
When you make a bootable USB with other tools like Rufus, the USB drive will be reformatted and all the data in the ISO will be written into the USB from the begginning.
So normally these data will not exceed the BIOS limitation and there is no need to read data from where is out of the range during boot.
But with Ventoy, as mentioned in Disk Layout, the 2nd partition is at the bottom of the USB disk. So it need to read data out of the Legacy BIOS limitation immediately after boot.
- Reformat the 1st partition manually (NTFS/exFAT ...)
- Copy ventoy.disk.img.xz to the 1st partition
To make sure that the file in step 2 will be saved within the BIOS access range.
ventoy.disk.img.xz from the install package (under ventoy directory). Create a
ventoy directory in the 1st partition and copy
ventoy.disk.img.xz into it.
/ventoy/ventoy.disk.img.xz in the 1st partition.
It should be noted that, this is just a workaround. There is no software solution for the BIOS limitation. If all the ISO files are within the valid range, there will be no problem. But if you put many many ISO files to the USB disk and some of them will be out of the range. For these ISO files, BIOS can't read them and
there will definitely be problems when boot them.
Just for Legacy BIOS mode, although this workaround is used for the limitation of the BIOS, but it can also be used to avoid the situation where the data of the 2nd partition is damaged. Because the workaround proces is to get data from the file mentioned above when failed to access the 2nd partition. The access failure may be due to the limitation of the BIOS, or the file may be damaged.