Why does Macrium PE boot into 1024x768 resolution instead of 1920x1080 resolution when I boot MacriumRescue.iso from Ventoy?  I'm using ASUS UEFI BIOS.

Why is Ventoy based on GRUB 2.04 instead of GRUB 2.06?

I have a 1TB nvme SSD in an external USB enclosure on which I installed Ventoy using the Windows installer, also creating a 850GB partition for general use.  This I formatted to NTFS and assigned a drive letter.  I noted the Ventoy partition had been assigned a drive letter and I created just a folder on there for now.

I then ejected the drive and reconnected it.  The access light flashed about twice a second for maybe a minute then went off.  During this time Drive Manager showed nothing mounted then, after the access light went dark, an uninitialized disk was shown.  Attempted to initialise this gave the message "Virtual Disk Manager: Incorrect Function".

Any thoughts what's going on here and what my options are for 1. Getting my SSD back and 2. Getting Ventoy working.

某些版本的Linux需要ext4格式分区保存数据，比如easyos和fossadog等，希望能提供格式化数据分区为ext4格式的选项，或者提供把fat/ntfs格式分区转换为ext4格式的功能，这样能方便用户免去自己操作分区带来的风险。

• 2023/04/05 --- 1.0.91 release
  

1. Add support for FreeBSD 14-CURRENT.
   
   
2. Fix the issue for booting Bliss OS 15.x (#2329)
   
   
3. Fix a bug that Fedora boot error if Ventoy partition is NTFS. (#2333)
   
   
4. Add Recognition for NTFS with large cluster size (greater than 64KB).
   
   
5. Improve grub2 mode process for legacy BIOS mode.
   
   
6. languages.json update.
   

实际情况：
初装的固态硬盘分区为（ventoy文件区，vtoyefi引导区）多系统启动正常，我想划出100G拿来玩Linux（VDI已经会了，想体验直接装与VDI的区别）

调整后分区为（ventoy文件区，闲置100G无区，votyefi引导区），启动失败，提示this is not a standard ventoy device，让我选择重启关机啥的

再调整分区为（ventoy文件区，ext4区，votyefi引导区），启动失败，提示我minimal bash-like line editing is supported，进的grub命令行

我的问题是，ventoy盘，可以划出一片直接安装别的系统吗？怎么操作

Ventoy菜单提示插件的提示文字大小调整，如何设置？
官网上的插件说明中没有说明，提示文字的大小是不可以设置吗？
多谢回答！

I am a newcomer to Ventoy and like the idea of being able to select among multiple ISOs to boot. However, after preparing a 32GB USB stick with Ventoy 1.0.90 under Linux and putting multiple ISOs on the stick, Ventoy is not able to see the ISOs on either of the two computers I tried.

Ventoy boots fine but there are no ISOs visible, nor can I find them when I use F2 to move around on the stick. Mounting the stick on another computer I see the ISOs in the Ventoy partition as expected.

What could I be doing wrong? Is there a step I have missed to make them visible in the Ventoy menu?

Is there a way to prevent VTOYEFI from auto-mounting from the MBR formatted Ventoy USB drive on another PC or after using mountvol /r?  When I unplug the USB drive and then run mountvol /r then plug the drive back in it auto-mounts both the Ventoy and the VTOYEFI partitions? MBR uses type EF for the VTOYEFI partition which means EFI System Partition but is not hidden. GPT uses GPT attributes 0xC0000001 for the VTOYEFI partition which is both hidden and no auto-mount.

Hi all,
for practical and performance reasons I am trying to copy from my USB driver .ISO and casper-rw files on the target (temporary) computer first partition (ext3)
I manage to boot successfully by F2 browsing the disk, but not giving persistency.
I tried to manually add "persistence" to the boot command line, but it does not work (it is not a FAT partition)
then I tried to configure ventoy.conf file adding (hd1,1) to the path, but as you see it is parsed as 'invalid'
Any further ideas ?
cheers
"persistence":[
        {
            "image": "/YUMI/Linux-ISOs/linuxmint-21.1-mate-64bit.iso",
            "backend":[
                "/YUMI/Linux-ISOs/persistence.dat"
            ]
        },
{
            "image": "(hd1,1)/boot/boot-isos/linuxmint-21.1-mate-64bitHDD.iso",
            "backend":[
                "(hd1,1)/casper-rw"
            ]
        },
        {
            "image": "/YUMI/Linux-ISOs/linuxmint-21.1-xfce-64bit.iso",
            "backend":[
                "/YUMI/Linux-ISOs/casper-rw"
            ]
        }
    ]