G
guferr
Hi. I have accidentally installed syslinux on a windows 7 disk, on the first partition.
It seems that, i don't know why, the sysnlinux installed on the "mbr" (the first sector) of the first partition, not the first sector of the whole disk.
Anyway: The syslinux got installed on the boot partition of windows 7, the one containing the bootmgr file.
So, i simply configured it to use chain.c32 to boot using the bootmgr, i placed the needed files to run COM32, and then i configured the syslinux.cfg with this parameters:
Code:
LABEL win7
MENU LABEL win7
COM32 chain.c32
APPEND ntldr=bootmgr
But, when booting, it says: "Err: Couldn't read the first disk sector".
So i tried specifying the disk: I started by hd0, nothing. hd 0 0, nothing. hd 0 2, nothing. But, when i chose hd0 1, it gave me the same message, but the system rebooted shortly after, and some random characters appeared on the screen, on a very, very short duration, something about 0,1 second or less before rebooting.
So, anyone know what's happening?
Just to remember: The Disk mbr is still the same, the only thing changed was the first sector (the "mbr") of the active partition, which is the first partition of the disk, the one containing the Windows 7 bootloader. The second partition is the main and biggest partition, and the third contains a backup of the system.
Ps.: I used the latest syslinux version from kernel.org, and all the files i used (chain.c32 etc) came from the same package.
Thanks!
Continue reading...
It seems that, i don't know why, the sysnlinux installed on the "mbr" (the first sector) of the first partition, not the first sector of the whole disk.
Anyway: The syslinux got installed on the boot partition of windows 7, the one containing the bootmgr file.
So, i simply configured it to use chain.c32 to boot using the bootmgr, i placed the needed files to run COM32, and then i configured the syslinux.cfg with this parameters:
Code:
LABEL win7
MENU LABEL win7
COM32 chain.c32
APPEND ntldr=bootmgr
But, when booting, it says: "Err: Couldn't read the first disk sector".
So i tried specifying the disk: I started by hd0, nothing. hd 0 0, nothing. hd 0 2, nothing. But, when i chose hd0 1, it gave me the same message, but the system rebooted shortly after, and some random characters appeared on the screen, on a very, very short duration, something about 0,1 second or less before rebooting.
So, anyone know what's happening?
Just to remember: The Disk mbr is still the same, the only thing changed was the first sector (the "mbr") of the active partition, which is the first partition of the disk, the one containing the Windows 7 bootloader. The second partition is the main and biggest partition, and the third contains a backup of the system.
Ps.: I used the latest syslinux version from kernel.org, and all the files i used (chain.c32 etc) came from the same package.
Thanks!
Continue reading...