The innovation in the latest version is excellent. We have long wanted to be able to run ISO or WIM files on any external or internal disk. Thank you for fulfilling users request
[Injection] function
iso file only.
Wim file test result.. [Inject] function does not work.
As much as possible...
Wim / VHD / iMG
It would be nice if the file also supports the [Injection] function.
(02-14-2022, 09:06 PM)hyun9358 Wrote: [ -> ][Injection] function
iso file only.
Wim file test result.. [Inject] function does not work.
As much as possible...
Wim / VHD / iMG
It would be nice if the file also supports the [Injection] function.
Injection can ONLY be used with ISO files. That's decided by the ISO file structure, so Wim/VHD/IMG will not be supported.
Hello, please explain what this means: Fix the bug that file injection does not take effect for windows.(introduced in 1.0.66).
(02-15-2022, 05:41 AM)Dumble_Hit Wrote: [ -> ]Hello, please explain what this means: Fix the bug that file injection does not take effect for windows.(introduced in 1.0.66).
In Ventoy 1.0.66 release, Injection Plugin can not be used for Windows ISO file. (In previous release, it's OK.)
https://www.ventoy.net/en/plugin_injection.html
In Ventoy 1.0.67, I fixed it.
Help. I am attempting to create and use the
vlink requirements, but I am having issues.
- I expand the tar into its own folder on root of sda2 system drive (a non-ventoy disk).
- I open the folder and proceed to a terminal within the folder
- Here are the terminal results
Code:
# echo 'The following is a console (terminal) log of use of VentoyVlnk.sh'
The following is a console (terminal) log of use of VentoyVlnk.sh
# ./VentoyVlnk.sh # list manpage for this command
invalid cmd
Usage: sudo sh VentoyVlnk.sh CMD FILE
CMD:
-c FILE create vlnk for FILE
-l VLNK parse vlnk file
-v print verbose info
-h print this help
# ./VentoyVlnk.sh --help # list manpage for this command
Usage: sudo sh VentoyVlnk.sh CMD FILE
CMD:
-c FILE create vlnk for FILE
-l VLNK parse vlnk file
-v print verbose info
-h print this help
# ./VentoyVlnk.sh -c /mnt/sda2/boot-isos/hirsute-desktop-amd64.iso # create a vlink file for this ISO
Output VLNK file is hirsute-desktop-amd64.vlnk.iso
====== Vlnk file create success =========
# ls *vlnk.iso # find the name of the ISO file's vlink
hirsute-desktop-amd64.vlnk.iso
# ./VentoyVlnk.sh -l hirsute-desktop-amd64.vlnk.iso # test for vlink file presence
Disk in vlnk not found!
# echo "uh-oh...something is wrong!" # What is wrong with this operation and why boot cannot find it.
uh-oh...something is wrong!
And moving the
'vlink' file to the Ventoy USB yields the same "-l" error.
What is wrong?
Thanks in advance for any Help leading to better understanding.
P.S. iS THIS additional info helpful?
Code:
# ./VentoyVlnk.sh -v -c /mnt/sda2/boot-isos/hirsute-desktop-amd64.iso # create a vlink file for this ISO
Create vlnk for /mnt/sda2/boot-isos/hirsute-desktop-amd64.iso
check vlnk
file size 2805891072 is not a vlnk file size
Full file path is /mnt/sda2/boot-isos/hirsute-desktop-amd64.iso
IMGPATH=/boot-isos/hirsute-desktop-amd64.iso IMGFILE=hirsute-desktop-amd64.iso
mountpoint is /mnt/sda2 dev 8:2
File system of /dev/sda2 is fuseblk
/dev/sda2 is fuseblk
/dev/sda2 is NTFS OK
Major=8 Minor=2
disk partition is sda2
PARTSTART=63031296 DISK=/dev/sda
Output VLNK file is hirsute-desktop-amd64.vlnk.iso
create vlnk
====== Vlnk file create success =========