FC2 test 1 dual boot

[Mike Lurk]

Has anyone else had this problem. I installed FC2 test 1 on a dual boot
system. Windows xp was installed first and then fc2 creating the
partitions manually, /boot, /swap, and /. This was done on a 40 gig hard
drive, giving 20gig to windows and the rest for fc2. I had a second hard
drive with all my important stuff on a 10gig hard drive which I mount
after booting to fc2. When I try to boot to Windows I get;

Other
        rootnoverify (hd0,0)
        chainloader +1

on the screen and thats it. When I check the partitions with linux fdisk
it all looks normal;

  Device Boot      Start         End      Blocks   Id  System
/dev/hda1   *           1       40641    20482843+   c  W95 FAT32 (LBA)
/dev/hda2           40642       40844      102312   83  Linux
/dev/hda3           40845       77332    18389952   83  Linux
/dev/hda4           77333       77536      102816    f  W95 Ext'd (LBA)
/dev/hda5           77333       77535      102280+  82  Linux swap

but then when i try dos's fdisk i get

1. non dos partition
2. non dos partition
3. extended partition
4. fat32

and this is in my grub.conf

# 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/hda3
#          initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,1)/grub/splash.xpm.gz
title Fedora Core (2.6.1-1.65)
        root (hd0,1)
        kernel /vmlinuz-2.6.1-1.65 ro root=LABEL=/ rhgb
        initrd /initrd-2.6.1-1.65.img
title Other
        rootnoverify (hd0,0)
        chainloader +1

I see a problem here with the differences in linux's version of fdisk
and dos's, the way in which the partitions are setup. I've tried
installing the dual boot 3 times and all 3 times it's been the same
outcome.

I filed a bug report in Bugzilla and it is bug 115980

I just thought of something..... it couldn't make a difference...it
shouldn't... jumper settings on the hard drives set to cable
select??????

Checking this out.......later

Mike