[syslinux] SYSLINUX 3.11-pre3 -- release candidate

[Bernd Blaauw]

Michael_E_Brown at Dell.com schreef:
> FYI (if anybody else is interested in this config), here is what we are
> using (short version):
> 
> Syslinux boots from HDD, loads memdisk + floppy A: image from HDD.
> Syslinux then chainloads to the floppy A: image.
> 
> Inside the floppy A: image, we again have syslinux+memdisk. This next
> memdisk takes over floppy B: and chainloads the boot sector in floppy
> B:.
> 
> This is a pretty cool and elegant solution to our problem. :-)

This seems like a horrible solution :)
But if it works, great!

Would MEMDISK be able to integrate the chain.c32 code?

Syslinux.cfg would have to specify:
-which imagefile(s) make up Memdisk floppydrive0, if any
-which imagefile(s) make up Memdisk floppydrive1, if any
-which imagefile(s) make up Disk emulation, if any
-which drive to boot :
  chain.c32 for physical floppies and for memdiskA and memdiskB

This way you could load an imagefile into RAM from Syslinux, and access 
it despite booting from another medium.

To be honest I have no idea how this would be implemented:

# Memdisk floppy A:, Memdisk floppy B:, Real C:, Memdisk harddisk D:
# boot from 0x80 instead of 1 of the emulated disks.
Label MDISK
kernel memdisk
append initrd=floppyA1.img,floppyA2.img c=XX h=YY s=ZZ floppy floppy=0
append initrd1=floppyB.img c=XX h=YY s=ZZ floppy floppy=1 ro raw
append initrd2=harddisk.img c=XX h=YY s=ZZ harddisk harddisk=0x80
append localboot 0x80

ok, this also looks horrible :)

Bernd