search for: msdos710

...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 LABEL MSDOS710 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. -Adan On Thu, Apr 4, 2019 at 8:43 AM Lu Wei via Syslinux <syslinux at syslinux.org> wrote: &g...

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:

...LOCAL > timeout 80 > prompt 0 > noescape 1 > > MENU TITLE UTILITY BOOT MENU > > MENU INCLUDE defaults.cfg > MENU INCLUDE slackware64.cfg > MENU INCLUDE pmagic.cfg > MENU INCLUDE kali.cfg > MENU INCLUDE SYS407.cfg > MENU INCLUDE dell-esxi-5.5.cfg > MENU INCLUDE msdos710.cfg > > > MENU INCLUDE slax.cfg > MENU INCLUDE liveslak.cfg > MENU INCLUDE xcp-ng.cfg > MENU INCLUDE xenserver.cfg > MENU INCLUDE sysresc.cfg > MENU INCLUDE pfSense.cfg > MENU INCLUDE vmware.cfg > MENU INCLUDE hdd.cfg > MENU INCLUDE hddiag.cfg > MENU INCLUDE memo...

...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 > > LABEL MSDOS710 > 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. > > -Adan > > On Thu, Apr 4, 2019 at 8:43 AM Lu Wei via Sysl...