vboot for ventoy

[nguyenhathaitrong]

vboot command line in ventoy how, i have try probe -s dev_uuid -u $ vtoy_iso_part insmod $ prefix / i386-pc / vboot.mod loopback vboot1 $ prefix / i386-pc / vbootldr.cpio set vbootloader = (vboot1) / vboot vbootinsmod (vboot1) /vbootcore.mod vboot harddisk = (UUID = $ {dev_uuid}) $ vt_chosen_path boot return 0 but vboot error 12

https://user-images.githubusercontent.com/71330863/103194421-34435900-4912-11eb-82e9-a48eca17d7f5.mp4

[a1ive]

probe -s dev_uuid -u $ vtoy_iso_part insmod $ prefix / i386-pc / vboot.mod loopback vboot1 $ prefix / i386-pc / vbootldr.cpio set vbootloader = (vboot1) / vboot vbootinsmod (vboot1) /vbootcore.mod vboot harddisk = (UUID = $ {dev_uuid}) $ vt_chosen_path boot

too many spaces. grub2 does not support loading modules across versions. Also, as far as I know, vboot should not support exfat. vmlite has stopped maintaining vboot for many years now, let it rest in peace.

[nguyenhathaitrong]

but grubfm 7.2 use vboot boot ventoy.vhd ok

On Mon, Dec 28, 2020 at 6:31 PM A1ive notifications@github.com wrote:

probe -s dev_uuid -u $ vtoy_iso_part insmod $ prefix / i386-pc / vboot.mod loopback vboot1 $ prefix / i386-pc / vbootldr.cpio set vbootloader = (vboot1) / vboot vbootinsmod (vboot1) /vbootcore.mod vboot harddisk = (UUID = $ {dev_uuid}) $ vt_chosen_path boot

too many spaces. grub2 does not support loading modules across versions. Also, as far as I know, vboot should not support exfat. vmlite has stopped maintaining vboot for many years now, let it rest in peace.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-751682036, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYLYTYBYXEIF2M53FU4DSXBUBDANCNFSM4VLTNA2A .

[nguyenhathaitrong]

If you use the map of grub.exe to boot ventoy.vhd or ventoy.img, there will be an error message

On Mon, Dec 28, 2020 at 7:32 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

but grubfm 7.2 use vboot boot ventoy.vhd ok

On Mon, Dec 28, 2020 at 6:31 PM A1ive notifications@github.com wrote:

probe -s dev_uuid -u $ vtoy_iso_part insmod $ prefix / i386-pc / vboot.mod loopback vboot1 $ prefix / i386-pc / vbootldr.cpio set vbootloader = (vboot1) / vboot vbootinsmod (vboot1) /vbootcore.mod vboot harddisk = (UUID = $ {dev_uuid}) $ vt_chosen_path boot

too many spaces. grub2 does not support loading modules across versions. Also, as far as I know, vboot should not support exfat. vmlite has stopped maintaining vboot for many years now, let it rest in peace.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-751682036, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYLYTYBYXEIF2M53FU4DSXBUBDANCNFSM4VLTNA2A .

[a1ive]

what is ventoy.img or ventoy.vhd? what error message? the commands you wrote only works in ventoy's grub!

[nguyenhathaitrong]

https://user-images.githubusercontent.com/71330863/103219067-4b546c00-494f-11eb-92d1-ad55b2735096.mp4

[a1ive]

1. Installing ventoy on a virtual drive is not useful at all.
2. You loaded vboot twice, which may cause memory conflicts.
3. You are using an old version of grubfm. vhd boot script has been changed long ago.

[nguyenhathaitrong]

sent to you my ventoy mod https://drive.google.com/file/d/1GUWuh-V9ypKCACyTAkkDD_rmDq4Sg3M_/view?usp=sharing

On Mon, Dec 28, 2020 at 9:56 PM A1ive notifications@github.com wrote:

1. Installing ventoy on a virtual drive is not useful at all.
2. You loaded vboot twice, which may cause memory conflicts.
3. You are using an old version of grubfm. vhd boot script has been changed long ago.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-751738411, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL3J75XGOWX4DJXAQMDSXCMDNANCNFSM4VLTNA2A .

[nguyenhathaitrong]

you help me buid core.img and bootia32.efi, bootx64.efi of ventoy version 1.0.31. Thank you

[a1ive]

why not download it from https://github.com/ventoy/Ventoy/releases

[nguyenhathaitrong]

