search for: tc64

...an't see if/how to do via GRUB. --------------------------------- Is it true that [critical but hidden facts]: <syslinux> is 16 bit, so 32 or 64 bit installations are not differentiated. The DOS 8.3 File ID restriction applies? ------- It seems to me necessary to confirm that the existing TC64 installer's isolinux.cfg can take an additional entry, for a 32bit installation on a DIFFERENT USBstik; plus the exact syntax of such additional entry. ==TIA.

...The DOS 8.3 File ID restriction applies? All BIOS Syslinux loaders (SYSLINUX, ISOLINUX, PXELINUX) start in 16-bit real mode but for the most part operate in 32-bit protected mode. No, the old DOS 8.3 filename restriction does not apply. > It seems to me necessary to confirm that the existing TC64 > installer's isolinux.cfg can take an additional entry, for a > 32bit installation on a DIFFERENT USBstik; > plus the exact syntax of such additional entry. So it seems to be the same question. TC64 still has ISOLINUX. The basics are to use chain.c32 to boot USB-B:p3 but syntax dep...

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". Hopefull...

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

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

...pt> . Of course just "chroot"ing Slak13, won't allow <make bootStik>. But why can't someone here, provide the info to make an equivalent bootStick from StikBooted TinyCore64 which already uses: /boot/isolinux isolinux.bin isolinux.cfg ..etc. Even better would be if the TC64 stikBooter could be extended to boot the Slak13 partition of the USB installed/chroot-able Slak13. Some of the key-lines of the SlakScript are:-------------------- chroot $T_PX /sbin/mkdosfs -I -n USBSLACK -F 12 /dev/$STICK $DOSSIZE 1> /dev/null 2> /dev/null fi if [ ! -d $TMP/bootd...

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 >>its location rather than "chain.c32 hdN M&quot...

...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 ca...