Syslinux - Nov 2017 - Booting USBdeviceB [as root} from USBdeviceA:booter ?

My previous question: "can syslinux on a USBstik also boot installations
on other USB devices ?" got no proper reply, so I'm now including more
background detail.
The new problem is that my 32bit partition of ETHOberon, only gives
a proper font-size under Debian7:DVDinstaller:rescueMode, since I'm
forced to use a laptop, after my previous systems were stolen.
Neither gnome nor Xcfe allow changing the 13786x786 resolution, altho'
M$ 8.1 does, so it's not a hardware limiation.
>From eg. /mnt/sr0/isolinux/rqgtk.cfg =  label rescuegui
        menu label Graphical rescue mode
        kernel /install.386/vmlinuz
        append video=vesa:ywrap,mtrr vga=788 initrd=/install.386/gtk/
        initrd.gz rescue/enable=true -- quiet
it seems that the vital parameters which give the good <font size> are:
  "video=vesa:ywrap,mtrr vga=788"

On the DVD,
/mnt/sr0/install.386 looks like:-
|-- gtk
|   |-- initrd.gz
|   |-- install.bat
|   `-- vmlinuz
|-- initrd.gz
|-- install.bat
|-- vmlinuz
`-- xen
    |-- debian.cfg
    |-- initrd.gz
    `-- vmlinuz
2 directories, 9 files

and /mnt/sr0/isolinux looks like:-
|-- adgtk.cfg
|-- adtxt.cfg
|-- boot.cat
|-- dtmenu.cfg
|-- exithelp.cfg
|-- f1.txt
|-- f10.txt
|-- f2.txt
|-- f3.txt
|-- f4.txt
|-- f5.txt
|-- f6.txt
|-- f7.txt
|-- f8.txt
|-- f9.txt
|-- gtk.cfg
|-- isolinux.bin <-ISOLINUX 4.05 20121210
|-- isolinux.cfg
|-- kde
|   |-- adgtk.cfg
|   |-- adgtkdt.cfg
|   |-- adtxt.cfg
|   |-- adtxtdt.cfg
|   |-- gtk.cfg
|   |-- gtkdt.cfg
|   |-- menu.cfg
|   |-- prmenu.cfg
|   |-- prompt.cfg
|   |-- txt.cfg
|   `-- txtdt.cfg
|-- lxde
|   |-- adgtk.cfg
|   |-- adgtkdt.cfg
|   |-- adtxt.cfg
|   |-- adtxtdt.cfg
|   |-- gtk.cfg
|   |-- gtkdt.cfg
|   |-- menu.cfg
|   |-- prmenu.cfg
|   |-- prompt.cfg
|   |-- txt.cfg
|   `-- txtdt.cfg
|-- menu.cfg
|-- prompt.cfg
|-- rqgtk.cfg
|-- rqtxt.cfg
|-- spkgtk.cfg
|-- splash.png
|-- stdmenu.cfg
|-- txt.cfg
|-- vesamenu.c32
`-- xfce
    |-- adgtk.cfg
    |-- adgtkdt.cfg
    |-- adtxt.cfg
    |-- adtxtdt.cfg
    |-- gtk.cfg
    |-- gtkdt.cfg
    |-- menu.cfg
    |-- prmenu.cfg
    |-- prompt.cfg
    |-- txt.cfg
    `-- txtdt.cfg
3 directories, 60 files

Q1.
Can the TC-64bit /boot/isolinux/isolinux.bin =ISOLINUX 4.05 0x4f92e181
 system be given an entry which will boot the 32bit Slackware
 installation on partn4 of another divice [USB driven disk] which
 lookslike:-
Disk /dev/sdc: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

   Device Boot  Start      End      Blocks  Id System
/dev/sdc1   *       1       88      706828+ 83 Linux
/dev/sdc2          89      358     2168775  83 Linux
/dev/sdc3         359      763     3253162+ 83 Linux
/dev/sdc4         764    21161   163840866+ 83 Linux <-ETHOinstltn

Q2. Can syslinux be installed to this 500.1 GB device, without messing
the existing sdc2,3,4; and also be able to boot installations on OTHER
32bit USB devices, plus 64bit TC ?

== TIA

On Tue, Nov 14, 2017 at 8:52 AM, eas lab via Syslinux
<syslinux at zytor.com> wrote:
> My previous question: "can syslinux on a USBstik also boot
installations
> on other USB devices ?" got no proper reply, so I'm now including
more
> background detail.
I thought it did get answered at least twice.

<snip/>
> Q1.
> Can the TC-64bit /boot/isolinux/isolinux.bin =ISOLINUX 4.05 0x4f92e181
>  system be given an entry which will boot the 32bit Slackware
>  installation on partn4 of another divice [USB driven disk] which
>  lookslike:-
> Disk /dev/sdc: 500.1 GB, 500107862016 bytes
> 255 heads, 63 sectors/track, 60801 cylinders
> Units = cylinders of 16065 * 512 = 8225280 bytes
>
>    Device Boot  Start      End      Blocks  Id System
> /dev/sdc1   *       1       88      706828+ 83 Linux
> /dev/sdc2          89      358     2168775  83 Linux
> /dev/sdc3         359      763     3253162+ 83 Linux
> /dev/sdc4         764    21161   163840866+ 83 Linux <-ETHOinstltn
I thought someone said it is ENTIRELY dependent on what your given
system BIOS bothers to do.  If your BIOS does not map the second USB
stick to another hard drive disk ID, it will not be accessible.  There
is no better answer.
> Q2. Can syslinux be installed to this 500.1 GB device, without messing
> the existing sdc2,3,4; and also be able to boot installations on OTHER
> 32bit USB devices, plus 64bit TC ?
That's two separate questions.

2a) Sure, SYSLINUX can be installed to sdc1, assuming a bootable MBR
is in place or your BIOS presents this 500GB device as yet another
hard drive.

2b) ISOLINUX and SYSLINUX (BIOS) start in 16-bit mode and can happily
boot 32-bit or 64-bit OSs.

-- 
-Gene