[syslinux] Question of syslinux chainloading

Adan Calderon adancalderon at gmail.com
Thu Apr 4 05:56:06 PDT 2019

Lu Wei,

For the DOS portion make sure you have a working FAT-32 DOS Bootable
Drive first.  Back up it's boot sector into a file. This file will
probably be 512 Bytes and if you were to open it with a Hex editor it
would start with ".X.MSWIN4.1" and end with "SYS~..WINBOOT SYS..U"
This would of course be looking at the ASCII view.  Assuming you put
the file in the DOS directory and that your file is named PBR.BS

Your entry would look something like this

MENU LABEL Boot MS-DOS 7.10 from USB Partition
COM32 chain.c32
APPEND fs file=/DOS/PBR.BS nosect

After you backed up the boot record into the file you can proceed to
install syslinux on the drive.


On Thu, Apr 4, 2019 at 8:43 AM Lu Wei via Syslinux
<syslinux at syslinux.org> wrote:
> Greetings,
> I encounter a problem that should be basic, but I can't get a clue. I
> have 8G USB disk formatted as FAT32. I run (syslinux -i -s -r -m H:)
> to make it bootable, and write syslinux.cfg according to the
> documents, but it will not boot some items.
> Syslinux is 6.03, bios files used. The whole syslinux.cfg file:
> ------------------------------------------------------------------------------------------------
> path /syslinux
> UI menu.c32
> prompt 1
> timeout 250
> menu title Multi-purpose Boot Disk
> #This item fails
> label normal
> menu default
> menu label Boot from ^hard disk
> com32 chain.c32 hd1
> label loadhd
> menu label Boot from local ^NTLDR
> com32 chain.c32 ntldr=/ntldr
> #This item fails
> label dos
> menu label MS-^DOS 7.1
> com32 chain.c32 msdos7=io.sys
> label dosimg
> menu label MS-^DOS 7.1 super boot disk image
> kernel memdisk
> append initrd=/dos/MSDOS.IMG floppy
> label hdt
> menu label Hardware ^Info
> com32 hdt.c32
> label reboot
> menu label Reboot
> com32 reboot.c32
> label poweroff
> menu label Power off
> com32 poweroff.c32
> ------------------------------------------------------------------------------------------------
> As I have commented, chainload hd1 and msdos7 do not succeed, while
> other items are good. What could be the cause?
> --
> Regards,
> Lu Wei
> _______________________________________________
> Syslinux mailing list
> Submissions to Syslinux at syslinux.org
> Unsubscribe or set options at:
> https://lists.syslinux.org/syslinux


More information about the Syslinux mailing list