@page { size: 21cm 29.7cm; margin: 2cm } p { margin-bottom: 0.25cm; line-height: 115%; background: transparent }
Hello Everyone!
I apologize for my poor knowledge of English, my text would probably be a little more clearer in Hungarian.
I have long wanted to create a tool that can act as a storage medium and boot many iso installers, and it also has an installed Linux system. So there is no need to use installer iso + persistence. In addition, the installed linux system can be updated. I think with the help of ventoy-1.0.15 this is almost entirely feasible.

I did the following.
I have a Sony 111 gigabit USB SSD.
I installed the new version with the instruction "sudo sh Ventoy2Disk.sh -i -r 32768 -g / dev / sdb". I then made a copy of the EFI partition VTOYEFI / EFI / BOOT / BOOTX64.EFI file.
Then I formatted the dev / sdb3 reserved partition into an ext4 partition using Gparted.

Now I have installed a linux system in UEFI mode using linuxmint-20-xfce-64bit.iso. Dev / sdb3 was mounted as / and dev / sdb2 was mounted as / boot / efi. The installer has repeatedly warned that this will not be good! In the meantime, I had to remove the boot, efi flag from the original efi partition on my computer to proceed with the installation. He finally succeeded and did it. Now Legacyy mode can be used to boot ventoy and UEFI mode to boot installed linux as a system. Because of this, I deleted the contents of the VTOYEFI / EFI / BOOT / folder and rewrote the previously saved ventoy BOOTX64.EFI file into it.

In the end, ventoy can be booted in Legacy mode, and installed Linux can be booted in UEFI mode (because it can boot from the EFI / ubuntu folder). By selecting “boot from efi file” from the “BIOS”, starting the VTOYEFI / EFI / BOOT / BOOTX64.EFI file, the ventoy starts in UEFI mode.

So far, I'm very happy about that.

I even copy the i386-pc folder from the usr / lib / grub folder to the boot / grub folder on the installed system with its contents. If I boot this system with a grub from another Legacy linux system, I will plug in a small flash drive and install the grub in the auxiliary flash drive (for example sudo grub-install dev / sdX), then update-grub or grub-mkconfig -o and the system Legacy mode can then be booted using the auxiliary flash drive.

I know it was pretty DIY like that, but maybe I gave you a tiny idea for the “how to proceed” aspect.

Thank you for your patience! … Best Regards … CsI

I tested live linux Mageia-8-alpha1-Live-Plasma-x86_64 with ventoy-1.0.15.
ISO: Mageia-8-alpha1-Live-Plasma-x86_64.iso
Download: download
Download Classic installator and Net CD installation: download
Boot:
- Legacy
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

I tested live SparkyLinux 5 „Nibiru” Xfce (based on Debian 10 „Buster”) with ventoy-1.0.15.
ISO: sparkylinux-5.12-x86_64-xfce.iso
Download: download
Other version SparkyLinux: download
Boot:
- Legacy
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

I tested live Linux Neptune 6.5 „Jet” Plasma5-20200707 with ventoy-10/15.
ISO:  Neptune65-Plasma5-20200707.iso
Download: download
Boot:
- Legacy
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

It would be very nice if the general forum language was English.

Hello,

I noticed a problem with the live cd ISO of the Haiku operating system.

Official site:

https://www.haiku-os.org/about/


Haiku 32bits :


https://s3.wasabisys.com/haiku-release/r...nyboot.zip


Haiku 64 bits :


https://s3.wasabisys.com/haiku-release/r...nyboot.zip


It refuses to boot on my DELL D630 and also on a virtual machine ( i have only tested in Legacy mode because I do not currently have UEFI).


Thank you for your attention.

First of all, Ventoy is awesome! 

Congratulations for the project and a big THANK YOU for publishing it for free under GPL license.

Suggestions:

1. The option to reserve a space for additional partitions could be more proeminent in the installer. As per my understanding, reserving a space in a form the 1st partition stays under 137 GB prevents that legacy BIOS access range limitation problem (what is not mentioned in that documentation page). Maybe instead an "Option" menu, all the settings could be visible in the main area of the app, bellow the boxes that show package/device Ventoy version.

2. It would be great if the files we have to put under ventoy directory in 1st partition (like ventoy.json and ventoy_wimboot.img) could be located under ventoy (or other) directory in 2nd partition instead. This way the 1st partition would be totally free of Ventoy data (allowing easier formatting to a different filesystem with no need to back up and restore the ventoy directory). Big plus if scripts and persistence files could also be located in 2nd partition (the installer could offer an option to select desired size of 2nd partition to easier accomodate the persistence files or we could manually resize 2nd partition after install).

3. I was unable to center align the hotkey tips hbox and memdisk hbox in grub theme. I was able to achieve the result I wanted using regular labels instead:

在系统的ESP分区复制了refind文件夹，安装了refind启动系统，插上Ventoy优盘，通过rEFInd的自动查找找到了可启动的Ventoy优盘，通过refind启动界面进入Ventoy优盘启动界面，再启动微PE（x64版）时，微PE无法启动，会回到Ventoy优盘启动界面。而通过bios直接启动Ventoy优盘时，微PE就可以启动。在1.0.14和1.0.15版都是如此，1.0.15版的gpt分区模式和mbr分区模式也都是如此。refind版本为最新的0.12.0版，refind文件夹为其解压所得。
如何才能通过refind启动界面进入Ventoy优盘启动界面后，启动微PE？
望各位帮忙！多谢！

ShadowProtect Recovery Environment is WinPE based.  However when I select it I get the press any key to boot message but despite pressing a key the prompt remains there and eventually times out and returns to the Ventoy menu.  In my ventoy.json file I specify CLI and the initial menu is CLI however after a period of time I'm returned to the Ventoy menu in GUI mode.  Why would a WinPE based bootable ISO fail to boot and why am I returned to a GUI Ventoy menu?

By the way, despite my posts, this is an excellent software - very well designed.

I have in Ventoy partition created a subfolder "ventoy" and in it "ventoy.json".  In this file I have:

{
    "theme": {
        "display_mode": "CLI"
    }
}
{
    "control": [
         { "VTOY_DEFAULT_SEARCH_ROOT": "/BootableISOs" }
    ]
}


I got the CLI working.  My UFD has a lot of .EFI files but they are not in the BootableISOs folder so they should not appear in the menu - only ISO/EFI files in the ufdI\BootableISOs should appear correct?

V1.0.15.