(02-02-2022, 08:40 PM)AlexBryansk Wrote: google translate:
In the video,https://disk.yandex.ru/i/4y6jChViAZXNvA , ventoy is installed on an external SSD disk with a capacity of 256GB. 8 themes are used:
- main menu,
- external menu(launching ventoy_grub.cfg),
- file manager (the idea and the main part of the code is nguyen ha thai trong, the author of the topics on the forum "grubfm_ventoyfm iso" and "ventoyfm1062")
- directory antivirus "/ISO/Antivirus"
- directory Windows Installation disks "/ISO/Install windows"
- directory linux Live-cd "/ISO/linux"
- directory the loaders "/ISO/multiboot"
- directory working with HDD,ssd,flash disks "/ISO/sistem utilit"

The difference from the original ventoy is only in adding code to the grub.conf file.
Native auto-search for files in { "VTOY_DEFAULT_SEARCH_ROOT": "/ventoymenu" }, but this folder is empty and therefore will not be displayed in the main menu.
The second Auto-search is carried out by the built-in file manager. Launching iso, img files... carried out by ventoy. Launching text files
with the cat command. In the file manager mode, not all iso, img files are launched from partitions other than hd0,1.
But these files are not launched from these places by other programs - a1ive/grub2-filemanager and nguyentumine/AIO-Boot.

Disadvantage and a big request to help:
Icons, aliases, themes... added manually:
for example, I have

Code:

if   regexp '^\b.*[kK][rR][dD].*$' "${name_icon}"; then
        set icon="Kaspersky";
    elif regexp '^\b.*[dD][rR][wW][eE][bB].*$' "${name_icon}"; then
        set icon="drweb";
    elif regexp '^\b.*[eE][sS][eE][tT].*$' "${name_icon}"; then
        set icon="eset";
    elif regexp '^\b.*[aA][vV][iI][rR][aA].*$' "${name_icon}"; then
        set icon="avira";
        ....

in the ventoy.json file

Code:

    "menu_class": [
            {
                "key": "krd",
                "class": "Kaspersky"
            },
            {
                "key": "drweb",
                "class": "drweb"
            },
            {
                "key": "eset",
                "class": "eset"
            },
            {
                "key": "avira",
                "class": "avira"
            },
            ....

1. Therefore, the request is how to extract data from the ventoy.json file from the terminal (in the grub.conf file).
Maybe longpanda has some kind of function.
2. Or how to run a binary file. The analog in the linux terminal is ./path/file_name
3. How to transfer data from the grub.conf file to the label component file theme.txt .
An analogue of "menu_tip" in the file ventoy.json or +label {text = "@VTOY_HOTKEY_TIP@"... in the file theme.txt .

For example, launching Kaspersky Rescue Disk antivirus
(press "Ctrl+r" - "GRUB2 Mode" will be displayed at the bottom, in the center of the screen and ... that's it then start.)

(02-03-2022, 06:39 AM)nguyen ha thai trong Wrote:

(02-02-2022, 08:40 PM)AlexBryansk Wrote: For example, launching Kaspersky Rescue Disk antivirus
(press "Ctrl+r" - "GRUB2 Mode" will be displayed at the bottom, in the center of the screen and ... that's it then start.)

ventoyfm of the future created by serhat100
https://www.tnctr.com/topic/1104765-altay-grub2fm-ventoyfm-g4d_g4e-1064/
video clip
https://disk.yandex.com.tr/i/JOMCDMRPePAbGg

(02-04-2022, 06:26 AM)AlexBryansk Wrote: Thanks for the reply.
I didn't set the task to run some file. This is handled by Venntoy. Therefore, I do not create menuentry manually.
I set the task to change the appearance. Namely, each catalog has its own theme.

(02-03-2022, 07:19 AM)serhat100 Wrote:

(02-03-2022, 06:39 AM)nguyen ha thai trong Wrote:

(02-02-2022, 08:40 PM)AlexBryansk Wrote: For example, launching Kaspersky Rescue Disk antivirus
(press "Ctrl+r" - "GRUB2 Mode" will be displayed at the bottom, in the center of the screen and ... that's it then start.)

ventoyfm of the future created by serhat100
https://www.tnctr.com/topic/1104765-altay-grub2fm-ventoyfm-g4d_g4e-1064/
video clip
https://disk.yandex.com.tr/i/JOMCDMRPePAbGg

Kaspersky Rescue Disk antivirus

The krd.iso file should be in the root of any partition of the hdd and also the data name should be created in a folder with krd.iso in it. 

krd.iso.cfg

set timeout=0
menuentry "${chosen_path}" --class=kapersky {
set iso_path="${vtoy_iso_part}/${chosen_path}"
set lang="en"
if cpuid -l; then set _kernel="k-x86_64"; else set _kernel_="k-x86"; fi
loopback loop $iso_path
linux (loop)/boot/grub/${_kernel} net.ifnames=0 lang=${lang} dostartx trace isoloop=krd.iso
initrd (loop)/boot/grub/initrd.xz
}

(02-04-2022, 07:32 PM)Steve2926 Wrote: Try using linux16 and initrd16 commands instead?