Dual Boot Problem

[Taae]

The installation for fedora went fine whi ch i was surpized of because i am a complete newbie to linux, i decided to keep windows xp on a seprate partition for the rest of the family to use. The only problem is is when the boot screen comes up i click other but it takes me to emachines sytem recovery for windows xp instead of windows xp. I'v tried recovering xp but the same thing comes up. I have a separte partition to hold data for a xp system recovery so i'm thinking maybe when i click other its loading the wrong partition. Any help would be great but remember to use simply words, otherwise i will not have a clue what your talking about :D

Disk /dev/hda: 160.0 GB, 160041885696 bytes
255 heads, 63 sectors/track, 19457 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes

Device Boot Start End Blocks Id System
/dev/hda1 * 419 13199 102663382+ 7 HPFS/NTFS
/dev/hda2 1 418 3357553+ b W95 FAT32
/dev/hda3 13200 13212 104422+ 83 Linux
/dev/hda4 13213 19457 50162962+ 5 Extended
/dev/hda5 13213 19457 50162931 8e Linux LVM

Partition table entries are not in disk order

[Taae]

Sorry to keep bugging you but i'm desperate to be able to access windows xp again :D Can anyone help me?

[daverj]

show us your grub.conf

[Taae]

Not sure if this is what you meant?:

# 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,2)
# kernel /vmlinuz-version ro root=/dev/VolGroup00/LogVol00
# initrd /initrd-version.img
#boot=/dev/hda
default=2
timeout=5
splashimage=(hd0,2)/grub/splash.xpm.gz
hiddenmenu
title Fedora Core (2.6.16-1.2080_FC5)
root (hd0,2)
kernel /vmlinuz-2.6.16-1.2080_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.16-1.2080_FC5.img
title Fedora Core (2.6.15-1.2054_FC5)
root (hd0,2)
kernel /vmlinuz-2.6.15-1.2054_FC5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
initrd /initrd-2.6.15-1.2054_FC5.img
title Other
rootnoverify (hd0,1)
chainloader +1

[daverj]

as you can see by the fdisk output, the bootable windows partition is /dev/hda1. In grub, this corresponds to (hd0,0). Therefore you need to make the following change:

rootnoverify (hd0,1)

to

rootnoverify (hd0,0)


This will fix it.

Dave

[BanditRider]

Try changing:

rootnoverify (hd0,1)

to

rootnoverify (hd0,0)



EDIT: I took a phone call while replying and your post beat mine... :)

[Taae]

Thanks you so much!!! It works great now ;)

[daverj]

Ok, BanditRider, to be fair and equitable, the next time an issue like this crops up, I will hold off for say, an hour, so that you can beat me to it. ;)

Dave

[BanditRider]

;) Sounds fair to me. :D

I wouldn't have posted had I seen yours first.

Hey, it fixed his problem!!!