5. If you receive a warning that files are not contiguos,
copy everything to a folder on your harddrive,
erase the USB, copy everything back to the USB and boot it again. NOTE: I usually just erase the USB as root, make sure you get it all,
then do 3.b. followed by 4.

Files must be contiguous for the chaining to work.
You ONLY need Linux.

Thanks Richard, for this post. I am one of Libre_Thing's many who has looked far and wide for linux usb stick multiboot options and found nothing that satisfied my soul. As I had zero knowledge or experience in this, names, features, and procedures were confusing and complex. So, I decided to see what my fellow MXers were using. I tend to trust them most. I first tried YUMI, as GUIs are my friend, with no joy. But, I'm cli comfortable, so your post gave me the confidence to cull Easy2Boot from the herd and try it. I now have usb stick multiboot bliss. Gratitude to you, Libre_Things, and the grub4dos folks. This is a great addition to my knowledgebase and skillset.

NOTE: The latest version of grub4dos 0.4.6a did not work. It gave me segmentation faults when installing via the ./bootlace.com command. The latest version of grub4dos 0.4.5c worked like a charm. It can be found here:https://code.google.com/archive/p/grub4 ... /downloads

I'm still using the same old 32GB easy2Boot stick I made about 1 year ago, with whichever version of E2B was the latest at that time. If I need to make space, I delete iso files from it in a Last In, First Out manner.

Maybe it's time to update the stick since a few (very few) distro isos didn't seem to work. The download link seems to indicate an update of an existing E2B stick is possible. I wonder if I should just extract all the files in the zip file and let them write over what is in the stick's root directory, or if I should first delete all the stuff in the root directory before extracting.

Development of 0.4.5c has pretty much stopped. 0.4.6a is being improved all the time but the latest version often has bugs because they do not identify a 'stable' or 'release' version.
If you use the version included with Easy2Boot, it will usually be the best, bug-free version.

To update your E2B stick, just download the latest version of E2B, unpack to a new folder and run UPDATE_E2B_USB_DRIVE.cmd - or under linux use cp -u - simple!

asqwerth wrote:. . .If I need to make space, I delete iso files from it in a Last In, First Out manner.

Maybe it's time to update the stick since a few (very few) distro isos didn't seem to work. The download link seems to indicate an update of an existing E2B stick is possible.

He says you can, but I've not tried to update E2B with it. I'll try it one day. If it is working, I'm hesitant to update it. :)

I wonder if I should just extract all the files in the zip file and let them write over what is in the stick's root directory, or if I should first delete all the stuff in the root directory before extracting.

Sometimes it works; however, I got fewer error messages if, as root, I erase the USB stick, copy back the E2B files, then copy the desired ISOs into the USB stick: /EZ2BOOT-2/_ISO/MAINMENU/

If you are careful to note the order of copying, as @asqwerth/you do, you can probably save time.
I just found that it didn't work well for me --could be because I use Double Commander and don't always note copy order-- perhaps Thunar does it cleaner.

It might be unnecessary but I do all preparations on the USB stick and copy ISOs as root.

Richard wrote:...He says you can, but I've not tried to update E2B with it. I'll try it one day. If it is working, I'm hesitant to update it. :)

I'm hesitant for the same reason.

...Sometimes it works; however, I got fewer error messages if, as root, I erase the USB stick, copy back the E2B files, then copy the desired ISOs into the USB stick: /EZ2BOOT-2/_ISO/MAINMENU/

If you are careful to note the order of copying, as @asqwerth/you do, you can probably save time.
I just found that it didn't work well for me --could be because I use Double Commander and don't always note copy order-- perhaps Thunar does it cleaner. ...

Nah, I note them down in a text file! But yes, I use Thunar and the "delete permanently" option. That seems to work very well.

It might be unnecessary but I do all preparations on the USB stick and copy ISOs as root.

Never thought of doing things wholesale in root. Something to think about.

I've been teaching my IT class about ezy2boot and I made one 2 days ago using an ultra high speed USB3.0 drive, however, as my work is windows based, I used the windows installer package to make my ezy2boot device. There was an option to format it as ntfs so it could support images larger than 4GB, so I chose NTFS as the file system.

I loaded 5 ISOs onto it immediately, 3 Windows and 2 Linux and took it for a spin. It worked flawlessly, however, I found a gotcha when using ezy2boot with the latest pmagic live ISO, which defaults to loading into RAM and umounting the boot device. If the usb drive is removed from the machine, which is perfectly normal for pmagic with no ill effects on a drive created with e.g., unetbootin, apps, tools and utils that reference /home/partimage fail when the boot drive is physically removed, but work again if the drive is reinserted. This doesn't happen with regularly built boot USB drives, only with ezy2boot.

What this tells me is there is a bug in ezy2boot, so watch out for it in case it bites you.