Help with Grub - Lost Windows Boot Loader..?!

[INFAMOUSNEEK]

Someone on here will know how to fix this.. I have tried a few different HD settings but can't get it working...

I just installed Fedora 11 (I installed over the Fedora 10 installation I had already installed)..

-Before I would have Grub give the choice of Fedora 10 or Windows (Where Windows would load the Win Boot loader for my options of Windows 7 and Windows Vista)

-NOW: I have the same options.. But when i select Windows (It loads the Recovery partition) instead of the Windows Boot Loader...

Here is my fdisk -l

Device Boot Start End Blocks Id System
/dev/sda1 1 192 1536000 27 Unknown
Partition 1 does not end on cylinder boundary.
/dev/sda2 192 5414 41943040 7 HPFS/NTFS
Partition 2 does not end on cylinder boundary.
/dev/sda3 5414 38914 269089792 f W95 Ext'd (LBA)
Partition 3 does not end on cylinder boundary.
/dev/sda5 5414 10513 40960000 7 HPFS/NTFS
/dev/sda6 10513 29635 153600000 7 HPFS/NTFS
/dev/sda7 * 29635 29661 204799+ 83 Linux
/dev/sda8 29661 38914 74321919+ 8e Linux LVM

Here is my current grub.conf which is booting into windows recovery

#boot=/dev/sda
default=0
splashimage=(hd0,6)/grub/splash.xpm.gz
hiddenmenu
title Fedora 11
root (hd0,6)
kernel /vmlinuz-2.6.29.4-167.fc11.i686.PAE ro root=/dev/mapper/vg_infamousmobile-lv_root rhgb quiet vga=792
initrd /initrd-2.6.29.4-167.fc11.i686.PAE.img
title Windows 7/Vista
rootnoverify (hd0,0)
chainloader (hd0,0)+1


Any help would be greatly appreciated! Thanks

[INFAMOUSNEEK]

Fixed my own problem guys! Finally got it right..

#boot=/dev/sda
default=0
splashimage=(hd0,6)/grub/splash.xpm.gz
hiddenmenu
title Fedora 11
root (hd0,6)
kernel /vmlinuz-2.6.29.4-167.fc11.i686.PAE ro root=/dev/mapper/vg_infamousmobile-lv_root rhgb quiet vga=792
initrd /initrd-2.6.29.4-167.fc11.i686.PAE.img
title Windows 7/Vista
rootnoverify (hd0,1)
chainloader (hd0,1)+1

[stoat]

Originally Posted by INFAMOUSNEEK

title Windows 7/Vista
rootnoverify (hd0,1)
chainloader (hd0,1)+1

Hello INFAMOUSNEEK,

Nice job. But here's something that might interest you at this point. Entering the drive and partition twice is redundant. Here are two more acceptable examples of GRUB menu command syntax for your situation...

title Windows 7/Vista
rootnoverify (hd0,1)
chainloader +1

title Windows 7/Vista
chainloader (hd0,1)+1

The rootnoverify command is used to set the current root device without attempting to mount the partition. It is used when the target partition is one that GRUB cannot mount (such as that Windows NTFS partition). The chainloader command used with that "+1" makes GRUB load and execute the first sector of the current root partition. If the root partition has already been established with the rootnoverify command, it's not necessary to repeat the partition in the chainloader command line. Lastly, I would predict that entering the drive and partition in the chainloader command would make it ignore the currently set root partition should they not be the same. Either way. Or your way. Just FYI.

[INFAMOUSNEEK]

Thanks for the info! I appreciate information like that! I will be sure to modify that.. as I too like things done as cleanly as possible!