YUMI (tested with YUMI 2.0.2.0 and previous versions) is not able"as-is" to correctly include antix-15.1-a1 (same problem with antix-15) in a multiboot USB pendrive. The result fails to boot. It worked OK with antix-13.2

But it's easy to fix. This is probably already known, but just in case:

Run YUMI to include antix-15.1-a1 in your multiboot USB pendrive, as usual
Once the process is finished, just open this file in the pendrive: /multiboot/antiX-15.1-a1-V_386-full/boot/syslinux/syslinux.cfg and change this line: with this line: you can also include other"boot parameters" (see
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://www.mepiscommunity.org/wiki/system/boot-parameters"
linktext was:"http://www.mepiscommunity.org/wiki/syst ... parameters"
====================================
) or"antix live cheat codes" (see
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://antix.mepis.org/index.php?title=Howto_articles#antiX_live_cheatcodes"
linktext was:"http://antix.mepis.org/index.php?title= ... cheatcodes"
====================================
) so the line could be like this:

Many thanks for that!

So should we let YUMI devs know what is the correct way? ie replace image_dir= for bdir=

Apparently, YUMI always puts"image_dir=" parameter in file syslinux.cfg, with all antix versions.
This has worked with antix-13.2
But for antix-15.1 and antix-15 it doesn't work (error"can't find antiX filesystem" during boot, if I remember correctly), so you have to manually replace"image_dir=" parameter with"bdir="

I've tested to also change"image_dir=" with"bdir=" in antix-13.2. It keeps booting correctly.
So, yes, my understanding is that you can say to YUMI devs that they should just change"image_dir=" with"bdir=" and then antix-13.2 and also antix-15 will be correctly supported.