I need ventoy version 1.031unlock, because using the standard version still works fine but has too much notice. I send back the ventoymod fixed error superVentoy.vhd https://drive.google.com/file/d/125cRxOfyYGeDZBWlEhm-uL8KlAFqtx46/view?usp=drive_web

On Thu, Dec 31, 2020 at 11:42 AM A1ive notifications@github.com wrote:

why not download it from https://github.com/ventoy/Ventoy/releases

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-752841361, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL5YXTPDY5NIXQFQS7DSXP6KVANCNFSM4VLTNA2A .

[a1ive]

I respect the decision of the author of ventoy, and I have no intention of creating a fork of ventoy.

[nguyenhathaitrong]

thank you very much. Everything I do just pushes you to have more fans' support and love https://youtu.be/xAUDb2OkigI

On Thu, Dec 31, 2020 at 12:40 PM A1ive notifications@github.com wrote:

I respect the decision of the author of ventoy, and I have no intention of creating a fork of ventoy.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-752851480, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYLYO3TGF5D6WXIHZ5Y3SXQFDJANCNFSM4VLTNA2A .

[nguyenhathaitrong]

ventoy load iso with memdisk and mount iso, unlike grubfm and aioboot use map or wimboot. Do you know how to load iso and mount iso using memdisk or map of grub4dos?

On Thu, Dec 31, 2020 at 1:39 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

thank you very much. Everything I do just pushes you to have more fans' support and love https://youtu.be/xAUDb2OkigI

On Thu, Dec 31, 2020 at 12:40 PM A1ive notifications@github.com wrote:

I respect the decision of the author of ventoy, and I have no intention of creating a fork of ventoy.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-752851480, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYLYO3TGF5D6WXIHZ5Y3SXQFDJANCNFSM4VLTNA2A .

[a1ive]

ventoy load iso with memdisk and mount iso

No, ventoy only uses memdisk in F1 "Memdisk Mode", otherwise it uses modified ipxe.

unlike grubfm and aioboot use map or wimboot

wimboot cannot mount iso.

Do you know how to load iso and mount iso using memdisk

See syslinux wiki.

unlike grubfm and aioboot use map Do you know how to load iso and mount iso using ... map of grub4dos?

Don't you think these two statements contradict each other?

[nguyenhathaitrong]

I use ventoy boot iso image always see the ventoy mount iso file, if I use the map of grub4dos, it only boots the iso image

On Mon, Jan 4, 2021 at 1:14 PM A1ive notifications@github.com wrote:

ventoy load iso with memdisk and mount iso

No, ventoy only uses memdisk in F1 "Memdisk Mode", otherwise it uses modified ipxe.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753779620, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYLZIRFVOFG7I7FPB7TTSYFMEVANCNFSM4VLTNA2A .

[nguyenhathaitrong]

https://youtu.be/herEYQvUNH8 How to fix this

On Mon, Jan 4, 2021 at 2:21 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

I use ventoy boot iso image always see the ventoy mount iso file, if I use the map of grub4dos, it only boots the iso image

On Mon, Jan 4, 2021 at 1:14 PM A1ive notifications@github.com wrote:

ventoy load iso with memdisk and mount iso

No, ventoy only uses memdisk in F1 "Memdisk Mode", otherwise it uses modified ipxe.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753779620, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYLZIRFVOFG7I7FPB7TTSYFMEVANCNFSM4VLTNA2A .

[steve6375]

Video is Private - I cannot see it! Ventoy uses a clever method when booting .wim files. It copies X:\WIndows\System32\winpeshl.exe to X:\Windows\System\ventoy\winpeshl.exe Then it adds a special X:\WIndows\System32\winpeshl.exe file - this file contains a windows executable which gets the path of the ISO from memory, searches for that file on the USB device, loads that ISO as a virtual DVD (e.g. Y:) and then runs X:\Windows\System32\ventoy\winpeshl.exe. In this way Y: is always present and winpeshl.ini is not changed. This makes it much better when booting WinPE-based ISOs that may use non-standard winpeshl.ini files or other methods of startup. Maybe grubfm could use the same method?

[a1ive]

I use ventoy boot iso image always see the ventoy mount iso file

When I say "mount iso", I mean mount iso at firmware level, not inside the OS. The bootloader itself cannot mount the ISO inside OS, but somehow injects the driver or otherwise, so that the OS mounts the ISO itself during the boot process. If you can't understand what I'm talking about, then don't continue the discussion.

