Hello all.  I'm a new Ventoy user.  What a wonderful tool.

I'm wondering if there's a way to change the virtual/emulated CD-ROM device's USB VID/PID (vendor ID and product ID).  Perhaps via the config or plugin mechanism?

There are some systems, such as Synology NAS installers, that only work with certain the USB VID/PID values.  I imagine there are many uses for this.

I searched in the forums and on Google unsuccessfully so thought posting here was the correct next step.

first of all a lot of thanks to Longpanda for his masterpiece Ventoy ( the best universal usb and hd booting method)
maybe someone can help me:
i was use ventoy to boot directly the file libreelec .img that i found into gz archive

this worked perfectly in efi and in legacy bios using 8.x and 9.x versions ( boots perfectly in every mode , live or run always perfectly) , from 10.x versions no way to boot , always a list of errors.
these new versions boot and works perfectly from usb created from libreelec sd creator but no way to boot from ventoy usb.
someone can help me?

(i have read:
https://github.com/LibreELEC/LibreELEC.tv/issues/5905
)
maybe something is changed in kernel in evolution from versions 8.x 9.x to version 10.x?
im not a pro linux user so im not able to insert module in kernel.....
 in every case thankyou very much

Attached Files

Thumbnail(s)
   

how to remove version number in lower left side? i wanted a plain design only. thanks

When booting safely, in UEFI systems, Ventoy asks to confirm the MOK key and after confirmation, the Boot Menu starts successfully when reloading. 
My question is, how does this happen? 
Ventoy saves data about the computer from which the Ventoy flash drive has already been downloaded in the boot area? 
If so, is it possible to copy this data to another Ventoy flash drive? 
( I use an online translator )

Hi there,

So I made a ventoy usb, with a couple of ISO, I tried this out on a VM and it seemed to work fine. But when I try on on my physical pc it is just glitched. Look at the top of the screen, this happens after I selected in boot menu the ventoy drive. I dont know how to fix. My specs are: MoBo: MSI Z690-P, i7 12700k, 32GB RAM, MSI RTX 3080TI.

We look forward to your contributions (members) to maintain and develop ventoy more and more.

I followed the instructions for adding a virtualbox machine as vtoy. This is amazing. It does not work in UEFi either but it works splendidly on legacy. I have to wonder if there is a need for linux systems with persistence anymore. I guess if you are cramped for space.

Any thoughts?

Hi, 

Just wondering if anyone has tried using Ventoy to boot the iPXE image? It supports a large range of image options but so far, I haven't had much luck with EFI or USB images to boot without failing and looping back to Ventoy, I'm only speculating but I'm guessing that it could be due to requiring access to the hardware at a lower level when Ventoy is operating out of that already?  

Ideally, I'd prefer to stay in the UFI space without having to manually reconfigure bios etc. 

I've gotten the ISO to boot previously but manually adding the script into the ISO means it isn't dynamic anymore and would need a hard coded script to chainload etc. 

Index of / (ipxe.org)

https://ipxe.org/

Anyway thanks!

i tried updated version 1.0.81, version 1.0.80, version 1.0.79, it break the UEFI detection in boot menu to select boot from UEFI for ventoy drive selection, unable to detect ventoy drive in UEFI mode. in BIOS i already set to UEFI and Legacy, or UEFI only in CSM option, both also unable to detect Ventoy in UEFI selection. Currently falled back to Ventoy version 1.0.45, no issue to boot into UEFI selection in that 2 mode in CSM option. 

I am wondering why the boot process reacted differently in between version 1.0.45 with the recent Ventoy versions.

how to compile ventoy to run on one partition and ventoy and iso