search for: bootpart

...: >>>> #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 name, so I use this one), but I think if >> io.sys is loaded, boot sector should be of no use. I have tried "boot >> BOOTSECT.W98" and "bss BO...

...is 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" works. ("bss dos.bs" works too; "com32 chain.c32 boot file=dos.bs" works with a warning about mapping; "com32 chain.c32 boot msdos7=dos.bs" do not work.)...

...tdetect.com, BOOT.INI are ntldr files (which can chain-boot successfuly); mtldr is for booting to MiniPE(which is actually grldr from Grub4dos and can chain-boot successfuly). 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 name, so I use this one), but I think if io.sys is loaded, boot sector should be of no use. I have tried "boot BOOTSECT.W98" and "bss BOOTSECT.W98" without success, so...

...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 name, so I use this one), but I think if >>> io.sys is loaded, boot sector should be of no use. I have tried "boot >>> BOOTSECT.W98"...

Hi all : my /dev/sda2 is ext3 format filesystem, the os moblin is installed in /dev/sda2 which is root partition, the bootloader is grub, now i want to change the bootloader to extlinux, but i came across some trouble, so i did some steps as following: 1. rpm -ivh syslinux-extlinux*.rpm 2. extlinux -i /boot/extlinux 3. i edit extlinux.conf , and put it in /boot/extlinux/, there is

...ntldr files (which can chain-boot > successfuly); mtldr is for booting to MiniPE(which is actually grldr > from Grub4dos and can chain-boot successfuly). > > 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 name, so I use this one), but I think if > io.sys is loaded, boot sector should be of no use. I have tried "boot > BOOTSECT.W98" and "bss BOOTSECT.W98"...

On at 2019-04-12 11:28 +0800, Lu Wei via Syslinux wrote: >> Regarding the MSDOS 7.1 boot files... Do you still have access to that Win98 >> system? If you do, I would suggest searching for "io.dos" and "msdos.dos". >> These might be set as "hidden" and/or "system" (use attrib if needed), and >> there might be some additional

...gt;> 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 name, so I use this one), but I think if > >>> io.sys is loaded, boot sector should be of no use. I have tried "boot > >>>...

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:

Hi all, I have just released syslinux-3.70-pre25. Unless someone has something big and scary that either I have managed to miss or was just stumbled over, I'm going to release 3.70 final some time between tomorrow and Monday. Thus, *please holler now* if there are any stop-ship problems still known... -hpa