[a1ive]

Video is Private - I cannot see it! Ventoy uses a clever method when booting .wim files. It copies X:\WIndows\System32\winpeshl.exe to X:\Windows\System\ventoy\winpeshl.exe Then it adds a special X:\WIndows\System32\winpeshl.exe file - this file contains a windows executable which gets the path of the ISO from memory, searches for that file on the USB device, loads that ISO as a virtual DVD (e.g. Y:) and then runs X:\Windows\System32\ventoy\winpeshl.exe. In this way Y: is always present and winpeshl.ini is not changed. This makes it much better when booting WinPE-based ISOs that may use non-standard winpeshl.ini files or other methods of startup. Maybe grubfm could use the same method?

Maybe grubfm could use the same method?

Now wimboot will backup the file with the same name that already exists in wim as orig_xxx. For example, if there is already a winpeshl.ini in wim, it will be renamed to orig_winpeshl.ini instead of just being replaced like in older versions. https://github.com/a1ive/grub/blob/ea502952d39d5896b0f3f19c6422c595d258dc07/grub-core/map/wimboot/init.c#L136 I am not familiar with Windows batching and program development, can't do this job.

[nguyenhathaitrong]

Thanks for the tip!

On Mon, Jan 4, 2021 at 6:00 PM A1ive notifications@github.com wrote:

Video is Private - I cannot see it! Ventoy uses a clever method when booting .wim files. It copies X:\WIndows\System32\winpeshl.exe to X:\Windows\System\ventoy\winpeshl.exe Then it adds a special X:\WIndows\System32\winpeshl.exe file - this file contains a windows executable which gets the path of the ISO from memory, searches for that file on the USB device, loads that ISO as a virtual DVD (e.g. Y:) and then runs X:\Windows\System32\ventoy\winpeshl.exe. In this way Y: is always present and winpeshl.ini is not changed. This makes it much better when booting WinPE-based ISOs that may use non-standard winpeshl.ini files or other methods of startup. Maybe grubfm could use the same method?

Maybe grubfm could use the same method?

Now wimboot will backup the file with the same name that already exists in wim as orig_xxx. For example, if there is already a winpeshl.ini in wim, it will be renamed to orig_winpeshl.ini instead of just being replaced like in older versions. I am not familiar with Windows batching and program development, can't do this job.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753908840, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL5NXTI375C4SF76HGTSYGNWVANCNFSM4VLTNA2A .

[steve6375]

OK. I am not sure if winpeshl.exe can take a file as a parameter, but if so, I guess we could run 'winpeshl.exe \windows\system32\orig_winpeshl.ini' from a .cmd file? If not, I guess the original winpeshl.ini could be restored and maybe winpeshl.exe could be run again?

[nguyenhathaitrong]

If right when the map iso file, but run cmd mount iso then like ventoy

On Mon, Jan 4, 2021 at 8:12 PM Steve Si notifications@github.com wrote:

OK. I am not sure if winpeshl.exe can take a file as a parameter, but if so, I guess we could run 'winpeshl.exe \windows\system32\orig_winpeshl.ini' from a .cmd file? If not, I guess the original winpeshl.ini could be restored and maybe winpeshl.exe could be run again?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753966618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL7TFWW2RKWZLCZ6XG3SYG5CPANCNFSM4VLTNA2A .

[nguyenhathaitrong]

grubfm use multiboot command ../ventoy/core.img will return grub shell 2.04 (press f5 select ventoy)

On Mon, Jan 4, 2021 at 8:14 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

If right when the map iso file, but run cmd mount iso then like ventoy

On Mon, Jan 4, 2021 at 8:12 PM Steve Si notifications@github.com wrote:

OK. I am not sure if winpeshl.exe can take a file as a parameter, but if so, I guess we could run 'winpeshl.exe \windows\system32\orig_winpeshl.ini' from a .cmd file? If not, I guess the original winpeshl.ini could be restored and maybe winpeshl.exe could be run again?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753966618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL7TFWW2RKWZLCZ6XG3SYG5CPANCNFSM4VLTNA2A .

[nguyenhathaitrong]

grubfm.iso use multiboot ../ventoy/core.img will return grub shell 2.04 (press f5, select ventoy)

On Mon, Jan 4, 2021 at 8:19 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

grubfm use multiboot command ../ventoy/core.img will return grub shell 2.04 (press f5 select ventoy)

On Mon, Jan 4, 2021 at 8:14 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

