Here is a suggestion for a Ventoy GUI for Linux ...





Download here

Extract and to run just type in the terminal:

sudo python3 ventoygui.py

Hello
After asking for help with syntax control and then for displaying options, I will ask you again for launching ubuntu

Whatever option i choose, the error message is the same.
    =>  /casper/initrd.lz not found

(Without modification the ubuntu starts well)

Do you have an idea?


http://pix.toile-libre.org/upload/origin...126257.jpg

"conf_replace_legacy": [
{ "iso": "/ISO/ubuntu-20.04.1-desktop-amd64.iso", "org": "/isolinux/txt.cfg", "new": "/Menus/txt-20.1.cfg"},
{ "iso": "/ISO/ubuntu-18.04.5-desktop-amd64.iso", "org": "/isolinux/txt.cfg", "new": "/Menus/txt-18.5.cfg"},
{ "iso": "/ISO/ubuntu-18.04.1-desktop-amd64.iso", "org": "/isolinux/txt.cfg", "new": "/Menus/txt-18.1.cfg"} ]



a@b:~$ cat /media/a/v*/M*/txt-18.5.cfg
default live

label montest
  menu label ^Essayer Ubuntu sans installation
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz nomodeset ---
 
label live
  menu label ^Try Ubuntu without installing
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash ---
label live-nomodeset
  menu label ^Try Ubuntu without installing (safe graphics)
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed initrd=/casper/initrd quiet splash nomodeset ---
label live-install
  menu label ^Install Ubuntu
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash ---
label live-install-nomodeset
  menu label ^Install Ubuntu (safe graphics)
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed only-ubiquity initrd=/casper/initrd quiet splash nomodeset ---

label secondtest
  menu label ^Probablity some thing bad in cdrom
  kernel /casper/vmlinuz
  append  file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz nomodeset ---


label memtest
  menu label Test ^memory
  kernel /install/mt86plus
label hd
  menu label ^Boot from first hard disk
  localboot 0x80

i am using ventoy latest build 1.29. 
while booting with ventoy uefi getting error "secured boot Disabled" Error before gui screen
i tried uefi with textmode its working
but on gui i am facing issue
i also tried to modify ventoy.json from partition 1
set gfxmode 1024x768 
its resolve error which occurred
may i know above 1024x768 why i am receiving secured boot disabled error 
i made from ventoy2disk with secured boot enabled tick

i deleted secure boot keys and set disable secure boot still unable to getting gui on above 1024x768 resolution
please fix bug

In addition to the two partitions (the first one for the ISO files and other things, and the second one for Ventoy), is it possible to make a third partition on the same drive, so that I can install something else that can boot, such as GParted Live, so that I can use it to clone the same drive?  I hope it can clone its own partition!

But if I do this, will it interfere with the way that Ventoy works?  I'd probably have to split the first partition into two, so that the one with Ventoy installed on it would become the third one.

Or actually, is it possible to boot GParted Live using Ventoy, so that I can just put its ISO on the drive with the others, or would that cause a problem?

Would someone explain what and how to use the "-l" feature in v1.0.29?

Thanks

Hello

For example  you write
"conf_replace": [
        {
            "iso": "/ubuntu-20.04-desktop-amd64.iso",
            "org": "/isolinux/txt.cfg",
            "new": "/ventoy/ubuntu.cfg"
        }
    ]

Are you sure it actually works like this

In my legacy test, there is a crash with the following message

Boot loader 
Live: File not found

OK

Hello


During the boot on the USB key, it is possible to press the F5 key in order to check the quality of the plugging 

This works perfectly well for the "conf_replace" plugin.

This makes it possible to verify that the names indicated correspond to files.

Would it be possible to do the same for the other two plugging "conf_replace_legacy" and "conf_replace_uefi"?

Thank you

Hello,
I use an Asus M5A97 R2.0 board with a UEFI bios. Windows 10 (installed in BIOS mode) and Manjaro 20.1.2 (installed in UEFI mode) are used as operating system. Both are installed on different SSD. No boot manager like Grub2 is used, I have to use the boot menu of the computer (F8 key after booting the computer) to select the desired operating system. That is also intended. Each hard disk is listed twice: 1x under her normal name and 1x with the prefix "UEFI".

Furthermore, I still own 3 external storage media:  an external 3.5" HDD, a docking station and a 2.5" HDD. 

Now I have two problems:

Problem one:  When I start Ventoy under Windows, I only see the 3.5" HDD and the disk in the docking station. If I install Ventoy on it, I can also boot the computer from it and everything works perfectly. But I have to select the UEFI entry for the hard disk in the boot menu, they don't start with the normal entry.
However, I would also like to install Ventoy on the 2.5" HDD. But this does not work, because the hard disk is found by Windows, but not by Ventoy.  Why is that and how can I install Ventoy on it?

Problem 2: I have installed Ventoy on Manjaro as a test and thus installed Ventoy on the 2.5" HDD. As installation command I have entered this:  "./Ventoy -i -g /dev/sdd" 
The "-g" is necessary because the 2.5" HDD is larger than 2TB and therefore MBR will not work. 
The result: When I now try to boot from this hard disk, I only get the text "GR" in the upper left corner. This is probably due to the fact that I have no choice of UEFI mode for the 2.5" HDD, i.e. the entry is simply missing. How can I install Ventoy so that the computer also recognises this disk in UEFI mode?

Hello ALL,

Win10xPE Work Very Nice With Ventoy.

For Download Win10xPE ==> http://win10se.cwcodes.net/Compressed/index.php

My Win10PE ScreenShot :



Regards

Quote:

Ventoy 1.0.28:

Recently, I received some special error reports, which finally proved to be the cause of the non-standard Ventoy environment. Especially use Ventoy in a single partition environment.
Although Ventoy displays Unofficial's label information, users will not care and will still think it is a Ventoy problem. Ventoy has been an overall design from the beginning, and has not considered integration into other bootloader or partition environments. Ventoy's verification and subsequent development of new features will not consider this non-standard usage. Therefore, I decided to prohibit the use of Ventoy in a non-standard environment and no longer accept requests for deregulation. Of course, this is just the default behavior of Ventoy. Ventoy is still 100% open source. If you want to apply Ventoy in your own environment, you can fork a branch and modify the source code implementation.