/grub/grub.cfg

Hello,

I tried the .29 version of Ventoy 3 days ago and after booting on linux from ventoy, when I returned to Windows, the usb key was detected as readonly.
To make it readable again I had to go to "Properties/Tools/Check now" (on Windows 7 at least) with admin rights.

I've tried 4 or 5 times on different linux bootable images and it happened every time.

I don't recall every seeing this issue with the previous ventoy versions (the last I tried was the .20).

As for the key creation options I did nothing fancy, just checked "Secure boot support" and chose "MBR" partition table.

Have fun debugging that!
Loceka.

请问一下是否可以在下个版本中，将“debug.cfg”文件中Ventoy UEFI Utilities子菜单能否加入分类，便于菜单显示图标？谢谢。

测试可以手动添加并且功能正常不影响启动。

In the next version, will the“ debug.cfg ”Can classification be added to the ventory UEFI utilities submenu in the file to facilitate menu display icons? thank you. 
The test can be added manually and the function is normal without affecting the startup.


submenu 'Ventoy UEFI Utilities' --class=debug_util {
        menuentry 'Fixup Windows BlinitializeLibrary Failure' --class=debug_util {
            chainloader ${vtoy_path}/vtoyutil_x64.efi env_param=${env_param} ${vtdebug_flag} feature=fix_windows_mmap
            boot
            echo -e "\npress ENTER to exit ..."
            read vtInputKey
        }

        menuentry 'Return to previous menu [Esc]' --class=vtoyret VTOY_RET {
            echo 'Return ...'
        }

I have two computers, a laptop and a desktop, and Ventoy doesn't work quite right with either one of them. The Ventoy menu freezes up on my desktop, and I can't get it to boot at all on my laptop (even when I configure the BIOS correctly).

I recorded some videos so you can see the problems in action:

https://youtu.be/XnsAx9TSnDA
https://youtu.be/ddsCWPqVqgI

Thanks for your time.

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