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?

Thank you.

My ventoy.json file is a text file; it contains:

{
    "theme": {
        "file": "/ventoy/theme/blur/theme.txt",
        "gfxmode": "640x480",
        "display_mode": "CLI",
        "ventoy_left": "5%",
        "ventoy_top": "95%",
        "ventoy_color": "#0000ff",
        "fonts": [
            "/ventoy/theme/blur/Hack-12.pf2",
            "/ventoy/theme/blur/Hack-14.pf2",
            "/ventoy/theme/blur/Hack-16.pf2"
        ]
    }
}

Hello,

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).

Thank's in advance

Attached Files

Thumbnail(s)
       

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

./ventoy/ventoy:
KDEneon20200625.img
kUBUNTU200400.img
Manjaro2003.img
ventoy.json

This is my .json:
{
  "persistence":[
      {
            "image": "/KDEneon-user-20200625-1119.iso",
            "backend": "/ventoy/KDEneon20200625.img"
      },
      {
            "image": "/kUBUNTU-20.04-desktop-amd64.iso",
            "backend": "/ventoy/kUBUNTU200400.img"
      },
      {
            "image": "/Manjaro-kde-20.0.3-200606-linux56.iso",
            "backend": "/ventoy/Manjaro2003.img"
      }
  ]
}

How to solve this?
Thank you, Michael

I tested livecd (maybe old?) Win10586PESE-x64 16.07.07 with ventoy-1.0.14.
ISO: winpese-x64_16.07.07.iso
Download: download (1,01GB)

Boot:
- Legacy - OK
- UEFI - not boot
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
       

I tested livecd Easy Recovery Essentials Pro EasyRE XP-7-8-10 with ventoy-1.0.14.
ISO's: EasyRE_WinXP.iso, EasyRE_Win7.iso, EasyRE_Win8.iso, EasyRE_Win10.iso

Download (archive include all ISO's): download

Tested - work: EasyRE_WinXP.iso, EasyRE_Win7.iso, EasyRE_Win8.iso
Tested - not work: EasyRE_Win10.iso

Boot:
- Legacy
- UEFI - not work

Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell)  laptop: Lenovo Z51-70

Attached Files

Thumbnail(s)
   

I tested livecd Ikki Boot 9.1 with ventoy-1.0.14.
ISO: Ikki_boot_9.1.ISO
download: https://ikkiboot.tuxfamily.org/en/download.html
Boot:
- Legacy
- UEFI (Secure Boot disabled)
Platforms test:
- processor: Intel i5-2410M (Sandy Bridge)  laptop: Packard Bell EN TS1HR
- processor: Intel i5-5200U (Broadwell) laptop: Lenovo Z51-70

Pic. 1: Ikki Boot Start menu with Legacy boot
Pic. 2: SliTaz after run from Ikki menu (Legacy/UEFI)
Pic. 3: Ikki Boot menu with UEFI boot

Attached Files

Thumbnail(s)
           

Good morning all,

I have not found how to add icons to the halt, reboot, search ... return submenu. Maybe this option could be integrated in a future version?

Thanks.

Hello !
Can you give me an example in order to display an icon in front of each "iso" file used.

I don't really understand the doc
https://www.ventoy.net/en/plugin_menuclass.html

The isos files are in a directory named isos

I created a sub directory named icons (+ icons) in the theme directory
the icon names correspond to the key line of the ventoy file

In the ventoy.json file, I have these lines...
{
    "theme": {
        "file": "/ventoy/theme/Vimix/theme.txt",
        "gfxmode": "1920x1080."
        "display_mode": "GUI",
        "ventoy_left": "5%."
        "ventoy_top": "95%",
        "ventoy_color": "#0000ff"
    }
}

{
    "menu_class": [
        {
            "key": "Acronis."
            "class": "Acronis_Bootable_PE_Media_06.2020"
        },
        {
            "key." Acronis-Backup-advanced",
            "class": "Acronis_Backup_Advanced_11.7_50230_en"
        },       
        {
            "key": "R-Drive-Image",
            "class": "R-DriveImage."
        }
    ]
}

exemple :
my iso name  is Acronis_Bootable_PE_Media_06.2020.iso  ( in the folder ISOS)
the respective icon is named 'Acronis.png  (in the folder   theme/icons )

Greetings

Hello and thank you for this great tool ! It really meets a need, and in such an elegant way.

My question is somehow related to the recent "advanced boot options" thread. Having no technical skills to understand Ventoy internals or json stuff, I was amazed at the persistence plugin, because it manages to boot as if a "persistent" option had been passed.
As you pointed, user can always enter boot options after ISO has been launched, and probably must do so to *remove* options (like "quiet"); but it can be a crippling task for beginners, moreover if they have to enter the options with the wrong keyboard layout ! So, when making a "multi-distros demo key" with Ventoy, I dream I could just edit ventoy.json to pass something like : "locale=fr_BE console-setup/layoutcode=be" and/or "toram".
Would it be possible in a future release ?