search for: msdos7

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

On 2019-4-10 1:20, Ady Ady via Syslinux wrote: >>>> #This item fails >>>> label dos >>>> menu label MS-^DOS 7.1 >>>> com32 chain.c32 msdos7=io.sys >> >> IO.SYS and COMMAND.COM are copied from a Windows98 system on another >> computer, which is MSDOS7.1; and BOOTSECT.W98 is from Bootpart tool (I >> compared it with the one from my Windows98 system, and I think they are >> basically the same except label nam...

..."good" file, dos7 can boot normally (before syslinux). After comparison I found it was cut short, missing some padding zeros. That file behaved well until failed under this specific situation, which is odd. But after syslinux, that good IO.sys still cannot make "com32 chain.c32 boot msdos7=io.sys" work. MSDOS booting through syslinux also solved: it turns out the boot sector file should be from the original, not the one I copied from another system or by bootpart tool. I saved a dos.bs file when the usb-hd could boot to DOS, then after running syslinux, "boot dos.bs"...

> On 2019-4-11 13:29, Lu Wei wrote: > > On 2019-4-10 1:20, Ady Ady via Syslinux wrote: > >>>>> #This item fails > >>>>> label dos > >>>>> menu label MS-^DOS 7.1 > >>>>> com32 chain.c32 msdos7=io.sys > >>> > >>> IO.SYS and COMMAND.COM are copied from a Windows98 system on another > >>> computer, which is MSDOS7.1; and BOOTSECT.W98 is from Bootpart tool (I > >>> compared it with the one from my Windows98 system, and I think they are > &gt...

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

On 2019-4-11 13:29, Lu Wei wrote: > On 2019-4-10 1:20, Ady Ady via Syslinux wrote: >>>>> #This item fails >>>>> label dos >>>>> menu label MS-^DOS 7.1 >>>>> com32 chain.c32 msdos7=io.sys >>> >>> IO.SYS and COMMAND.COM are copied from a Windows98 system on another >>> computer, which is MSDOS7.1; and BOOTSECT.W98 is from Bootpart tool (I >>> compared it with the one from my Windows98 system, and I think they are >>> basically the s...

...dos" file(s) too. These are the "MSDOS 7.1" >> boot files. The ones you got before _might_ be the "Win98" variants instead. >> > > I don't have access to that Win98 system now, yet I can recall two files > io.sys and command.com are sufficient for MSDOS7.1 booting; Bootsect.dos > is the only ".dos" file (which I later renamed to bootsect.W98). That > system installed WinXP after Win98, that's I think why there was this > bootsect.dos file, because a line > C:\bootsect.dos="Windows 98" > in boot.ini will boot t...

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

...DOWS="Microsoft Windows XP Professional" /noexecute=optin /fastdetect and it can successfully boot the fixed hard disk. But I think "com32 chain.c32 hd1" should be more direct. >> #This item fails >> label dos >> menu label MS-^DOS 7.1 >> com32 chain.c32 msdos7=io.sys > > > Where exactly the files needed to boot MSDOS 7.1 are located? > > Do you have the module file "ls.c32" in the USB? If you have it, you could: > > 1_ From the Syslinux boot menu, press [Esc] in order to get to the boot prompt. > > 2_ At the bo...

....c32 # Boot to first partition of ... # There is a space character before the partition number. append hd1 1 > > 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 Where exactly the files needed to boot MSDOS 7.1 are located? Do you have the module file "ls.c32" in the USB? If you have it, you could: 1_ From the Syslinux boot menu, press [Esc] in order to get to the boot prompt. 2_ At the boot prompt, type in "ls.c32" and pre...

...me additional "*.dos" file(s) too. These are the "MSDOS 7.1" > boot files. The ones you got before _might_ be the "Win98" variants instead. > I don't have access to that Win98 system now, yet I can recall two files io.sys and command.com are sufficient for MSDOS7.1 booting; Bootsect.dos is the only ".dos" file (which I later renamed to bootsect.W98). That system installed WinXP after Win98, that's I think why there was this bootsect.dos file, because a line C:\bootsect.dos="Windows 98" in boot.ini will boot to Win98. > Once copie...

...ppend hd1 1 swap If that fails too, try: label hd1_swap com32 chain.c32 # Boot to first partition of ... # There is a space character after the disk number. append hd1 swap > >> #This item fails > >> label dos > >> menu label MS-^DOS 7.1 > >> com32 chain.c32 msdos7=io.sys > > > > > > Where exactly the files needed to boot MSDOS 7.1 are located? > > > > Do you have the module file "ls.c32" in the USB? If you have it, you could: > > > > 1_ From the Syslinux boot menu, press [Esc] in order to get to the b...

This patch introduces extra functionality to chain.c, mainly with reference to BPB adjustments, but not only that. It expects 3 small patches I sent earlier (they are included for easy reference, patches 1-3/4). The changes introduced are: 1) file and boot sector use separate options to control load address and jump address (if applicable). Options are as described below: *

This is a bit updated set of chain.c32 changes that simplifies a few things (and in partiter part), fixes few minor issues and adds a few new features. Details are in the following commits, below is the summary and pull details at the end. Shao - any chance to peek over them ? Most of those are relatively simple changes and well tested, though of course something might have slipped my attention.