I installed Ventoy to my 256gb usb stick.
Now for some reason, when I tried to update my usb stick with latest Ventoy version, Ventoy2Disk doesn't see that Ventoy 
is already installed and doesn't offer to update. I only have option for a new install.

All I did was convert exFat to NTFS and used 2048kb cluster as per FAQ. I also placed ventoy.disk.img.xz to Ventoy dir on primary partition.

Any ideas?

i am so satisfacted.my english is poor, sorry . thx for approving my user greetings wally

不得不说，ventoy这个工具太牛了，但是我把ushendu的UEFI版生成的ISO放在ventoy分区，发现不支持EFI引导模式，请问大神这个问题有办法解决吗？

Hello
Since I'm using Ventoy, I miss an UI for Linux. In fact, before Ventoy existed, I used MultiJBootUSB, that have UI for Linux. However, I continue using MultiBootUSB cause it has a great interface to launch ISO's and USB's distros using QEMU. I don't know if Ventoy Windows version has that possibility, but it would great in a Linux UI.
MultiBootUSB is outdated since 2018-04-04 and its domain is for sell. I don't know if both projects are using same language, but I suggest to fork the MultiBootUSB interface and reuse its UI to give Linux users a way to simplify the use of Ventoy, adding the QEMU launch possibiity.
Thank you

My day job is BIOS engineer working in UEFI and have just started using Ventoy as my main usb stick for personal use.

I've been thinking about using Ventoy in my Day job...

Is the source for Ventoy available somewhere?

Specifically; I'd like to be able to run Ventoy from the UEFI shell and pass it a --text parameter on the commandline. This should cause Ventoy to run as a EFI application and print a list of selections (ISOs) in table form to the console.

Think of this as a crude text launcher for ISOs. 

I'd use this in place of the graphical gui since most of my work is done remotely over a usb serial port in the shell. These systems are "headless" and don't have a usb keyboard/mouse/monitor attached. All work is done on these systems via the serial port (TeraTerm).

Could Ventoy.json be used to force Text mode?

Found on Distrowatch, here. 

And, Forum discussion here.

Thanks in advance

Hello,
Tried to compile Ventoy 1.32 from source.
Grub Core.img is coming out at 0kb.
I am getting this error when compiling Grub separately.
Compiles fine on 1.31 source.  Compiled using Longpanda's guide on Github.
Likely an error on my part as I am new to compiling.

ventoy/ventoy.c:49:19: fatal error: miniz.h: No such file or directory
#include "miniz.h"
                  ^
compilation terminated.
make[3]: *** [ventoy/ventoy_module-ventoy.o] Error 1
make[3]: Leaving directory `/home/Ventoy-master/GRUB2/SRC/grub-2.04/grub-core'
make[2]: *** [install] Error 2
make[2]: Leaving directory `/home/Ventoy-master/GRUB2/SRC/grub-2.04/grub-core'
make[1]: *** [install-recursive] Error 1
make[1]: Leaving directory `/home/Ventoy-master/GRUB2/SRC/grub-2.04'
make: *** [install] Error 2
grub-mkimage: error: cannot open `/home/Ventoy-master/GRUB2/SRC/grub-2.04/../../../GRUB2/INSTALL/lib/grub/i386-efi/moddep.lst': No such file or directory.
grub-mknetdir: error: cannot open `/home/Ventoy-master/GRUB2/INSTALL/lib/grub/i386-efi/moddep.lst': No such file or directory.

I am able to get Mint 20, CAINE 11, Systemrescue 4.9.2 and Foxclone 42 to boot in UEFI mode but HBCD_PE_x64 and tails-amd64-4.14 will only boot in Legacy Bios mode. Is there a way of getting them to work in UEFI as on other threads people have reported they do work in UEFI

经过多台计算机测试，操作系统分别是Windows10 2004 专业工作站版和专业版，ext2fsd会导致ventoy无法识别到U盘，需要手动关闭

Hi. I have seen that the iso of wifislax64 2.1 is compatible with ventoy. However when starting the iso it does not work for me. Attached image of the error that gives me. I don't know if I have to do some kind of thing. Can you help me? Thank you

Attached Files

Thumbnail(s)