Current Ventoy handles some .img packages just fine but not others, which is acknowledged in the doc/s.  I would like to learn more about the differences, how to examine an .img for information.

Example of a usable .img with Ventoy is now Easy OS:  
https://distro.ibiblio.org/easyos/amd64/...23/5.4.10/

Example of an .img which is not usable by me in any way I have discovered is Armbian for x86 (not ARM, I understand that).
https://fi.mirror.armbian.de/dl/uefi-x86/archive/

I am new to Ventoy, although a longtime Linux user.
Does persistence in Ventoy preserve Wi-Fi settings
and screen shut off time or its lack in the power settings?
I've got about a dozen ISOs in my Ventoy USB, but even in Manjaro
Wi-Fi settings are not preserved between one session and the next
when I reboot.

我在一个1T的移动硬盘上按文档安装了Ventoy，它创建了两个分区Ventoy和VTOYEFI，之后还保留一部分空间成功安装了NixOS和ParrotOS，安装NixOS的时候手动创建了EFI boot分区和root分区，用UEFI模式启动能进入grub并引导启动NixOS，用legacy模式会直接进入Ventoy引导画面也能正常启动各个ISO（存放ISO的分区现在用掉大概117G），但是当我同样手动分区并安装成功ParrotOS后，用UEFI只能进入ParrotOS或NixOS，换成legacy模式first会报如下错误:!!!warning!!! This is NOT a standard Ventoy device and is not supported"。按论坛里方法升级第二分区以及用dd写入某个字节还有尝试把压缩文件放在第一分区的ventoy文件夹下面都没能解决问题，来此求助

Hello, I would like to know if there is any way to change the default path that is used for the iso folder, for example, have the iso on a USB or external disk.

thanks

主板是微星B460迫击炮，安全模式启动在Enroll Key from disk这个页面，选了Enroll Key from disk或者Enroll Hash from disk按回车键就会一直卡死，只能手动重启。

Hello, whenever I try to copy my Win11_22H2_EnglishInternational_x64v1.iso file to Ventoy the process gets slower and slower until it gets stuck. 

I tried reinstalling both Ventoy and the iso file many times but without success. The same thing happens all the time even with a Windows 10 iso file. 

How to display HDD information and capacity?






+ vbox {
left = 90%
top = 3%
width = 10%
+ hbox {
+ label {text = "@@grub_cpu_platform" color = #FFFFFF"}
}
+ hbox {
+ label {text = "@@grub_total_ram" color = #FFFFFF"}
+ label {text = " MB" color = #FFFFFF"}
}
+ hbox {
+ label {text = "@@gfxmode" color = #FFFFFF"}
}
}

Hello!

First of all, I want to thank you for a great project!

In my network, I use a small server based on a former TV set-top box, which is built on ARM (armv7l), it runs a small armbian distribution based on Debian. And I faced a problem - I can't run iVentoy directly on this system - because the binaries are only for x86 and x86_64 architecture. I even managed to start iVentoy with "qemu-user-static" emulation, but in iVentoy settings (Boot Information - IP Configuration) Select Server IP = 0.0.0.0 and "NIC Name" - not defined. Apparently there are some limitations of QEMU emulation regarding the network subsystem. Therefore, starting the PXE Service is not possible.

So, I want to ask if you plan to create binaries for the ARM 32 architecture?

Today, I am encountering the issue of a fuzzy screen on numerous computers, while some computers are functioning properly without any problems. I would like to inquire about your experience in successfully resolving and fixing the problem of fuzzy computers. Specifically, I have utilized Sergi Strelec Boot version dated 25.06.2023

hello and Thank you very much for create ventoy 

Is it possible to upgrade the ventoy installed on my PC(not on my USB drive)?