I still don't see how this should matter. Please try an USB installation yourself. I just did one to specifically check this.Adys wrote:Well, there you go. Unfortunately, the tutorial in the wiki is not clear enough about this particular detail. You need the exact same version of syslinux that the ISO includes, and I don't think v4.04 is the adequate one at this point....
Syslinux is v4.04. No additional error messages.
Note: There is nothing wrong with Syslinux 4.04. The point is that the installer of syslinux needs to be the same exact version as the one in the ISO.
Explode the Salix ISO image to the USB. Then check the file structure. You won't notice ANY syslinux files or com32 whatever modules for a specific syslinux version. The only file is syslinux.exe which is the syslinux installer binary for Windows.
Now do an installation through the install-on-USB.sh script. The only files related to syslinux that are CREATED are syslinux.cfg and ldlinux.sys. So I don't see how any incompatibilities should arise when all files are created by the same version of syslinux that is used to install it. Maybe the .cfg file, but their syntax is extremely stable and the feature set used by us is absolutely minimal, so that can't be a problem either.
I think that confirms that we can strike this out. I guess we've just got some messed up metadata on those sticks which is tidied up by zeroing the beginning of the stick. If somebody with that issue which is solved by zeroing the beginning of the device could mail me a disk image, I could possibly say more. But if it is what I believe it is, I doubt much can be done about it. Anyway, I would definitely take a look at it.
Maybe hybrid images are the way to go?