[Feature Request] Create separate Legacy and Uefi Boot Menu about ventoy

[ventoy]

@soares23 @chromer030

A new feature is under testing now.
I will provide two styles of boot menu: normal list mode and directory tree mode.
By default it's list mode, and you can switch freely between the two modes by a hotkey (e.g. F3)

So, we can expect the next release!

[chromer030]

Or by pressing a function key in related boot mode ( UEFI or Legacy) , for example F2 , unsupported ISO files disengage and disappear from Menu.
I don't know if this implementation could be possible but maybe this workarounds can be usable :

• By adding a discoverable specific filename flag (UEFI/Legacy) to each ISO file name , and Ventoy separate and disappear unrelated ones based of that.

• Maintaining a reliable , always in updating phase database ( with help of users contributions ) based on file name patterns for Ventoy , so that Ventoy will know which ISO has Full/Semi or No support of UEFI or Legacy or both , and for nonexistent ISO files on database , treat them as generic like current mode on 1.7 version.

• Before showing the list Ventoy tries to test and separate UEFI/BIOS capable ISOs based on current tested results or boot attempt if there is any workaround for that , (this make boot time longer ) , or after pressing a FN key try to do that.

• User make two folder on USB , one with name of UEFI . one with name of Legacy and put related ISOs in related folder , then in the list , by pressing a FN key Ventoy separate ISO based on this folders and if press again show all ISOs. (default be on showing all ISOs)
  ( but user is not fully sure about whether UEFI or Legacy or none is supported or not )

• Ventoy makes a log on its fat32 partition and save status of booted ISOs , so in the next boot if current booted mode for an ISO is not supported , ISO will not be shown on the list again , and this workaround can be bypassed by a FN key in list. ( Problem is log is not permanent ! )

[soares23]

Or by pressing a function key in related boot mode ( UEFI or Legacy) , for example F2 , unsupported ISO files disengage and disappear from Menu.
I don't know if this implementation could be possible but maybe this workarounds can be usable :

1- By adding a discoverable specific filename flag (UEFI/Legacy) to each ISO file name , and Ventoy separate and disappear unrelated ones based of that.
2- Maintaining a reliable , always in updating phase database ( with help of users contributions ) for Ventoy , so that Ventoy will know which ISO has Full/Semi support of UEFI or Legacy or both.
3- Before showing the list Ventoy try to test and separate UEFI/BIOS capable ISOs (this make boot time longer ) , or after pressing a FN key try to do that.
4- User make two folder on USB , one with name of UEFI . one with name of Legacy and put related ISOs in related folder , then in the list , by pressing a FN key Ventoy separate ISO based on this folders and if press again show all ISOs.

I thing from the 4 options the best if is possible to make is the First an Last one because the Second if a iso is not in the database but is compatible for example Uefi not Legacy what Menu is showing.

The third option i thing how do you want test it. Maybe you can verify is a efi bootloader is in the iso but that will not guarantee that if one iso have a efi file to boot that is booting efi.

The developer must see what is for him the best way to programming that an user friendy if possible in my opinion.

But is a very good tool and hope that @ventoy will longtime support that project and thanks for all your time. I algo thanks for you @chromer030 that you test many of iso.

[chromer030]

@soares23 , thank you very much for your opinions and any effort that make this great and lovely tool better than before.
I will update my suggestions for this feature request if i find any idea.
And thank you millions for paying attention to my ISO tests.

[ventoy]

In most cases, I think the user should known whether this ISO supports UEFI mode or not.
If this filtering is done by Ventoy, it will be very easy to misjudge.

[soares23]

Yes is true but if example: I make the stick i know what is uefi or legacy but if other people use the stick also because working in a repair shop they don't know if all the iso that I but is uefi or not because they maybe not use all of that stuff. For another reason is also if you but an amount of iso that’s bigger you must scroll very to reach the right iso if is more at the bottom if you has a split of uefi and legacy all these iso's isn't showing and you must not scroll so much and i thing also is an aesthetic point in my opinion to. If is possible maybe to program that you create 2 folders how chromer030 has say maybe uefi and legacy and that ventoy was only search ISO in that Folder, subfolders of them and make then Uefi and Legacy Menu was nice because if you would have example Office iso and other Programs Iso's also on the usb drive or hard drive he's showing also that would be also an nice feature that they don't see them if possible.

[ventoy]

You can try 1.0.08 with TreeView Mode.

[soares23]

HI tanks have try it is definitely better with that. For me is ok, i can ignore the folders that i want and also create the folder tree thanks ventoy for that.

I have another questions for version 1.0.08 in the previous version a have put the parameter in grub.cfg for menuentry the --class $img_name after that i have change the icon name to the name of the iso that the icon is appear on the Menu. How can i do that with version 1.0.08 that you can tell me where i can but that and if it's no more possible that you can maybe put that option on new version that would be nice. Thanks for you great work.

[ventoy]

Yes, in 1.0.08 the menu and submenu was created in the backend.
I will add the file name or directory name as there class in the next release.

[soares23]

ok thanks it would be nice if maybe for both name and directory if possible if not than if possible ass option to specify if we would have Name or directory. THanks for the great work.

[soares23]

Hi Ventoy, i have a question have you implement in 1.0.09 the --class parameter don't see it on changelog and isn't working for now or i don't know how to activate?