![multiboot usb secure boot multiboot usb secure boot](https://www.sorbilene.com/wp-content/uploads/2013/03/MultiBoot-Usb-3.png)
![multiboot usb secure boot multiboot usb secure boot](https://fileswin.com/wp-content/uploads/2018/10/MultiBootUSB-Review-640x360.png)
Persistence is for short term use, IMHO, where you want the ability to install eventually, if the OS works out. Second choice would be VMs (VirtualBox or VMWare). Persistence is flaky (I've had to replace one.
#Multiboot usb secure boot full#
If these are supposed to be test boxes, full install will work much better. If this is core to your objectives, I think senjoz had the right idea. Finally, notice the persistence file names don't precisely mirror the ISO file names, because I find it easier to keep track of them this way.īy the way, you didn't mention persistence originally. Did it this way because I have two dozen ISOs on the drive (including rescue utilities), only three with persistence (which I did merely as a test, out of curiosity). Notice also that I've slotted the ISOs into directories, but that's not necessary. Including one after all three was what tripped me up for a while.
![multiboot usb secure boot multiboot usb secure boot](http://a.fsdn.com/con/app/proj/multibootusb/screenshots/328223.jpg)
Notice there are commas after the first and second stanzas, but not the third. "backend": "/persistence/mint-mate-20.dat", With those tips in view, take another shot at it and report back. This should tell you what's wrong, either with the form of entry (might be something as trivial as an extra comma) or a mismatch between an entry and the actual file names. To check whether you adapted those correctly, click F5 at boot (Tools), then Check plugin (first option) and Check persistence (fourth sub-option). The IODD Mini USB 3 SSD can load any ISO\VHD as a virtual drive and then boot from the new virtual DVD or HDD. As for the file itself, I assume you saw and used the forms of entry on the website. E2B the free USB multiboot solution for professionals An IODD will SECURE BOOT hundreds of different ISOs\VHDs. Then there has to be a directory in the partition called /ventoy (also lower case) and the ventoy.json file has to be in that directory. Let's start with, the label for the Ventoy partition has to be ventoy (lower case). Open File Manager as Root/Admin, right-click the partition, open Properties, select Permissions tab, and change to your user and group.Īs for persistence, I got it to work, but was a PITA because the ventoy.json file has to be EXACTLY correct. Yes, reformatting the partition is what made root the owner, but that's easy to fix.