search for: usbstika

...andle the USB adapter. There are 2 separate goals: 1. booting a second USB-stik; 2. perhaps more difficult: booting ID or SATA via the USB-adapter. Apparently the USB-adapter is smart enough to hide the IDE/SATA. Using the principle of "successive refinement": my question was "Can USBstikA boot USBstkB ?". If so, then I'll tackle the IDE/SATA. When running debian7 and the USB adapter: `lsblk` lists all the IDE or SATA partitions. But that's not the question; which is <can syslinux boot USBstkB from USBstikA ?> > To find out, you could: > _ boot a Slackwar...

On Sat, Dec 2, 2017 at 10:35 AM, eas lab via Syslinux <syslinux at zytor.com> wrote: > AIM: from <isolinux> on USBstikA, > boot Debian7 installation on USBstikB. I thought we answered this but perhaps it's not the "Can I boot ISOLINUX/SYSLINUX from USB-A and boot to USB-B" whose short answer is "No" but long answer is "It depends on the BIOS/CSM mapping USB-B to another device.&qu...

AIM: from <isolinux> on USBstikA, boot Debian7 installation on USBstikB. EXISTING STATE: USBstikA is TinyCore64bit booter, with:- /boot/isolinux/* 61312 Oct 26 2016 menu.c32 24576 Oct 26 2016 isolinux.bin 2069 Nov 22 01:24 isolinux.cfg ... USBstikB-partition3: Currently boots a 32bit installation, via GRUB usi...

> I don't think that syslinux be in concern here. That's why I pasted the `ls -l` of the directory: to show that the previous working USBstik was *SYSLINUX* based.

]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

> Yes this is the SAME question, that I can't get an answer from a month ago! > > I have the files, from a USBstik [now stolen] which I previously could > edit at boot time, to boot any of my IDE or SATA partitions. How exactly were you editing (something)? Do you mean that you somehow changed some boot command from the Syslinux boot prompt during boot? In that case, which

Amazing how zillions of us victims tolerate web-based gmail ? On 12/10/17, eas lab <lab.eas at gmail.com> wrote: > Gene Cumm wrote:- >>TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >>USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >>version that you can use the "guid" or "label" options to auto-detect

[quoted lines from Ady Ady]: > At this time, Syslinux by itself cannot boot files located on a > different filesystem volume. > Using chain.c32, you can load a boot sector (MBR or VBR) located on > another device. Since the list of files located in your boot stick did > not include chain.c32, my assumption (and not only mine, if you > carefully read some of the prior

Yes this is the SAME question, that I can't get an answer from a month ago! I have the files, from a USBstik [now stolen] which I previously could edit at boot time, to boot any of my IDE or SATA partitions. Now, with a laptop, I want to boot the same IDE or SATA via a USB-adaptor to IDE/SATA. And also I want to boot a Toshiba 500GB USB disk. The obvious question is: why [if] the old system

> ]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

PS. Since I've now only got a laptop, I mostly use TinyCore linux; which is also sysylinx booted; and makes provision for *THE SLOW REACTION TIME OF SOME USB DEVICES*; which may be the subtle cause of my problem in trying to boot a second USBdevice [other than the <boot device>]. WDYS? On 6/14/17, eas lab <lab.eas at gmail.com> wrote: >> I don't think that syslinux be

Gene Cumm wrote:- >TC64 still has ISOLINUX. The basics are to use chain.c32 to boot >USB-B:p3 but syntax depends. Ideally, it's a modern enough Syslinux >version that you can use the "guid" or "label" options to auto-detect >its location rather than "chain.c32 hdN M". Hopefully your FS >label/GUID is unique sdb3 Boot Primary