Running Linux Mint19.3-MATE. Ventoy(finally) installed, and on the 16GB flash drive I have the iso's for antiX32b, BionicPup32b, and BionicPup64b. AntiX and BionicPup64, boot, and run, no problems. My trouble is BinicPup32 will not boot. I have made 3 different downloads of it, and placed each, 1 at a time, onto the drive,in the proper partition(with the 2 working iso's), and it just won't run.
(Sorry-I have the debug directory, but it doesn't allow me to attach the files.)
Please use this link to view the debug directory: https://drive.google.com/drive/folders/1...sp=sharing
I have an idea to improve the Auto Installation plugin for Windows to include the possibility to copy $OEM$ folders to the iso when it is in use (like an autounattended.xml), with the possibility to propose multiple $OEM$ folders for ISOs (like the xml way in the json).
That way, this opens the possibility to include parameters, apps, etc to an unattended installation with a completly untouched Windows ISO.
I think there is a problem when running parted magics secure erase feature for ATA drives when booting PM from a ventoy usb.
Parted Magic will boot just fine, it will allow you to secure erase NVMe drives, Sanitize ATA Devices, but when you click on Secure Erase ATA drives nothing happens and the menu to select which drive does not appear.
So to test PM I made a PM usb using rufus, ATA secure erase works fine.
Then made a E2B with alives grub2 file manger booted PM with default iso extension and secure erase worked fine, rebooted with alives grub2 file manger and selected the ventoy boot option and secure erase on ATA drives would not work.
So I rebooted the ventoy usb and selected the grubfm_multiarch.iso, selected PM with partnew option and all worked good.
It is only the secure erase of ATA drives that does not work, I can see the drives and their contents with PM file manager.
Tested with
Ventoy 1.14, 1.13
3 systems using uefi and bios
2 different USB drives
pmagic_2020_02_23.iso
pmagic_2019_09_03.iso
Any ideal why this is happening or what could be blocking ATA erase to run or load
On one of my systems the Ventoy menu appears all blurry and the cursor - you can't tell what is selected. Same UFD works great on my other two systems.
So after creating my Ventoy UFD using V10.014, I went into its VTOYEFI partition and added a text file to both its root and in its Ventoy folder, named ventoy.json, hoping to tell it to display the menu in TEXT mode (CLI). It had no effect. If at the Ventoy menu, I press c and type in terminal_output console (enter) then press ESC I do get the text menu. What am I doing wrong?
I have an issue for make KonbootCD 2.5 for windows working on all computers.
The main problem is to konboot operating broke Search and boot windows option (only hhhhh is displayed, see pic.1).
Also the boot from harddrive 1 2 3 ... doesn't work on all pc.
For example on my old intel laptop:
Boot from harddisk 1: got a - flashing
Boot from harddisk 2: no loader
Boot from harddisk 3: error: hd2 cannot get C/H/S valuas.
error: you need to lad the kernet first.
I think the problem is to any "Boot from harddisk" options can't find the windows installation if we got few partitions at the left before the windows partition (see pic.2).
So it became impossible to boot to windows without restarting the computer (Restarting it remove the Konboot modification).
But we can bypassing this issue in the previously version by following this tips:
- Boot the Konboot iso while using the memdisk option
- Boot a windows iso file and don't press any buton while the message "Press any key to boot from CD or DVD..." appeair.
After that Konboot can work on any windows computers with ventoy !
The new feature on 1.0.14: Auto skip Press any key to boot from CD or DVD... make this tips impossible to do now.
Can you make an option or add-on script for chose to not auto skip this prompt from a selected windows iso? Or to disable this feature.
Then, can you try to make "Boot from harddisk" working in the case of there are left partitions before the windows installation ?
Tested in an old intel laptop (BIOS: Can't find windows with any of localboot option after start Konboot), Intel Z97 desktop (BIOS: konboot give BSOD after load session even with another USB booting soft) and a virtualbox vm which have a windows virtualdisk(work great).
I have no success to get persistence for some actual UBUNTU-based distribution. The USB-Stick was created with ventoy 1.0.14 from an kUBUNTU (18.04)-PC.
The .json-Syntax (ref. below) was checked and after booting the stick, F5 Debug > Persistince reports OK. Booting kUBUNTU or KDEneon from the stick, I'm asked about using persistence and I agree. The systems start and I apply some modifications on the desktop (arrangement of icons, clock settings).
I shut the system down and restart it from the stick, again I'm asked about using persistence and I agree: But all modifications are gone, no persistence.
This is the structure of my USB-Stick (first partition):
./ventoy:
gParted-live-1.1.0-1-amd64.iso
KDEneon-user-20200625-1119.iso
kUBUNTU-20.04-desktop-amd64.iso
Manjaro-kde-20.0.3-200606-linux56.iso
ventoy
