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:
Code:
+ label {
top = 92%
left = 25%
width = 50%
align = "center"
text = "@VTOY_MEM_DISK@"
color = "white"
}
+ label {
top = 95%
left = 25%
width = 50%
align = "center"
text = "@VTOY_HOTKEY_TIP@"
color = "white"
}
It would be cool if ventoy_width and ventoy_align were available options in ventoy.json and it were displayed as a regular label (in case it is not yet) so center align would work.
4. I have been playing with Chrome OS (Brunch Framework, to be more precise) and one of their install options is to create a disk image (.img) in a ext4 or ntfs partition and boot from it by adding to grub an entry like this:
I have added it to the grub install I already have on another disk and it worked fine but it would be cool if Ventoy allowed custom entries like this to be added to it's own grub manually, so we could boot Chrome OS (and other images similarly) with no need to have grub in another disk.
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 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?
Any way to automatically/manually Randomly change the Background Image while booting every time or each time visiting the directories while in Tree View.
Like, if I enter ISO directory then the Background image will shuffle/change and so as with WIM directory...
Running Linux Mint19.3-MATE. Ventoy(finally) installed, and on the 16GB flash drive I have the iso's for antiX32b, BionicPup32b, and BionicPup64b. AntiX and BionicPup64, boot, and run, no problems. My trouble is BinicPup32 will not boot. I have made 3 different downloads of it, and placed each, 1 at a time, onto the drive,in the proper partition(with the 2 working iso's), and it just won't run.
(Sorry-I have the debug directory, but it doesn't allow me to attach the files.)
Please use this link to view the debug directory: https://drive.google.com/drive/folders/1...sp=sharing
I have an idea to improve the Auto Installation plugin for Windows to include the possibility to copy $OEM$ folders to the iso when it is in use (like an autounattended.xml), with the possibility to propose multiple $OEM$ folders for ISOs (like the xml way in the json).
That way, this opens the possibility to include parameters, apps, etc to an unattended installation with a completly untouched Windows ISO.
