Is there a way to change the default highlighted selection for the auto installation plugin from the 1st auto install script to "boot without auto installation template"? Some times I need to use Windows installer for WinRE environment, and am always worried someday I might accidentally use wrong selection and accidentally lose someone's data.

Hi, I'm no expert in Ventoy or Linux, but I've been getting acquainted with them since a couple of years ago. One way of accomplishing that is by setting a Ventoy multiboot USB flash drive.

Most often I've been playing with MX-Linux 19.3 KDE x64 with 16 GB Persistence dat file, and so far so good saving lots of data files in the dat virtual storage for a couple of months until, I guess, I made a terrible mistake and started getting stuck at the message of the Subject above...

I have already posted in a MX Linux forum, but I was advised rather to post in a Ventoy forum.

This is how it all started:

A few days ago the system was left on for a day or two, with an extra empty flash drive attached to another USB port, when I set the system to Suspend mode in order to save a little in the electric bill, and get the system back quicker and right where it was before going to Suspend mode. Prior to turning the system back on in the day after, I decided first to replace the extra flash drive by another one, as it was not yet being used by me after all...

As a matter of fact, my guess is the system does save all current status information in regards the hardware, software, RAM and so on when going to Suspend mode, quite different from when going to shut down, of course.

Besides, now I can not either boot any other Linux in the Ventoy flash drive, neither using or not using the Persistence dat file for the MX Linux, or for any other flavor for that matter. Even the boot order in the BIOS settings has being changed intermittently for some reason beyond my reasoning.

The screen where the message is displayed is a blank one. Hitting Enter takes the cursor down like a new line (wrap). Alt-F2/F3... does not work either. Nothing can be done.

I'm writing this topic on a dual boot W7/Debian Buster, and using Dolphin I can browse the ISO and dat files in the Ventoy USB multi boot flash drive, but no any other files seen there.

I deeply appreciate if anybody knows how to address this and get the Ventoy flash drive usable again without losing any information stored in it. And, of course, without starting fresh from scratch again.

Not to mention it is a good challenge and opportunity to learn something else out of it.

Let me know of any other additional detail you might need to resolve this issue.

I can use an hex editor to do changes in the right spot if someone tells me how.

See dropbox link of the screenshots here.

First of all, thank you for Ventoy!
I have an obscure windows 10 tablet which appears to be 32 bit.
It only supports OTG USB connection and the boot manager does not recognise any USB drives.
I've managed to get into the Intel EFI shell.
My Ventoy USB is available here.

I type...

mount fs1 usb
usb:
cd efi/boot
grubx64.efi

...and I get...

"Image type X64 is not supported by this IA32 shell"

...which I presume is because the tablet is 32 bit.

How do I use Ventoy on here?

I tested (live) OpenMandriva Lx 4.2 Plasma (2021) (based on Russian linux ROSA) with Ventoy-1.0.35.
ISO: OpenMandrivaLx.4.2-plasma.x86_64.iso  (2.2GB)
Download: https://www.openmandriva.org/en/download
Boot: Legacy/MBR, UEFI64 (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U, AMD Radeon R9 graphic

Note:
I also tested OpenMandriva Lx 4.2 Plasma znver1 and not work (boot: Legacy MBR/UEFI), when iso start I see info "(...) microcode: no support for this CPU vendor" (see picture 3 above) and after this I see only OpenMandriva logo (see picture 4 above) and laptop restart.
ISO for test: OpenMandrivaLx.4.2-plasma.znver1.iso > download

Attached Files

Thumbnail(s)
               

Spam rate is increasing -- and with it the SEO benefits spammers collect by this evil -- and the problem is bound to get worse if nothing is done, until the forum collapses under their weight.

I saw it happening many times in other places; this reflects badly on Ventoy as users come to the forums to find specific help.

An easy measure that has worked well elsewhere, is preventing automatic first posts -- i.e., after registration, all users first post has to be approved by the team before it goes public.

Also, users posting spam should be immediately banned.

Other anti-spam measures can be adopted, scores of examples around the web. (E.g., see https://stopforumspam.com/)

Thanks for considering. Have a nice day.

Hello,

I read the documentation, but didn't find an answer.

Is it possible to change the default gfxmode without adding a (extra) theme? I miss such possibility in the Global Control Plugin.

many thanks
skyteddy

I tested (live) PrimTux6 Ubuntu20.04 on Ventoy-1.0.34/1.0.35.
ISO: PrimTux6-Ubuntu20.04-1-amd64-2020-12-06.iso (3.4GB)
Download: download
Boot: Legacy/MBR, UEFI (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U

Attached Files

Thumbnail(s)
   

I tested (live) Ultimate Edition 7.0 Lite Xfce x64 (based on Ubuntu/Debian) on Ventoy-1.0.34/1.0.35.
ISO: ultimate-edition-7.0-x64-lite-xfce.iso (2GB)
Download: download
Boot: Legacy/MBR, UEFI (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U

Attached Files

Thumbnail(s)
       

I tested (live) Sparky Linux 5.14 Xfce "Nibiru" 2021 (based on Debian) on Ventoy-1.0.34.
ISO: sparkylinux-5.14-x86_64-xfce.iso (1.2GB)
Download: download
Info: info site
Another info: another info
Boot: Legacy/MBR, UEFI (Secure Boot -> Disabled)
Platform: Lenovo Z51-70 Intel i5-5200U

Attached Files

Thumbnail(s)
       

I just rebuilt my Ventoy key with the version that I already had on the drive that worked perfectly before. I used it to install Acro more than once. This is the first time in Acro that I have rebuilt the Ventoy key and the first time that I have had an issue with it under any OS. I get the below when trying to access the drive to copy ISO's to it.

OS: AcroLinuxD with the Plasma desktop.