ventoy / vtoydump Goto Github PK

good project !
but it doesn't boot with a 32bit uefi boot. some computers use it like asus transformer book or MacBook 2.1 (I don't know why). to boot with uefi 32 we need a file named "bootia32.efi" in the efi directory.

It seems vtoydump does not work on kernel 6.1 (haven't tried 6.0) but on this one it says there is not ventoy environment or something similar. (the system was booted through Ventoy of course). Tried the same with 5.19 and it reports correctly the iso file and environment.

Great project.
Will be great a GUI for Linux based systems.
in the other hand, I didnt find an option for persintence of data after restarting.

Thanks

检查发现和我构建的PE没关系。
Legacy 模式下，即便是在原版的安装镜像下手动调用命令提示符执行 vtoydump 也不会返回镜像路径。UEFI 模式下就可以正常返回路径。

手头暂时没有 Version 1903 / 1909 的安装镜像测试，但在 Version 1809 下执行同样的 vtoydump.exe 构建可以正常返回路径。

如下图，使用 Hikari PE (Ventoy Compatible) 测试。
ISO 路径是 "/中文测试/Hikari_PE_X64_V8.2_R2_SC.iso"，Ventoy 启动 PE 后无法挂载 ISO，vtoydump 取出的路径好像不对。

若路径改为 "/engtest/Hikari_PE_X64_V8.2_R2_SC.iso"，则一切正常。

I am impressed with ventoy, less so with vtoydump.

It would be helpful in your readme if you stated that vtoydump has to be run with admin privileges. That would have saved me time scratching my head wondering why it did not work, i.e. sudo vtoydump.

In the git package there is a binary, vtoydump64. I have two custom isos, one built off ubuntu 18.04 (bionic) the other 20.04 (focal). sudo vtoydump64 worked in the focal iso, it did not in the bionic iso, vtoydump64: /lib/x86_64-linux-gnu/libc.so.6: version GLIBC_2.28' not found (required by vtoydump64). Can I install a later version of libc6 in bionic - NO. If you are going to include binaries, a version built on older ubuntu/debian would be more helpful.

So I installed ubuntu 18.04 in a VM. Is there any documentation stating what packages are required to build using your build.sh script - NO. I guessed build-essential would probably be required, installed it. Ran script - error. It took some googling on the error to find out I also needed to install gcc-multilib. Did the script then run without error - NO. Looking at the build folder I have 32 and 64 bit versions of vtoydump, what is happening? More googling.

If you want to build both AMD and ARM versions of vtoydump in the same script you could at least have a menu:

1. AMD version.
2. ARM version.
3. Both.
   Enter 1, 2 or 3:

and wrap the build code in a case or if statement. It is not difficult. Did the version of vtoydump built in bionic work in both my isos - YES.

You want devs to make their isos 'ventoy compatible' and ventoy is a good product, but being generous - your documentation and build script for vtoydump is sloppy. Want us to support ventoy, you need to improve.

All you have done here is leave one dev irritated.