Why don't you just press 'e' when you select the menu item???
Then you will see the command, e.g.
vt_browser_dir hd1,5 0x12345678 "/ISOS"
(08-02-2023, 05:48 PM)Steve2926 Wrote: [ -> ]Why don't you just press 'e' when you select the menu item???
Then you will see the command, e.g.
vt_browser_dir hd1,5 0x12345678 "/ISOS"
thank you steve2926; I know you said yes, I want to learn how we can write this 0x12345678 expression, which we see with the e key, as a command in the configuration file. can you please help.
I would assume that you use the 'e' key - look at the number, and then write a .cfg file with that command in it.
vt_browser_dir parameter1 parameter2 parameter3
parameter2 is related to memory
(08-03-2023, 09:32 AM)Steve2926 Wrote: [ -> ]I would assume that you use the 'e' key - look at the number, and then write a .cfg file with that command in it.
Thank you master steve2926; I already have a .cfg file, I prepared it manually from the very beginning. I only had the opportunity to test it on my own computer. It works perfectly, is the 0x12345678 value I want to know fixed or is this code variable "0x%lx" when I want to use the flash memory on different computer? Or is it a fixed command?
(08-03-2023, 09:54 AM)nguyen ha thai trong Wrote: [ -> ]vt_browser_dir parameter1 parameter2 parameter3
parameter2 is related to memory
Thank you my friend nhtt for your contribution. If what I want to learn is about memory, how can I get it as a command.
I made an amateur video. grub2fm and ventoyfm two in one, also installing HKBoot_1_2017.iso with ventoy.vhd, connecting after boot.
video link:
https://disk.yandex.com.tr/i/cWzwLX-O24yJ7A
Note: Lenovo ThinkCentre E73 secureboot Enabled
Do you already know how to use vt_browser_dir?
Note, parameter2 depends on your computer's memory and parameter2 is not exactly equal to ${vt_systemd_menu_mem_addr}
(08-03-2023, 04:35 PM)nguyen ha thai trong Wrote: [ -> ]Do you already know how to use vt_browser_dir?
Yes
(08-03-2023, 06:15 PM)nguyen ha thai trong Wrote: [ -> ]Note, parameter2 depends on your computer's memory and parameter2 is not exactly equal to ${vt_systemd_menu_mem_addr}
ok, if parameter2 is related to computer's memory, why ventoy has different value in normal mode and ventoy.vhd gives different value.