resolution issue booting using ventoy vs e2b
There is something i just don't understand.....
When i boot the macrium rescue iso (and many others) using ventoy for e2b (and even standalone ventoy) i get a resolution that is downright ugly and so pathetic that i cannot even access certain buttons on select screens of the program. However when booted via e2b the resolution is far better and useful.
(just to add.. using Rufus gives me full resolution when working with the concerned isos (but the program is not useful for multi iso usage)
Is there any understandable reason and/or workaround for these varying outcomes and is it hardware related? My laptop can only boot UEFI and secure boot is OFF
Do you mean you get a very high resolution or very low resolution?
Have you tried the various workarounds.
F7, ctrl-w, ctrl-r, etc.
Why not ask in Ventoy forum?
Give exact example so someone can reproduce the scenario, exact iso and model of laptop, etc.
Did you tick this advanced option when making the Rescue ISO?
| Legacy EFI Screen Resolution | Select this option if you are experiencing very low, less than 1024 x 768, screen resolution in PE 10 or WinRE. Some early UEFI BIOS chipsets are incompatible with Windows 10 Pre-Installation Environment graphics output. Selecting this option will cause the PE 5.0 EFI microcode to be used instead of PE 10 when starting the rescue environment. |
I get no problems (ideaPad 300) with a UEFI64-boot on the default or Legacy EFI Macrium Rescue ISO I just made today, so your computer h/w or UEFI firmware also must play a role in the problem you are seeing (Ventoy 1.0.75 tested).
Thank you so much Steve for attending to my post....
I meant to say very low resolution (800 x 600) causing inability to access certain features/buttons/commands
What i meant to ask was whether booting with different multiboot software on the same machine can actually be cause of different resolutions on screen - Ventoy is poor resolution (800 x ), E2B and AIO are moderately good (1024 x) while Rufus delivers full HD resolution USING THE SAME BOOTABLE ISO ON THE SAME MACHINE
I have been grappling with this problem for many months now....
Yes, i have posted my problem in the Ventoy forum and received suggestions similar to what you prompted above but the issue remains....(hence my switch to and experiments with E2B. I see a few persons do have this problem and only with winPE bootable isos but it does not seem to be universal.
Yet i am a we bit mystified that different multiboot programs throw up different resolutions on the same machine using the same bootable iso
Just one more query - is the way a bios is programmed responsible for the successful/unsuccessful boot of bootable isos? and would that have something to do with the resolution offered on screen too?
For a few bootable isos i can update the graphic driver with the local intel driver files and achieve what i want but with the remaining i find there is insufficient memory to do this as graphic file drivers are huge in size. (the native basic windows vga driver can never get me a changed higher resolution)
Since i do not know much about these issues, i was interested in knowing what could bee the potential causative factors.
My laptop is an Avita Liber running win 11 64 and capable of full resolution
Resolution under UEFI is a tricky problem and I am afraid don't understand the cause but it is a common and annoying problem.
Are you talking mainly about WinPE ISOs, Linux ISOs or what?
Booting from Rufus does not boot the ISO file itself (the contents are extracted) and does not load grub2 (except if it is used by the ISO).
It will depend on the UEFI BIOS and also what OS you are booting to and if you used an intermediate boot loader like grub2 or syslinux.
Under UEFI, E2B will just boot straight to agFM menu system which uses grub2. Ventoy also uses grub2 however it may be programmed differently.
If you have an example of a specific iso on a specific computer giving different results between agFM and Ventoy then you can report the issue as a ventoy issue so it can be reproduced and fixed.
As a test, you could boot to Ventoy, then select the grubfm_multiarch.iso and then boot to the 'bad' ISO - if the resolution is OK that way but not if just using Ventoy, then the Ventoy developers may be able to improve their implementation within their grub2 version?
If you have problems (resolution or secure boot) then it is usually overcome by making a .imgPTN23 file from the ISO so that you are not booting via an intermediate grub2 boot loader.
P.S. You can try configuring the \ventoy\ventoy.json file to use a text mode menu, then it may avoid some resolution issues with Ventoy (it just means you won't see the grub2 graphical theme menu and grub2 won't switch to a graphics mode - hopefully).