Dualbooting

[shocka04]

I'm trying to dualboot xp and fc5 and i partitioned the drive and installed fc5 and its running fine, now im trying to figure out how to get xp to run, i was goin to change the grub settings but when i opened them, it looked like everything was already set up but when i restarted, fc5 started, this is what my grub settings look like:
# 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/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,4)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.15-1.2054_FC5smp)
root (hd0,4)
kernel /vmlinuz-2.6.15-1.2054_FC5smp ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5smp.img
title Other
rootnoverify (hd0,1)
chainloader +1

I figured the "Other" would be for the xp and i ran fdisk too so anyone could help see what is wrong
Device Boot Start End Blocks Id System
/dev/sda1 1 8 64228+ de Dell Utility
/dev/sda2 * 9 16506 132520185 7 HPFS/NTFS
/dev/sda3 19057 19452 3180870 db CP/M / CTOS / ...
/dev/sda4 16507 19056 20482875 5 Extended
/dev/sda5 16507 16519 104391 83 Linux
/dev/sda6 16520 19056 20378421 8e Linux LVM

could someone please help me out here, im tryin to run xp so i can get some of my files

[bob]

It sure looks correct as is. Yes, 'Other' is XP and you should have a short window to make changes when the boot sequence starts. You'd hit any key except 'enter' and then be given the option to boot into your Fedora kernel or into Other. What is the error that you're getting when the grub menu comes up or does it skip the grub menu and just go straight into FC?

[shocka04]

no menu comes up, it just loads straight to fc

[bob]

It shouldn't do that, of course. Maybe the timeout is just too quick for you to catch it? Well you could start hitting the 'down arrow' just after the bios screen starts up and see if it kicks in the menu or you can modify the 'timeout' as described below:

So, let's change the 'timeout' to something larger which should delay things and maybe let you in. Open a terminal, sign in as 'su -', give your password and then type:

gedit /boot/grub/grub.conf

When the grub.conf window opens, change the timeout to something larger - maybe 20. Then, save, close and exit the terminal.

Reboot and see if there's a delay and if you now see the boot menu.

BTW, the kernel you're using is older and has been replaced. You might want to also try a 'yum update' to get the latest kernel. In the olden days (FC4), the new kernel would be added to the older ones and you'd certainly have a boot menu that way, but I've noticed that with FC5, the new kernel tends to replace and remove the older one. In my case, the original kernel was still retained, so that's another option. Maybe it will keep one older kernel and create an addition to the grub menu that way.
Edit: Just checked another thread and it looks like the system DOES hang onto the older kernel, so that might be the way to go!

[bob]

One other thing to try - change

title Other
rootnoverify (hd0,1)
chainloader +1

to:

title Other
rootnoverify (hd0,1)
makeactive
chainloader +1