Re: install windows xp after redhat
From: Kevin (kevin28_at_yahoo.com)
Date: 01/07/04
- Next message: Geoff: "3Com Etherlink III (3C509B) won't work"
- Previous message: Carl: "Re: Loki Heretic II in RH9"
- In reply to: Kevin: "Re: install windows xp after redhat"
- Next in thread: news: "Re: install windows xp after redhat"
- Reply: news: "Re: install windows xp after redhat"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: 7 Jan 2004 12:14:35 -0800
kevin28@yahoo.com (Kevin) wrote in message news:<17d88c5a.0401070646.4f069c64@posting.google.com>...
> "news" <news@giganews.com> wrote in message news:<YtSdnXjjftQM42aiRVn-ig@comcast.com>...
> > "Marko Nurmenniemi" <no.way@kolumbus.fi> wrote in message
> > news:btf1bb$2i8$1@phys-news1.kolumbus.fi...
> > > Kevin wrote:
> > >
> > > > Respectively, I know things haven't changed. I've done enough Linux
> > > > installs that I can do them with my eyes closed. But I hate to have
> > > > to go through the entire install process again just to install XP.
> > > > And if there is a shortcut that someone may have discovered I would
> > > > like to know what it is and how to execute it.
> > > >
> > > > I know that lilo writes to mbr but I'm not using lilo but grub.
> > > > That's why I mentioned it. The OS installs are on separate hard
> > > > drives. So when I install XP this won't touch my RH install on the
> > > > other hard drive. I'm thinking there might be a way to configure the
> > > > grub menu.lst file to see the XP partition so I can boot from it.
> > > > Possible?
> > >
> > > Problem is that MS does not want to consider that it might not be alone
> > > in the MBR. So it just writes it the way it likes. Linux will play it
> > > nice and allow other's to share the playground.
> > >
> > > Linux re-install is not needed. Just boot from the rescue CD or floppy
> > > and fix the MBR. Trouble is that the Linux made MBR is not the correct
> > > anymore since you did not have the XP installed when Linux was
> > > installed. but this should not be a big problem. you just need to add to
> > > grub.conf the partition which contains XP to configure another boot
> > > option for the Windows.
> > >
> > > go googling my brother or if feeling a bit lazy...
> > >
> > > http://www.sorgonet.com/linux/grubrestore/
> > >
> >
> > Good stuff Marko, thanks. Here's another querky question. I hope you can
> > help me figure this out. Since the Windows and RH installs are on different
> > disk. RH being the first disk I want connected to the controller. So
> > (hd0,0) works for RH to boot. But how will I figure out the partition number
> > for Windows on the daisy-chained hard drive? I think I made 4 or 5
> > partitions for RH ( / , /tmp , /usr , /var , /home ). I'll double check to
> > be sure. So, to set Windows up in grub do I add something like (hd0,6)?
> > During a google search I learned that I still have to trick Windows that it
> > is on the first partition. So the grub setting would look something like
> > this.
> >
> > title Windows
> > map (hd0,0) (hd0,5)
> > map (hd0,5) (hd0,0)
> > rootnoverify (hd0,5)
> > chainloader +
>
>
> On second thought, do I need to do the map thing since I already have
> Windows installed on the second drive. I checked my linux drive. I
> made 4 partitions mapped as:
>
> /dev/hda1 = /
> /dev/hda2 = /tmp
> /dev/hda3 = /var
> /dev/hda4 = linux extended
> /dev/hda5 = /usr
>
> If I daisy chain the Windows drive as a slave to the linux drive would
> not linux see the drive as:
>
> /dev/hda6 = windows extended
> /dev/hda7 = FAT
>
> Then I could just edit my grub config file an add the following:
>
> title Windows
> rootnoverify (hd0,7)
> chainloader +
>
> Might not this work?
After more Googling this afternoon. I believe I found the answer
which I will test out tonight.
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
makeactive
or
title Windows
map (hd0) (hd1)
map (hd1) (hd0)
rootnoverify (hd1,0)
chainloaddr +1
In all the posts I've read, the users who used either one of the above
confirmed a working dual boot process. Where Windows is located on
the second hard drive. The last resort alternative (which does work)
is to switch boot location from the BIOS). To messy.
- Next message: Geoff: "3Com Etherlink III (3C509B) won't work"
- Previous message: Carl: "Re: Loki Heretic II in RH9"
- In reply to: Kevin: "Re: install windows xp after redhat"
- Next in thread: news: "Re: install windows xp after redhat"
- Reply: news: "Re: install windows xp after redhat"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|