I have tried to boot some .img files with ventoy newest version 1.0.22
I can´t get any img files working.
Is there a specification wich img formats are working, or is this funktion still broken ?
Hello!
I've faced a problem booting windows 10 ISO. After selecting appropriate menu entry i see black screen with underscore and after couple of seconds it gets me back to previous menu.
As far as I can see, last entries on logs are "no mapping". It tries couple of times and exit.
bonus question: is there a built-in option in ventoy for logging rather than editing boot entries manually?
Any help would be much appreciated.
Hi!
I have a suggestion: in general, ventoy folder on first partition is mostly for a theme customizations and usually not used daily. How about making it hidden out-of a box? Those who need customizations may read manual and find that folder and those sho don't need it, ...well they dont need it anyways.
---
For those who wish to hide it without damaging its functionality (at first i thought renaming it to .ventoy - that will not work)
Linux users
cd /your_flash_root_folder (e.g. /media/admin/ventoy)
echo ventoy > ./.hidden
Windows users
Just mark ventoy (and .hidden file if you did previous step) folder hidden in its properties.
That's it. That will prevent ventoy folder to be accidently tampered while using flash drive
On an Intel NUC, I can use Ventoy in BIOS mode to boot the Arch Linux installation ISO.
If, on the same Intel NUC, I use Ventoy and EFI mode, the boot will fail.
The failure messages is:
Waiting 30 seconds for device /dev/disk/by-label/ARCH_202010 ...
ERROR: '/dev/disk/by-label/ARCH_202010' device did not show up after 30 seconds.
I then get an emergency shell, and I can see the following devices in /dev/disk/by-label: Recovery and VTOYEFI
Recovery is probably Windows 10 on another disk.
If, instead, I boot via BIOS, the following disks exist in /dev/disk/by-label:
ARCH_202010, Recovery, and VTOYEFI. ARCH_202010 is a symlink to /dev/dm-0.
Attached are screenshots of (1) the EFI error message, and (2) ls -l /dev/disk/by-label after a successful BIOS boot.
Further, the Ventoy product does NOT maintain "options" parity across; as, there is no "config" file saved from one release on its disk (sda2) for the next upgrade to use.
Here is a screen shot of my ventoy directory on a usb memory stick:
And here is a screen shot of the ventoy.json file:
All of the .dat files were generated by CreatePersistentImg.sh and then copied to the ventoy directory and the names change as you see them. When booting from the usb memory stick, all of the ventoy menus look and function as they should. The Kbuntu iso starts and runs as expected and configuration changes are stored and remembered at the next startup, as expected.
The Ubuntu iso will not start up using the persistence file. It will start and run without persistence. All of the others start up and run with their persistence files, but no configuration changes are remembered on the next boot.
What am I doing wrong?
