search for: hd1_1

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:

...ormal and press [Enter]. Is there any (error) message then? Where/how exactly this fails? What exactly happens after the message(s)? Test #2: if you unplug the USB and reboot the system, can you successfully boot directly to the HDD's OS? Test #3: Add an entry to your syslinux.cfg: label hd1_1 com32 chain.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 > com3...

...angs. I can only reboot using ctrl-alt-del. > Test #2: if you unplug the USB and reboot the system, can you successfully boot > directly to the HDD's OS? > Yes. The only HDD, NTFS, WindowsXP native boot loader ntldr. > Test #3: Add an entry to your syslinux.cfg: > > label hd1_1 > com32 chain.c32 > # Boot to first partition of ... > # There is a space character before the partition number. > append hd1 1 > That will change the error message to one line "Booting..." only and still hang. Change hd1 to hd0 will loop back to syslinux menu, which is ex...

...cessful boot when using the HDD alone, as it used to be. Maybe this is also the intention of your answer, but I would like to be sure we are both referring to the same thing / scenario / case. So, can you (still)? > > Test #3: Add an entry to your syslinux.cfg: > > > > label hd1_1 > > com32 chain.c32 > > # Boot to first partition of ... > > # There is a space character before the partition number. > > append hd1 1 > > > That will change the error message to one line "Booting..." only and > still hang. Change hd1 to hd0 will loop...