This is listed as a bug. Since FC2 test 1. I've had this happen 3 or 4 times with the different test releases and now the release. I ended up having to get the low level formatter utility from Samsung and zero the MBR, re-partition and start over. This may not have been the only solution, just the one I used. There is talk in the bug that you may be able to change your BIOS settings to LBA instead of AUTO (if that is what it's set to), and be able to boot again. I did not read the whole thread in depth. It's huge. This has been an issue for all kinds of folks. I've done 6 installs in the past 2 days and only 2 have gone without partition errors. Check bugzilla for information. Bug number is 115980. Good Luck, Paul Crabb >>I have a computer with an athlon xp 2400, gigabyte motherboard, and more >>importantly 2 western digital 80gb drives (ide). I had Windows XP on a >>fat32 partition on the first drive. I used partitionmagic to create the >>linux partitions the way i wanted them. When I installed Fedora Core 2 >>and used grub as the boot loader windows xp would no longer boot. After >>installing partition magic would not read the master boot record and i >>could only get to my data through a dos boot disk. Fedora would run >>fine. Why did Fedora destroy the windows xp boot loader (fedora core 1 >>would allow me to use grub to boot windows xp) and why wont partition >>magic read my partitions?
