One of my USB devices that has Ventoy on it would not work with memdisk mode. Upon experimenting with it, I realized that I had NTFS formatted the original exFat partition that Ventoy made. While ISO booting worked just fine, Memdisk mode will not properly load or boot ISO if the primary partition is formatted NTFS, but does work with exFat. I have not tested other filesystems, but I prefer to use NTFS over exFat where possible on my devices.

pfSense, an Open Source FreeBSD based firewall distribution is something I use and install on older workstation and server hardware to repurpose it into a firewall device. I put this on my Ventoy bootable media, but during boot of this ISO from Ventoy it cannot find a mount point of some kind and stops. Burning the ISO to CD or booting from a USB stick (without Ventoy) does not have this issue.

ISO here: https://www.pfsense.org/download/

多次测试、UEFI启动无法引导win10 ISO、但可以启动PE。

Today I tested (livecd) LuninuxOS-20.04 with Ventoy 1.0.12.
ISO: LuninuxOS-20.04-Desktop-amd64.iso
https://sourceforge.net/projects/luninux...o/download
Boot: Legacy BIOS
Processor: Intel i5-5200U (Broadwell)
Laptop: Lenovo Z51

Attached Files

Thumbnail(s)
   

If you have persistence working on an iso ie you made changes and they stuck...not just that the menu offered to boot "with persistence" please post what iso and your ventoy.json.  If so, are you running the most recent version of ventoy?

I've tried 4 different iso's.  Of them one hangs on boot with or without persistence.  The other 3 give me the option to choose "with persistence" but don't actually HAVE persistence from what I can tell.

