Hello.
Venty allows booting as standard and also with the "persistent" option.

However, it is often necessary to add other options. I have not found an explanation on how to do it.
Perhaps I have searched the documentation poorly.
But I fear that this is a very regretful oversight.

Remember by making an installation medium with only the dd command, it is possible to press the e key and introduce a lot of options often necessary to successfully boot.
See https://wiki.ubuntu.com/Kernel/KernelBootParameters
A list of some  useful parameters https://doc.ubuntu-fr.org/kernel#exemple...oyau_linux

Hello longpanda   , how are you
my language is Arabic , But , I will try to communicate the idea

boot ventoy in hdd and sdd , like the photo


I used a program BOOTICEx64 , Then I copied the files And the iso , He did not work with me

I worked to save a backup MBR And PBR IN USB , Then Restore MBR And PBR  worked in sdd 

boot grldr and menu.lst  I need extracted file systems , This boot is my basic , And I want to combine it with boot ventoy



I liked the program so much



Thank you


thamer mousa

Attached Files

Thumbnail(s)
   

  menu.zip (Size: 11.35 KB / Downloads: 2)

I'd like to add that the "zen_installer-2020.05.27-x86_64.iso" works perfectly using Ventoy V13.

clear-33300-live-desktop.iso will boot to clearlinux boot menu, but after removing "quiet" everything appears OK or normal but just hangs. Using Ventoy version 13.

Is there any chance of getting a Ventoy version for Linux with a GUI like you have for Windows? Thanks

Just downloaded the latest Fedora KDE (Fedora-KDE-Live-x86_64-32-1.6.iso) and dropped a copy on my Ventoy 1.12 key and when I tried to boot Fedora from within Ventoy I got error messages. Thinking it might just be the Fedora ISO I created a live key of it using Etcher and rebooted and booted in to the Fedora live environment without issue. Is this a know problem, and if so is there a fix for it? Thanks

https://github.com/ventoy/Ventoy/issues/243

Just prepping a thread.  With the newer 1.0.13, I'll be testing the following images.  Test hardware will be a Dell Latitude 3500 (shouldn't matter, but 8265u/16GB/1TB NVMe/GB Eth/Wifi 5 (9260AC))with no legacy compatibility turned on (full UEFI). I realize some are duplicates that have already been tested, but I just copied all my current iso's over to the USB...

anarchy-1.2.1-x86_64.iso
STILL WORKING

debian-10.4.0-amd64-netinst.iso
STILL WORKING

endeavouros-2020.05.08-x86_64.iso
WORKING

Fedora-Workstation-Live-x86_64-32-1.6.iso
WORKING

FuryBSD-12.1-KDE-2020042001.iso


GhostBSD-20.04.1.iso


gparted-live-1.0.0-2-amd64.iso
WORKING

Mageia-7.1-Live-Plasma-x86_64.iso
Hangs at Mageia splash screen, cannot get to console to see where it hung

OpenMandrivaLx.4.1-2020.05-plasma.x86_64.iso
WORKING

q4os-3.11-x64-tde.r1.iso


ROSA.FRESH.PLASMA5.R11.x86_64.uefi.iso


sparkylinux-5.11-x86_64-lxqt.iso


void-live-x86_64-20191109.iso

When running UEFI boot on a 2011 iMac the boot into the ventoy menu works fine, but when an ISO is selected the screen goes black and does not respond.  I have tried secure boot mode with the error secure boot platform not found (error 14) when selecting an ISO.  I check-summed the ISO's, so I believe the only issue has to do with either the Mac boot configuration or the fact that rEFInd is installed on my computer, although I bypassed it when booting ventoy for no new results.  Is mac usage known to be a problem? Many threads and the github issues show complaints about iMac issues?  Anyway, if you know of a way to fix issues booting using 2011 iMac please do tell.

Hi

First of all, thank you for this awesome tool. I've been looking for something like this for ages. (I've been a long time user of the Zalman 2.5" case that allowed something similar to Ventoy, but in hardware.)

Now my feature request:

The ability to put the ISO files anywhere in the USB drive is a great usabiilty feature. I would like it to be possible for the ventoy.json file to have this feature too, so I could put it along with my ISO files in my ISO folder and keep the rest of the drive clean. Since the ventoy folder's existence seems to be there just to hold the ventoy.json file, why not allow that particular file to reside anywhere in the drive instead of a rigid placement inside a ventoy folder at the root folder of the drive? If the ventoy folder is expected to hold more things in the future, just allow the folder to be placed anywhere instead of just the root folder.

Congratulations for what you have achieved already and keep the good work!