On some ISOs (i.e. WDO.iso WinToGo.iso) i get an Error like

"No bootfile found for UEFI! Maybe the image does not support X64 UEFI."

UEFI64 Bootfile \EFI\Boot\bootx64.efi is present.

Tried the same ISOs in Easy2Boot and they worked for me.

Any ideas?

Regards

how to add Search Option to the auto loaded iso list when we have long list of iso file in hardisks....

Attached Files

Thumbnail(s)
   

头大 

I have installed Ventoy version 1.0.15 and have enabled the Secure Boot and can boot ISOs from both Legacy and UEFI correctly. I use an HP Spectre x360.

When I try to boot either Tails 4.6 on UEFI, I get nowhere (as announced in the ISO list).

But when I try to boot from Legacy, I get to the second Syslinux boot menu, and can select "Tails". Only to find an error message that mentions "no supported file system on /Live/medium" (see picture 1).

Is there something I'm doing wrong? Should the boot work as is?

Thanks for your help!

Ventoy, as marvelous as it is, has some shortcomings that its developers are addressing.

This is a work-around that I discovered that may be useful as Ventoy matures.

SuperGrub2 (SG2D) is a boot-manager in the form of a distro which does similar booting of ISOS. It is found on Distrowatch as well as is present on GIT where its developer is responsive to requests. Click the image that follows.
   

It has a GRUB2 loopback.cfg requirement of ALL the ISOs it supports, One of them is Ubuntu. Others are scattered in the LInux landscape. This year, all 2020 PUPs that are generated from the Puppy Linux WOOFCE distro builder has been generating PUPs that are compliant with booting their ISOs via SG2D, as well.

So, I've discovered a fascinating ability that works within the Ventoy framework for Secure Boot enabled. If the EFI version of SG2D is added to the ISOs for Ventoy, SG2D can be started and it will list EVERY compliant ISO contained in a BOOTISOS (or boot-isos) folder anywhere on any USB/SSD/HDD/SDcards that the PCs has and list them for user selection to boot. I have tested this workaround for all PUPs ISOs generated this year as well as Ubuntu derivatives ISOs. On my PC I have over 40 ISOs that are compliant in the HDD's "boot-isos" folder and SG2D found them as well as the one in the boot-isos folder of Ventoy. 

Its a nice addition to working with VENTOY. BUT REMEMBER, SG2D will ONLY list compliant ISOs that have a loopback.cfg for booting.

Hope this is mere helpful info for others that would benefit in running non-secure boot ISOs on a PC with Secure Boot enabled.

FYI

I have tested the following:

• Software: FATDOG
  
• ISO: Fatdog64-810.iso
  
• File size: 444MB
  
• Download: https://distro.ibiblio.org/fatdog/iso/
  
• Boot:
  - Ventoy v1.0.15 on USB 2.0 8GB stick created with options "-s" & MSDOS
  
• Platforms tested:
  - HP AIO Touch (G020,8GB RAM)
  
•       - 1st tests - UEFI Secure Boot disabled
  
•       - 2nd tests - UEFI Secure Boot enabled
  

Hello All,

Does Ventoy support Medicat.img

Thanks for a Reply.

If I fail to properly format this post, it can also be seen on Linux Mint forums:
https://forums.linuxmint.com/viewtopic.p...6&t=325131

I think I went astray following someone's mistakes on another website. I deleted that link.
Now, I am at a loss after playing with this off and on, for about 2 weeks.

Ventoy Installs and Boots fine, whether the Partition Table is msdos or GPT.
I finally found the -g option and it is now on a GPT Partition Table, Formatted as ext4.

I am at a loss after trying different things, including reinstalling a couple of times.

No Persistence option in the menu.
No Persistence in settings on re-boot.

Ventoy_File_Structure_2020-07-12


Ventoy_Partition_Format_2020-07-12: Previous


Mount Difference: Current
Code: Select all

Thank you for this great tool! Everything works fine  - except peristence.
I've got persistence for these distribution
UBUNTU 20.04
KDE neon 20200702

Using the same setup-principles persistence fails (F5-test reports SUCCESS / OK for all) for
kUBUNTU 20.04
MANJARO 2003

My question: Is there any chance to find out in advance, if a distribution should work with persistence using ventoy?
Would it be possible, to add a column "Persistence" to the ISO-list, with label (e.g. "casper-rw" OR "MX-Persist") if working or "NO" if persistence not possible?

I would like to volunteer to assist in resolving some errors seen to improve understanding of Ventoy to its readers.

Who/whom do I address them? Or have the moderator send me a PM.