chrispop99 wrote:From the last sentence, it would not seem likely that the developers would be interested in sorting this out themselves.

Elsewhere in their FAQ under How can I get my distribution supported by UNetbootin? they say to file a Unetbootin bug report, which I've done.

I've also tested using Syslinux directly and our menus worked perfectly. Unetbootin uses Syslinux on fat32. I copied the contents of one of our iso's to a fat32 partition on a usb stick. I renamed /boot/isolinux/ to /boot/syslinux/ and in that directory renamed isolinux.* to syslinux.*. I than ran syslinux -i -d /boot/syslinux $DEVICE.

This should be *very* easy for the Unetbootin devs. It would be great if they would also support persistence which can be as easy as just one extra command to create a rootfs file.