At which moment shall I write a command "set check_signatures=no" in crd 18 (what is a caspersky rescue disk) in UEFI mode? Which Letter shall I press - TAB, e, c, and then, how do I boot?
Will a plugin with grub.cfg replacement work? In crd.iso we do not have a standard grub.cfg where the "linux" line is.
Could you please give me a step-by-step instructions for all of this?
I've got an idea for faster Ventoy boot up!! You could add cache, so, it just searches for iso files the first boot, and it registers their locations. On other boots, the user can wether chose to search again for iso files, or to continue with cached ones!!
It will be useful for people who have many files in the partition of iso files!! (like me..)
I am using Veracrypt on my computer and unfortunately, it only creates a .zip rescue disk instead of an .iso. The .zip contains the files meant to be on a FAT32 EFI system partition. Is there any way Ventoy can boot it, or I can convert it into an .iso?
Thanks.
P.S. regarding Veracrypt, it should create an .iso rescue disk since my computer boots in UEFI with a GPT partition disk. However for some reason it only creates a .zip rescue disk. I have asked around and no one knows why or how to force Veracrypt to generate an .iso.
I used the Menu Alias Plugin to list my ISO files.
I assumed that at boot time the entries will be displayed in the order that I had listed them in the plugin, but they are listed in the alphabetical order of the .ISO files instead.
I want all .ISO files to be listed in the order that I specify in the plugin.
WITHOUT renaming the files, how can I accomplish that?
I am confronted with an error, using this last version of Ventoy, and I had replicated the error multiple times. Always the same result, installation fails.
The previous version of Ventoy that I had used, 1.0.37, works perfect for me, however with this current version installtion leads to an unusable USB Flash Drive.
I am not able to see the USB drive listed in the file manager any longer, after attempting to install Ventoy, unless of course I re-format.
Here are the screenshots in GParted before and after install attempt, as well as the terminal command window in MX Linux 19.4, when atempting to install.
See the error message, I do not get any error at all with the previous versions of Ventoy that I had used, only with this one.
Take note that despite the message at the end of installation stating that installation was succesfull, obviously it was not so.
Here are the screenshots, when going thru the installtion process.
Hope this helps and thank you for the usefull tool that Ventoy is.
Hello everyone!
There was a problem when loading some images, this is such a black window that appears and does not allow installing Windows only in legacy.
Empirically, I determined that if you replace the install.wim file from the working image and pack it back into the downloadable iso, then everything will work. But I need exactly my install.wim. When booting from USB flash, the image works in both legacy and uefi, but in Ventoy such a window appears only in legacy and uefi works well.
I need my multiboot iso, I have been suffering for 4 days already. Ventoy is the latest version.
file not more 4gb
Help to solve the problem please.
I m using ventoy to boot from 2 TB Toshiba exHDD
I have a secondary partition of 1.7 TB
the primary (ventoy) is 130 GB
the hidden partition is 34 MB
ventoy is installed on manjaro OS as application when updated I just plug my exHDD and run (ventoygui --qt5) and press update
in the last update (1.0.61) I did the same .. rebooted my PC to check and it won't boot both leagcy and uefi
the uefi booting is showing some warring and code 12 not suitable medium or something similar
I have about 1 TB on the secondary partition so reinstalling is a difficult option
please advise
It may be convenient to immediately go to the partition with images, of exist /Ventoy/ventoy_Grub.cfg
Code:
function ventoy_ext_menu {
if [ -e $vt_plugin_path/ventoy/ventoy_grub.cfg ]; then
search -s root -f /ventoy/ventoy_grub.cfg
set ventoy_new_context=1
configfile $vt_plugin_path/ventoy/ventoy_grub.cfg
unset ventoy_new_context
else
echo "ventoy_grub.cfg NOT exist."
echo -e "\npress ENTER to exit ..."
read vtInputKey
fi
}
