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.

Wow! Ventoy has made my Linux-life so much better ... easier, faster!

The name "Ventoy" makes me wonder though ... where did it come from? Especially the "toy" part, because it is really more of a TOOL than a TOY .

I have one request for the developer(s?) ... is there a possibility that Ventoy could support .sblive (systemback) files?

Thanks AGAIN for a very COOL TOOL!!!

I've tried to create a secure login using persistence with a live ISO (I was using Mint 20) but it always allowed me to login just by clicking the place to type a password, without actually typing it.  This isn't very secure at all.  Is there a way to enable this which would work?

Or otherwise, is there a way to put a secure login on Ventoy itself, before it even boots the OS?  I don't care where the login is as long as it exists.  Thanks.

我在技嘉G41主板上安装win10系统，进入安装页面后，按enter键无法安装，无反应，是怎么回事?

Please read the whole post because I approach this from several angles:

I'm trying to figure out how to do something and I have a few related questions.  I want to be able to make a live Linux that will persist, but then I can set it to use the persistence file as read-only, so that it will still keep all the changes that I've made to that point, but not make any new ones, so I can save on wear and tear for my USB stick, and lock in the settings that I want.

First of all, when exactly does Ventoy update its persistence file - during shutdown or at any arbitrary time?  So if I yank the USB drive before shutting down then will that prevent it from writing?

But more importantly, how can I make the file read-only, so that once I have it all set up the way that I want it, I can prevent further changes, and also save on wear and tear for my USB stick?  Is there some line I can put into the .json file to just prevent it from writing anything to the drive?

I've tried disabling persistence in the .json file but that seems to ignore the file completely, thus reverting everything to defaults, but I need to be able to read and use the customizations that I've made.  And I've also tried making the persistence file itself read-only (I disabled all write capabilities for all users), but it still somehow keeps updating, without even changing the date modified information!

Alternatively, is there a way that I can take all of the data in the persistence file and just put that into the ISO itself, to update it and build a new ISO or modify the existing one, so that I can just boot from that and turn off persistence?

And if none of this stuff is possible then PLEASE consider making an update for a new .json parameter to make persistence read-only!  It should be very easy to implement - just use whatever function is for writing to the drive and make it conditional.  I even tried looking into the source code myself but there are so many files and folders that I can't figure out how to fix it, much less how to even compile it so that I can redeploy it onto a USB stick (I'm new to Linux, btw).

Is this a bug in LInux upgrade to v1.0.27?

The USB is an 8GB USB V2.0 unit with its ISOs in partititon #1 and Ventoy on partition #2. Mount command message suggest a bug???