Boot loader wont boot WinXp

[kapelo]

(Sorry in advance if i don't use the right terminology)

I'll get strait to the point, i have a dual boot system running Fedora14 as the main OS and WinXp as a secondary OS. On the boot up screen i choose to boot windows XP and all i get is a black screen.
i am assuming the boot-loader has a small glitch and won't boot WinXp. so i was wondering how can i fix this ?

i am stressing because i need to use MS office Access to finish a crappy school project due tomorrow.

thanks in advance

[glennzo]

In this thread I asked that 2 commands be run and the result posted in a reply. This would apply to you too. Run those commands and post the result here.

[kapelo]

Disk /dev/sda: 150.0 GB, 150039945216 bytes
255 heads, 63 sectors/track, 18241 cylinders, total 293046768 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00079c89

Device Boot Start End Blocks Id System
/dev/sda1 * 63 61432559 30716248+ 7 HPFS/NTFS
/dev/sda2 61433856 62457855 512000 83 Linux
/dev/sda3 62457856 293046271 115294208 8e Linux LVM

Disk /dev/sdb: 500.1 GB, 500107862016 bytes
255 heads, 63 sectors/track, 60801 cylinders, total 976773168 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x0718dcf2

Device Boot Start End Blocks Id System
/dev/sdb1 * 63 976768064 488384001 7 HPFS/NTFS

Disk /dev/dm-0: 53.7 GB, 53687091200 bytes
255 heads, 63 sectors/track, 6527 cylinders, total 104857600 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/dm-1: 10.5 GB, 10536091648 bytes
255 heads, 63 sectors/track, 1280 cylinders, total 20578304 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

Disk /dev/dm-2: 53.8 GB, 53821308928 bytes
255 heads, 63 sectors/track, 6543 cylinders, total 105119744 sectors
Units = sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disk identifier: 0x00000000

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

---------- Post added at 06:52 PM ---------- Previous post was at 06:49 PM ----------

su -c 'cat /boot/grub/grub.conf'
Password:
# 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,1)
# kernel /vmlinuz-version ro root=/dev/mapper/vg_andoni-lv_root
# initrd /initrd-[generic-]version.img
#boot=/dev/sda
default=0
timeout=5
splashimage=(hd0,1)/grub/splash.xpm.gz
hiddenmenu
title Fedora (2.6.35.11-83.fc14.x86_64)
root (hd0,1)
kernel /vmlinuz-2.6.35.11-83.fc14.x86_64 ro root=/dev/mapper/vg_andoni-lv_root rd_LVM_LV=vg_andoni/lv_root rd_LVM_LV=vg_andoni/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.35.11-83.fc14.x86_64.img
title Fedora (2.6.35.10-74.fc14.x86_64)
root (hd0,1)
kernel /vmlinuz-2.6.35.10-74.fc14.x86_64 ro root=/dev/mapper/vg_andoni-lv_root rd_LVM_LV=vg_andoni/lv_root rd_LVM_LV=vg_andoni/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.35.10-74.fc14.x86_64.img
title Fedora (2.6.34.7-66.fc13.x86_64)
root (hd0,1)
kernel /vmlinuz-2.6.34.7-66.fc13.x86_64 ro root=/dev/mapper/vg_andoni-lv_root rd_LVM_LV=vg_andoni/lv_root rd_LVM_LV=vg_andoni/lv_swap rd_NO_LUKS rd_NO_MD rd_NO_DM LANG=en_US.UTF-8 SYSFONT=latarcyrheb-sun16 KEYTABLE=us rhgb quiet
initrd /initramfs-2.6.34.7-66.fc13.x86_64.img
title Windows XP
rootnoverify (hd0,0)
chainloader +1

---------- Post added at 10:15 PM ---------- Previous post was at 06:52 PM ----------

please someone help. in a real jam here

[glennzo]

Is Windows on the 500GB disk? If so, change the boot loader to so it reads

title Windows XP
rootnoverify (hd1,0)
chainloader +1

Save and reboot. Select Windows and see if it boots. This may or may not work. Post back with the result please.

[kapelo]

No both OS's are on the 150GB disk

[glennzo]

Originally Posted by kapelo

No both OS's are on the 150GB disk

In that case (hd0,0) should work as it's the only Windows partition on that disk.

[kapelo]

title Windows XP
rootnoverify (hd0,0)

so if their is no problem with the boot loader settings, then what caused the black screen when selecting winxp to load?


thanks

---------- Post added at 01:30 PM ---------- Previous post was at 01:16 PM ----------

can i re-install boot loader?

---------- Post added at 01:34 PM ---------- Previous post was at 01:30 PM ----------

Should i do the following??????

3.2 Making a GRUB bootable CD-ROM

GRUB supports the no emulation mode in the El Torito specification1. This means that you can use the whole CD-ROM from GRUB and you don't have to make a floppy or hard disk image file, which can cause compatibility problems.

For booting from a CD-ROM, GRUB uses a special image called cdboot.img, which is concatenated with core.img. The core.img used for this should be built with at least the ‘iso9660’ and ‘biosdisk’ modules. Your bootable CD-ROM will usually also need to include a configuration file grub.cfg and some other GRUB modules.

To make a simple generic GRUB rescue CD, you can use the grub-mkrescue program:

$ grub-mkrescue -o grub.iso

You will often need to include other files in your image. To do this, first make a top directory for the bootable image, say, ‘iso’:

$ mkdir iso

Make a directory for GRUB:

$ mkdir -p iso/boot/grub

If desired, make the config file grub.cfg under iso/boot/grub (see Configuration), and copy any files and directories for the disc to the directory iso/.

Finally, make the image:

$ grub-mkrescue -o grub.iso iso

This produces a file named grub.iso, which then can be burned into a CD (or a DVD), or written to a USB mass storage device.

The root device will be set up appropriately on entering your grub.cfg configuration file, so you can refer to file names on the CD without needing to use an explicit device name. This makes it easier to produce rescue images that will work on both optical drives and USB mass storage devices.

[sonoran]

Check this out: http://www.supergrubdisk.org/