This topic is marked as [solved], so this is just FYI.
According to the feedback from flebber
, the UFD is booting and working correctly, but... I don't know what (form BIS results.txt)
The integrity check of the ADV area failed
, the following is NOT correct:
when the syslinux command is called to install syslinux all those files are copied over in a working version
What the installer of syslinux essentially performs is:
1_ copy ldlinux.sys to the indicated (by the installer command) location;
2_ modify the MBR/PBR with the exact location of ldlinux.sys.
So the rest of the files (modules, memdisk and so on) need to be updated to the respective version separately, either manually or by means of some script.
AFAIK, in the case of unetbootin the menu.c32 module and the respective syslinux.cfg file are added, so the version of that first menu.c32 should be compatible with what unetbootin does about ldlinux.sys and in the MBR of the UFD. Neither unetbootin nor the syslinux installer would touch any other component of syslinux that any distro would already contain within the original ISO (now expanded in the UFD by unetbootin).
In short: if a user manually updates the MBR/PBR and ldlinux.sys with the syslinux installer, then it is also recommended to manually update (copy over) all the syslinux components in the UFD (in whichever directory they would be located). This is the general recommendation, but there are some cases where components of different versions of syslinux would work together correctly anyway.