Re: Unable to boot on WinXP after Fedora Core 2 test3 install

[Gerry Tool <gstool earthlink net>]

Phil Schaffner wrote:
> On Thu, 2004-05-13 at 14:36, shrek-m gmx de wrote:
>
> > Kenneth Benson wrote:
> >
> >
> > > if /dev/hda1 is your XP then it looks like grub over-wrote the boot 
> > > code for the XP partition, since that is where it's booting from and 
> > > grub is in the boot partition.
> >
> > afair
> > hd0,0 = hda1
> > hd0,1 = hda2
> >
> >
> > > >    Device Boot      Start         End      Blocks   Id  System
> > > > /dev/hda1   *           1       26550    13381168+   7  HPFS/NTFS
> > > > /dev/hda2           26551       26753      102312   83  Linux
> > > > /dev/hda3           26754       37785     5560128   83  Linux
> > > > /dev/hda4           37786       38760      491400    f  W95
> > > > Ext'd (LBA)
> > > > /dev/hda5           37786       38760      491368+  82  Linux swap
> > >
> > > > splashimage=(hd0,1)/grub/splash.xpm.gz
> > > > title Fedora Core (2.6.5-1.327)
> > > >      root (hd0,1)
> > > >      kernel /vmlinuz-2.6.5-1.327 ro root=LABEL=/ rhgb quiet
> > > >      initrd /initrd-2.6.5-1.327.img
> > > > title WindowsXP
> > > >      rootnoverify (hd0,0)
> > > >      chainloader +1
> >
> > afair
> > winxp has problems with pqmagic5 created partitions,
> > i could not find the article
> > http://search.microsoft.com/search/results.aspx?view=en-us&st=b&na=82&qu=partition+magic
> >
> > could it be that since fc2tx something has changed the partition in a 
> > simliar way?
> >
> >
> > what had you tried?
> > http://www.redhat.com/archives/fedora-test-list/2004-April/msg00138.html
> >
> > bios-setting from auto to lba ?
> > boot win-xp-cd in rescue-mode ?
> > c:\> fixmbr
> >
> >
> >
> > --
> > shrek-m
>
>
> Looks a lot like
> http://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=116653
>
> Please post if you get this working - have been following this issue as
> I'd like to put FC2 on my IBM A21p notebook that currently runs FC1 and
> XP, but have been leery due to numerous reports of FC2/XP dual boot
> problems.  The above bug is still open, and some earlier threads
> suggested the above work-arounds, but there did not seem to be a
> reported successful resolution in some cases.
>
> Phil
I concur.  This happened to me twice with different FC installs and also 
once with a Suse install, even though I chose to have grub install on 
the boot record of the drive containing the new install rather than on 
the mbr.  Somehow those installs screw up the mbr anyway.  Each time 
after much searching for a solution, I resorted to starting over with a 
Windows reinstall.  Fortunately I had a separate partition on which I 
keep all my windows data files, so I didn't have to lose them.  I 
finally put windows on the first partition of a second harddrive running 
on a second "raid" controller.  To use it, I just select SCSI from a 
BIOS menu during boot to use windows and have grub installed on the hda 
mbr for everything else (several Linux distros.)  Since then I've done a 
number of linux installs on the harddrive that is connected as master on 
the first standard IDE controller (hda) with no problems.

Gerry