The ventoy.json I used is (confirmed by https://jsonformatter.curiousconcept.com/ as correect):

{
  "persistence":[
      {
        "image":"/ISO/redobackup-livecd-1.0.5.1.iso",
        "backend":"/persistence/redobackup.img"
      },
      {
        "image":"/ISO/manjaro-kde-20.0.3-200606-linux56.iso",
        "backend":"/persistence/manjaro-kde-20.0.3.img"
      },
      {
        "image":"/ISO/extix-20.2-64bit-kde-refracta-snapshot-calamares-2380mb-200127.iso",
        "backend":[
            "/persistence/persistence_ext4_1GB_casper-rw.img"
        ]
      },
      {
        "image":"/ISO/lfa-64bit-lxde-efi-refracta-nvidia-1670mb-200607.iso",
        "backend":"/persistence/lfa-64bit-lxde.img"
      }
  ]
}


Contents of /ISO:
-rwxrwxrwx 1 famewolf famewolf  740294656 Aug 31  2018  bodhi-5.0.0-64.iso
-rwxrwxrwx 1 famewolf famewolf  760217600 Aug 31  2018  bodhi-5.0.0-legacy.iso
-rwxrwxrwx 1 famewolf famewolf  301989888 Jun  5 02:48  clonezilla-live-2.6.6-15-amd64.iso
-rwxrwxrwx 1 famewolf famewolf  287309824 Jun  5 02:36  clonezilla-live-2.6.6-15-i686-pae.iso
-rwxrwxrwx 1 famewolf famewolf 2564407296 Jun  5 00:08  extix-20.2-64bit-kde-refracta-snapshot-calamares-2380mb-200127.iso
-rwxrwxrwx 1 famewolf famewolf 1261371392 Jun  4 20:51  extix-20.4-64bit-efi-lxqt-nvidia-mini-1170mb-20200404.iso
-rwxrwxrwx 1 famewolf famewolf 2709946368 Jun  5 01:29  extix-20.5-64bit-deepin-20beta-live-2500mb-200517.iso
-rwxrwxrwx 1 famewolf famewolf 1410744320 Jun  4 15:27  exton-os-64bit-efi-budgie-gnome-refracta-calamares-1310mb-200319.iso
-rwxrwxrwx 1 famewolf famewolf 1799553024 Jun  7 14:00  lfa-64bit-lxde-efi-refracta-nvidia-1670mb-200607.iso
-rwxrwxrwx 1 famewolf famewolf 1502609408 Oct 23  2018  lxle-14.04.3-32bit.iso
-rwxrwxrwx 1 famewolf famewolf 1604321280 Jun  4 12:44  lxle_16.04.4_32.iso
-rwxrwxrwx 1 famewolf famewolf 3123830784 Jun  8 02:58  manjaro-kde-20.0.3-200606-linux56.iso
-rwxrwxrwx 1 famewolf famewolf 2835957760 Jun  4 17:53  manjaro-xfce-20.0.2-200531-linux56.iso
-rwxrwxrwx 1 famewolf famewolf  698351616 Jun  3 12:17  redobackup-livecd-1.0.5.1.iso
-rwxrwxrwx 1 famewolf famewolf  721420288 Jun  5 03:01  systemrescuecd-amd64-6.1.4.iso
-rwxrwxrwx 1 famewolf famewolf  707788800 Jun  5 04:23  systemrescuecd-i686-6.1.4.iso
-rwxrwxrwx 1 famewolf famewolf 1217341440 Jun 13  2018  tails-amd64-3.7.1.iso
-rwxrwxrwx 1 famewolf famewolf 1167990784 Jun  9 03:21  tails-i386-2.9.1.iso
drwxrwxrwx 1 famewolf famewolf     131072 Jun  9 14:41 'TrueNAS-12 0-MASTER-202006050424-e19f49426'
-rwxrwxrwx 1 famewolf famewolf  728922112 Jun 12  2018  Ultimate_Boot_CD_5.3.8.iso

Contents of /persistence:
-rwxrwxrwx 1 famewolf famewolf       1440 Jun  9 02:34 CreatePersistentImg.sh
-rwxrwxrwx 1 famewolf famewolf 1073741824 Jun  9 03:32 lfa-64bit-lxde.img
-rwxrwxrwx 1 famewolf famewolf 1073741824 Jun  9 03:35 manjaro-kde-20.0.3.img
-rwxrwxrwx 1 famewolf famewolf 1073741824 Jun  9 03:12 persistence_ext4_1GB_casper-rw.img
-rwxrwxrwx 1 famewolf famewolf 1073741824 Jun 13 11:16 persistence.img
-rwxrwxrwx 1 famewolf famewolf 1073741824 Jun 13 11:21 redobackup.img

vt_dump_persistence show a status of "SUCCESS" for all 4 entries and the filenames match the .json.  See screenshot.

Attached Files

Thumbnail(s)
   

I succesfully tested livecd Greenie Linux 20.04 KDE amd64 on Ventoy 1.0.12...
I think it based on Linux Kubuntu (during installation show logo Kubuntu)...
Iso: https://sourceforge.net/projects/greenie...o/download
Boot: Legacy BIOS
Laptop: Lenovo Z51
Processor: i5-5200U (Broadwell)

Attached Files

Thumbnail(s)
   

Hello
When I install ventoy, the entire receiving medium is automatically formatted in two partitions: EXFAT and FAT16.
This destroys my three partitions EXFAT, LUCKS and FAT32
Is there an option to just download the software to my FAT32 partition?

Thanks for reading me.

hello

this is a message for developers

Currently if the ventoy.json file does not exist.
or if the keyword "persistence" is not found in the ventoy.json file
or if what is written inside the keyword "persistence" has bad syntax
The application decides that there will be no persistence
it's a very bad choice.

It should decide that there is persistence and propose the second screen with the first line allowing to choose not to have persistence and the following lines should list all the files present in the persistence directory.
Indeed it seems to me that the number of files present will never be very large.

In summary: Imposing this codification on users for only a few files is a very bad idea.
If one day the user wants to filter the list, he will make the effort to correctly code the "persistence" chapter in the ventoy.json file.

FYI: I am a member of a French forum offering ventoy

Thanks for reading me

苹果电脑启动不了！！！

Hello.

Message for developers

With windows I don't know how to initialize the persistent file.

If someone gives me a ventoy key with a persistent file, I may need to initialize this persistent file again.
You should offer this option in the second screen immediately after choosing no persistence and before the list of the persistent files.

Thank you in advance for this implementation