要在Ventoy引导随身Deepin，于是在Windows 11的Hyper-V中制作了Deepin的VHDx放在Ventoy，但是启动不了

i've made a Deepin in VHDx file using Windows 11 Hyper-V, but it doesn't work at all

Ventoy 1.0.71 installed on MicroSD 32GB. Inserted in 2 MicroSD adapters. Multiple ISO inside.

   

Test on Toshiba Satellite (old model, LEGACY mode only):

LEGACY mode

Yellow adapter is booting well after boot menu (can be seen as Mass Storage Device).
All ISO's are working, even both MiniTool ISO's (MiniToolPartitionWizard v12.6 and MiniToolPowerDataRecovery v10.1) are working fine.

   

Black adapter is showing Grub shell after boot menu (can be seen as Generic USB SD Reader).

   


Test on Lenovo ThinkBook (new model, UEFI and LEGACY mode):

UEFI mode
Both adapter is booting, only 2 ISO (MiniToolPartitionWizard v12.6 and MiniToolPowerDataRecovery v10.1) are not working, both is presenting this error, even if both are x64 EFI bootable.

   

LEGACY mode

Both adapters is showing GRUB shell after boot menu (can be seen as Generic USB SD Reader or Mass Storage Device).

   


Very strange behaviour..

2022/03/11 --- 1.0.71 release

1. VTOY_DEFAULT_IMAGE can be set to F2> to automatically enter F2 browser mode.
   
   
2. Fix the bug when booting FreeBSD 13.0 in F2 browser mode.
   
   
3. Auto use memdisk mode for Memtest86+ and KolibriOS iso file.
   
   
4. Support Easy Recovery Essentials for Win10/Win11.
   
   
5. Suppress Fn hotkey when VTOY_DEFAULT_IMAGE is set to Fn>.
   
   
6. New ISO support (total 830+)
   

I hope i am able to express this adequately to you folks

When i boot an iso (say free Macrium bootable iso) i get a very ugly resolution which hides several tabs and functions and often does not let me access tabs such as 'ok' to complete an operation.   Also i do not get mouse support (i need to attach an external mouse when running most ventoy compatible isos).  Ventoy's screen resolution option does not solve my proble3m at all. 

HOWEVER, when i use Rufus to make the same iso bootable, i get a brilliant display at high resolution of the bootable software with everything visible and accessible (not needing me to push and pull screens  to get to some tabs) and i also have mouse support (on the trackpad)

Why does this huge difference in executing the two iso's occur?  what exactly is happening?

Thanks

Hello, 

Ventoy works perfectly with my 32-GB Pendrive but I haven't been able to use it from my hard disk.

I have 2TB HDD where I created a FAT32 partition installed Ventoy inside that partition.

But when I boot, it just shows a minimal grub command-line interface, nothing else.

Here is a picture:




I know there is an issue about the legacy BIOS limit, posted here: https://ventoy.net/en/doc_legacy_limit.html

However, I'm running on a UEFI setting in GPT scheme.

Is there any way to fix this?

My CPU Spec:
-----------------
Motherboard: Asrock A-320M 
CPU: AMD Ryzen 3 (2200G)
HDD: 2TB Seagate Barracuda

I checked several ISO LinuxMint images, when I exit Live mode, it is suggested to take out the flash drive and press Enter, and I do so, then I load into Windows 10 x64, insert the same flash drive, and a window appears with a notification that the flash drive is damaged and errors need to be fixed, I fix it, and this notification no longer appears. But why does it appear at all? After downloading these ISO images, this notification appears:

linuxmint-20.3-cinnamon-64bit.iso
linuxmint-20.2-cinnamon-64bit.iso
linuxmint-20.1-cinnamon-64bit.iso
linuxmint-20-cinnamon-64bit.iso

linuxmint-20.3-mate-64bit.iso

After downloading these ISO images, the notification does not appear and there are no errors on the flash drive:

linuxmint-20.3-xfce-64bit.iso

linuxmint-19.3-cinnamon-64bit.iso

Starting with version 20 of Cinnamon, flash drive errors occur.
Moreover, if you write linuxmint-20.3-cinnamon-64bit.iso, it through Rufus 3.17, then there are no errors.
All ISO images are checked with a checksum on the official website, and were downloaded from there. In addition, there are other ISO images on the flash drive, these are utilities and others. All are loaded without problems. When pulling out and inserting the flash drive later into the working system, no errors occur.

After long checks, changing flash drives, ports, that's what we managed to find out. If you boot from a flash drive with Ventoy, and specify the ISO image as the ISO image that is on the HDD (I'm trying on this linuxmint-20.3-cinnamon-64bit.iso ), then there are no errors, but if the ISO image is selected from another connected flash drive, then errors occur on the flash drive where it is located. As a result, there is a suspicion that errors occur due to the file system of the exFAT flash drive (I tried to reformat it with Windows tools, it did not give results). Then I decided to try the same operations with NTFS, Fat32 file systems with the same ISO image. As a result, there were no errors when reconnecting the flash drive.

There is an assumption that the exFAT file system is not the best choice. Is it possible to add an option in which the user himself will choose which file system the partition will be formatted to accommodate ISO images?

There is something i have never understood about using isos with ventoy

What exactly interferes with ventoy supporting all UEFI bootable isos out of the box?

Why some and not others?

For example, Minitools data recovery 9.2 works perfectly with ventoy uefi boot while 10.2 fails to....

and what tweaking is involved in making these isos compatible and who does it?

can be do it ourselves and is there a guide to it?

I am not the ultimate techie but am a great fan of Ventoy from its inception

VentoyVlnk supports .dat  but no mention is made of XML files.
Is it possible to have the Window ISO on a different partition (e.g. Ventoy USB partition 3) and also specfify XML files?

最近一直在用这台arm64的机器测试ventoy，我把他安装到了本地硬盘，同时还有一个u盘版的，都是最新的1.7

现在的问题是，我在本地硬盘给两个iso创建了vlnk，和iso在一起，但在ventoy下，他们是不可见的，无论我用本地硬盘的ventoy还是用u盘启动，这几个vlnk都是不可见的
但我把文件拷贝到u盘上，立刻就可见了。
这是什么奇怪的限制吗?

如果我给一个本地iso创建了vlnk，并拷到了u盘上，但我的u盘上有相同的iso，这时启动vlnk，会调用哪个iso？本地的还是u盘的？

另外，说明文档里提到，直接用f2启动本地硬盘时，插件时不可用的。
那么我给本地硬盘上的iso创建了vlnk，并把它拷贝到u盘，我应该给vlnk创建数据持久化文件，还是给本地iso？
但是如果我给u盘上的vlnk创建持久化文件，是不是这个dat也只能放在u盘而不能丢在本地硬盘？这台机器对u盘的读写速度不太理想，所以不太想放到u盘去

I got new hardware -- a Lenovo ThinkCentre M93p -- and while booting Ubuntu, Mint and Q4OS ISOs I've been facing the following error: