[syslinux] Can USBstikA boot USBstkB ?!

eas lab lab.eas at gmail.com
Wed Jun 14 03:56:59 PDT 2017

]You seem to be assuming that changing from a direct SATA and IDE
] connections to some USB adapter would have no impact on how the
] respective HDDs are recognized/detected by the BIOS.

] You seem to be
] assuming that the BIOS from 2 different PCs/Laptops would recognize all
] your devices in the same exact way and that there would be no changes
] in behavior or in supported features by the respective BIOS.

] Generally speaking, these
*WRONG* [when I wanted to buy it: I doubted I could read linux SATA]
] assumptions are not necessarily valid. There
] might be some particular case(s) in which, by coincidence, your whole
] hardware is "portable", but this is not a _generic_ situation. There
] might be some way to overcome potential differences, but we don't have
] any relevant information at this time in order to guide you in any way.

Since SYSLINUX was designed by the controllers of this forum, the
"Information" asked for does not need eg. discovery of a hidden/unknown

] Please also have in mind that this is the Syslinux Mailing List, and
] there is some practical limit as to how much guidance users can receive
] here about "whatever boot problem in the world might exist". At this
] point, there is no detail/information that actually indicates that
] there is some issue related to Syslinux in your situation; explicit
] clear information would help.

My starting point was the *SYSLINUX* partial dir-listing; to PROVE that
the issue is directly syslinux related. I'm free to ignore syslinux and
use other methods; except that the old SYSLINUX booter proved itself well
under the previous configuration. Also TC64's syslinux booter works well.

] Are you currently able to boot these OSes in any way?

Currently can only boot:
TinyCore64 Linux from stik1;
Debian7-64bit from stik2  via GRUB;
Debian7-32bit stik3 - got <damaged>.
IDE & SATA & usbToshiba can only be`chroot`-ed to via adaptor.

] When trying your USB boot stick, what exactly do you see? What's the
] behavior? What do you do and in which way it "fails"?

Imagine the size of the logs of my testing, compared to the simple
explanation that I've so far failed to convey?!

Can you read and answer the simple question of the SUBJECT of this thread,
from a THEORETICAL perspective?

---- Cut irrelevant questions -------------

More information about the Syslinux mailing list