I would like to ask if there is a way to create a USB without ISO selection so that it can find and boot the internal M2 drive with EFI Win10 OS on it?

For example in this way:

{
    "control": [
        { "VTOY_MENU_TIMEOUT": "10" },
        { "VTOY_DEFAULT_IMAGE": "F4>Search PCIE M2 and boot EFI Windows" }
    ]
}

Not all BIOS'es support M.2 in PCIE ver.2 slot. A simple upgrade eliminates this problem But, in order for the BIOS to load the OS, you need to insert an additional module into the BIOS. And this is already complicated and can cause problems.
I would think it would be much more convenient to boot from tiny USB which redirect booting to PCIE slot with Windows EFI in it. Such an option would also be convenient in the case when you have to frequently replace other disks in the computer.

Hi

iventoy crashes without an error message if there is a SPARC boot ISO image in the iso directory -- example:

I can't use my windows 7 as host for iVentoy since the beginning till recent 1.0.17
It start and open web link but nothing working and non clickable and frozen, I check on one PC and one laptop with Win7 and both have same Freeze symptom
The freeze maybe go away after a while but click on one item and again freezing
The Green play not start or if start, iVentoy immediately will Crash. i check with different Windows ISOs
It work fine on Windows 10 LTSB and i can manage it from my Windows 7 PC browser
I read in some post you said it only need Visual C++ .. both my Win7 are fully updated and with latest Visual C++
can you please tell me if Win7x64 supported? and if yes is there any Requirements ?

Thank you for great SW

I have created an entry in ventoy_grub.cfg for booting void linux from /dev/sda6 on a Ventoy disk, but get an error msg:-

error: unknown filesystem.
error: you need to load the kernel first.

The same grub.cfg works fine when I try booting from a non-Ventoy disk.

Can someone explain what is going on and how to overcome this error?

Boot menu contains many directories, every directory hold ISO files.
1.how can I set background to specified directory  in boot menu that contains iso files differ than them background.
For example, if I want to install windows 10, I should enter windows directory from boot menu, then the background should change to microsoft.
This feacher exist in grub boot.
2.how to write comment in json file.

• 2023/07/21 --- 1.0.17 release
  

1. Fix a boot issue with ExternalNet DHCP Mode.
   
   
2. Bugfix, comments and suggestions are welcome.
   

Hello,

I installed iVentoy on Debian Bookworm and set up NFS file share from which I get .iso images.

I want to know is there any way to set that when I upload new image in my file share that it is synced to iVentoy iso folder without restarting service.

Has  anyone that uses BIBM been able to boot a Ventoy flash USB from the BIBM boot menu? For me, Ventoy won't boot from there with a
strange message that says the boot sector does not support its location on the hard drive. For some reason BIBM doesn't like the
way the flash is created. I don't have problems with other bootable flash USBs. Thanks for any infos on this.

I want to deploy iVentoy in my labs to streamline my VM deployment and automate the installation. I've set up a completely new Ubuntu 22.04 new VM:

Hi all,
I have debian-live-12.0.0-amd64-kde.iso on a ventoy cd.
The linuxmint-21.1-cinnamon-64bit.iso works fine with persistance

BUT when I choose debian-live-12.0.0-amd64-kde.iso ventoy does go through the boot up correctly and allows me to choose debian-live-12.0.0-amd64-kde.iso with persistance. I can log into the desktop and install apps, but when I reboot, theres no persistance. ie it DOES NOT SAVE BETWEEN SESSIONS.

Here is my directory structure:
.
├── debian-live-11.7.0-amd64-kde.iso
├── debian-live-12.0.0-amd64-kde.iso
├── linuxmint-21.1-cinnamon-64bit.iso
└── ventoy
    ├── persistence_debian-live-11.7.0-amd64-kde.dat
    ├── persistence_debian-live-12.0.0-amd64-kde.dat
    ├── persist_LM-21.2-cinnamon.dat
    └── ventoy.json

1 directory, 7 files


*The persistence_debian-live-12.0.0-amd64-kde.dat is simply the  persistence_ext4_4GB_casper-rw.dat  file renamed.
* Here is my ventoy.json file:
{
    "persistence":
    [
        {
            "image": "/linuxmint-21.1-cinnamon-64bit.iso",
            "backend":"/ventoy/persist_LM-21.2-cinnamon.dat"
        },
        {
            "image": "/debian-live-12.0.0-amd64-kde.iso",
            "backend":"/ventoy/persistence_debian-live-12.0.0-amd64-kde.dat"
        },
        {
            "image": "/debian-live-11.7.0-amd64-kde.iso",
            "backend":"/ventoy/persistence_debian-live-11.7.0-amd64-kde.dat"
        }
    ]
}



Is there something I'm missing for debian 12 to make it persistant?
Why does Linuxmint 21.1 work perfectly with persistance and not debian 12?

Any help would be appreciated.

thanks
saru