If right when the map iso file, but run cmd mount iso then like ventoy

On Mon, Jan 4, 2021 at 8:12 PM Steve Si notifications@github.com wrote:

OK. I am not sure if winpeshl.exe can take a file as a parameter, but if so, I guess we could run 'winpeshl.exe \windows\system32\orig_winpeshl.ini' from a .cmd file? If not, I guess the original winpeshl.ini could be restored and maybe winpeshl.exe could be run again?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753966618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL7TFWW2RKWZLCZ6XG3SYG5CPANCNFSM4VLTNA2A .

[nguyenhathaitrong]

Press f5 to select ventoy in uefi mode then ok

On Mon, Jan 4, 2021 at 8:20 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

grubfm.iso use multiboot ../ventoy/core.img will return grub shell 2.04 (press f5, select ventoy)

On Mon, Jan 4, 2021 at 8:19 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

grubfm use multiboot command ../ventoy/core.img will return grub shell 2.04 (press f5 select ventoy)

On Mon, Jan 4, 2021 at 8:14 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

If right when the map iso file, but run cmd mount iso then like ventoy

On Mon, Jan 4, 2021 at 8:12 PM Steve Si notifications@github.com wrote:

OK. I am not sure if winpeshl.exe can take a file as a parameter, but if so, I guess we could run 'winpeshl.exe \windows\system32\orig_winpeshl.ini' from a .cmd file? If not, I guess the original winpeshl.ini could be restored and maybe winpeshl.exe could be run again?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753966618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL7TFWW2RKWZLCZ6XG3SYG5CPANCNFSM4VLTNA2A .

[nguyenhathaitrong]

https://youtu.be/herEYQvUNH8

On Mon, Jan 4, 2021 at 8:21 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

Press f5 to select ventoy in uefi mode then ok

On Mon, Jan 4, 2021 at 8:20 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

grubfm.iso use multiboot ../ventoy/core.img will return grub shell 2.04 (press f5, select ventoy)

On Mon, Jan 4, 2021 at 8:19 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

grubfm use multiboot command ../ventoy/core.img will return grub shell 2.04 (press f5 select ventoy)

On Mon, Jan 4, 2021 at 8:14 PM Trong Nguyen nguyenhathaitrong@gmail.com wrote:

If right when the map iso file, but run cmd mount iso then like ventoy

On Mon, Jan 4, 2021 at 8:12 PM Steve Si notifications@github.com wrote:

OK. I am not sure if winpeshl.exe can take a file as a parameter, but if so, I guess we could run 'winpeshl.exe \windows\system32\orig_winpeshl.ini' from a .cmd file? If not, I guess the original winpeshl.ini could be restored and maybe winpeshl.exe could be run again?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753966618, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYL7TFWW2RKWZLCZ6XG3SYG5CPANCNFSM4VLTNA2A .

[a1ive]

OK. I am not sure if winpeshl.exe can take a file as a parameter, but if so, I guess we could run 'winpeshl.exe \windows\system32\orig_winpeshl.ini' from a .cmd file? If not, I guess the original winpeshl.ini could be restored and maybe winpeshl.exe could be run again?

I think we could inject imdisk as winpeshl.exe, and rename orig_winpeshl.exe to winpeshl.exe after mounting iso.

[steve6375]

How to get drive letter and path of ISO file ?

[nguyenhathaitrong]

ventoy boot winpe like anhdv.iso or WinPE10_8_Sergei_Strelec_x86_x64_2020.11.27_English.iso also mount iso file

On Mon, Jan 4, 2021 at 9:05 PM Steve Si notifications@github.com wrote:

How to get drive letter and path of ISO file ?

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/a1ive/grub2-filemanager/issues/306#issuecomment-753993494, or unsubscribe https://github.com/notifications/unsubscribe-auth/ARAGYLYLASAD76A545QAIYLSYHDMFANCNFSM4VLTNA2A .

[a1ive]

How to get drive letter and path of ISO file ?

inject another text file. In addition, grub2 map boot iso under uefi will also write ventoy compatible information, and the iso that follows "Ventoy Compatible" spec can be booted directly without any modification.

[nguyenhathaitrong]

What's the difference between grubfm.iso and grubfm-pc.iso? Why did you remove grubfm-pc.iso in the latest version?

[nguyenhathaitrong]

I see grubfm.iso using grubfm.elf and grub2.05 and grubfm-pc is the same as the old version