I'm inclined to agree with the advice offered by Guy. If you don't want to do it that way, then first decide on a
filesystem, DOS or Linux based, and select the correct bootloader. From the Info file for syslinux.tcz:
bootloaders for MS-DOS FAT filesystems (SYSLINUX),If you decide on a Linux filesystem, the info file states:
network booting (PXELINUX),
bootable "El Torito" CD-ROMs (ISOLINUX), and
Linux ext2/ext3/ext4 or btrfs filesystems (EXTLINUX).
Howto:If you choose to use a DOS based filesystem, visit the syslinux Wiki for more information:
$ sudo mkdir -p /mnt/sda1/boot/extlinux
$ sudo extlinux -i /mnt/sda1/boot/extlinux
copy and rename config from tinycore iso...
$ sudo cp /path-to-file/isolinux.cfg /mnt/sda1/boot/extlinux/extlinux.conf
The only thing that's confusing using ext3 exclusively is why when
the filesystem is identically restored on an additional flashdrive,
that partition has the same UUID, label, format, and every other
parameter there is, why that darned mbr.bin dd'd to the first 440
bytes of the flash drive won't allow that drive to boot successfully.
Let me read the info on the AppsBrowser tomorrow and perhaps
some idea there will click up.
It syslinux(extlinux) which is already configured must be looking from
the MBR to sda1, instead of to sdb1 or wherever the flash is installed.
Happens with grub if I don't change the root to hd0,0 in menu.lst on
the flash. Then it boots infallibly when I restore the OS to a flash.
The flash is hd0,0 even tho it isn't sda1. Don't know how to fix that
with syslinux(extlinux). I suspect that's the only problem left