Hello, heres the issue.
I have a gateway laptop with Vista 64 previously installed with 2 partitions: C and D and an "invisible" 10gb recovery partition. I installed Fedora 12 without issue, but now when grub loads it gives me 2 options: Fedora and Other.
Instead of "Other" going to Windows it now goes to the Gateway recovery tool. Which i believe resides on that 10gb "invisible" partition.

I dont think this will be a hard fix. Im sure its just a file i need to edit. Just not sure where to find it, kinda new and such. Any help that can be given i will greatly appreciate.

Hi,

Please paste the output of the command "fdisk -l", if you are not logged in as root but have sudo you may have to do "sudo /sbin/fdisk -l" instead. With this if you could then also output the the content of "/boot/grub/menu.lst" or "/boot/grub/grub.conf". We should be able to tell you what to change, I suspect if you are right then you may have done an update to Fedora that updated a driver that allowed it to see that partition, if this is the case then it might be just a case of changing the reference of hd(0,0) to hd(0,1) but let's see the output first before messing around with boot scripts .

[root@Gateway Dan]# fdisk -l

Disk /dev/sda: 200.0 GB, 200049647616 bytes
255 heads, 63 sectors/track, 24321 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xbfa4073f

Device Boot Start End Blocks Id System
/dev/sda1 1 1306 10485760 27 Unknown
/dev/sda2 * 1306 12832 92579840 7 HPFS/NTFS
/dev/sda3 12832 21569 70185026+ 7 HPFS/NTFS
/dev/sda4 21570 24321 22105440 5 Extended
/dev/sda5 21570 21595 204800 83 Linux
/dev/sda6 21595 24321 21900287+ 8e Linux LVM

Disk /dev/dm-0: 16.1 GB, 16114515968 bytes
255 heads, 63 sectors/track, 1959 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-0 doesn't contain a valid partition table

Disk /dev/dm-1: 6308 MB, 6308233216 bytes
255 heads, 63 sectors/track, 766 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0x00000000

Disk /dev/dm-1 doesn't contain a valid partition table

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,4)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_gateway-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,4)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.31.5-127.fc12.x86_64)
root (hd0,4)
kernel /vmlinuz-2.6.31.5-127.fc12.x86_64 ro root=/dev/mapper/vg_gateway-lv_root LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYBOARDTYPE=pc KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.31.5-127.fc12.x86_64.img
title Other
rootnoverify (hd0,0)
chainloader +1

And with your help i fixed it :-D .

From grub.conf .....

title Other
rootnoverify (hd0,0)

changed too

title Other
rootnoverify (hd0,1)

And now instead of booting into the recovery console it boots into windows.

Maybe change the title to something meaningful while you're at it.
Personally I prefer to see the menu, so comment out the hiddenmenu line - add "#" at start of the line.

Probably as I guessed a driver update that caused it to be able to see a partition that was previously not viewable under the previous driver for the Hard Drive controller. Only curious thing if this is the case is why it didn't break your linux installation as well. But everything seems to be working for now so it should be fine. It might be fedora fixed it's own configuration at the same time of compiling the driver into the kernel.

I would say I agree with this, I myself do this just for normal installations but I go further with my hosted server where I work to make things a bit more obvious.

A typical kernel line would be like the following (please note this is from the domain-0 of a xen server)
title CentOS (2.6.18-164.11.1.el5xen)

I change this on my server to
title CentOS, Kernel: 2.6.18-164.11.1.el5xen (current)

on top of this I label previous Kernels as (old) and none Xen Kernels as (do not use) as Xen was installed post installation since the usage of the server changed and I did not reinstall it I still get none Xen Kernels but if Xen did develop a problem I still have the back-up of a none-xen kernel to fix things from, however these won't bring up my Virtual Machines so I label these as (do not use).