This is a discussion on GRUB and Windows XP within the Linux Operating System forums, part of the Unix Operating Systems category; --> Hi! I have Red Hat 8 and a few days ago I was using Windows 2000 just fine using ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi! I have Red Hat 8 and a few days ago I was using Windows 2000 just fine using GRUB as the boot manager. But suddenly ntldr was missing. I tried fixmbr and fixboot from the Win2000 recovery console but no chance. Of course, fixmbr has written the original boot manager from Win2000 and so GRUB was out of the MBR. So I booted from the Red Hat CD into a rescue console and used grub-install /dev/hda1 in order to rewrite GRUB into the MBR. On /dev/hda1 Windows is installed. /dev/hdb is the Linux harddisk. GRUB now works, but if I try to boot Windows 2000 the screen flashes and again the GRUB menu is there. At least I expectated that ntldr would be missing. Now I can't get access to /dev/hda1 (NTFS) from Linux, either. But this is not the real problem because Windows 2000 was getting a little bit slow, etc. So now I want to format C: (/dev/hda1) and install Windows XP on /dev/hda2 (D left. C: is then used for something else. After the Windows XP install I will get the Windows XP boot manager so that I can't boot Linux any longer. To fix this I thought I could use /sbin/grub-install. But now I am afraid that grub-install will damage the MBR again, so that I can't boot Windows XP and therefore only Linux (just like it's now). So my questions: If I am going to install Windows XP to /dev/hda2, will the MBR of WinXP still be on /dev/hda1? What is the proper use of grub-install? I think that there has occured a problem using "grub-install /dev/hda1" and maybe it damaged this partition. I know it must work because the Red Hat setup wrote GRUB properly and made the config file so that I was able to boot Linux AND Windows without touching anything. Thanks! -- Regards, André |
| ||||
| André Heßling wrote: > Hi! > > I have Red Hat 8 and a few days ago I was using Windows 2000 just fine > using GRUB as the boot manager. But suddenly ntldr was missing. > I tried fixmbr and fixboot from the Win2000 recovery console but no > chance. Of course, fixmbr has written the original boot manager from > Win2000 and so GRUB was out of the MBR. > So I booted from the Red Hat CD into a rescue console and used > grub-install /dev/hda1 in order to rewrite GRUB into the MBR. > On /dev/hda1 Windows is installed. > /dev/hdb is the Linux harddisk. > GRUB now works, but if I try to boot Windows 2000 the screen flashes and > again the GRUB menu is there. At least I expectated that ntldr would be > missing. Now I can't get access to /dev/hda1 (NTFS) from Linux, either. > > But this is not the real problem because Windows 2000 was getting a > little bit slow, etc. So now I want to format C: (/dev/hda1) and > install Windows XP on /dev/hda2 (D > left. C: is then used for something else. > > After the Windows XP install I will get the Windows XP boot manager so > that I can't boot Linux any longer. To fix this I thought I could use > /sbin/grub-install. > But now I am afraid that grub-install will damage the MBR again, so that > I can't boot Windows XP and therefore only Linux (just like it's now). > > So my questions: > If I am going to install Windows XP to /dev/hda2, will the MBR of WinXP > still be on /dev/hda1? > What is the proper use of grub-install? I think that there has occured a > problem using "grub-install /dev/hda1" and maybe it damaged this > partition. > I know it must work because the Red Hat setup wrote GRUB properly and > made the config file so that I was able to boot Linux AND Windows > without touching anything. > > Thanks! I tried something similar, but the damn thing insisted to be on the first drive. M$ wants you to use their solutions, not anybody elses... But I strongly recommend you to read the Texinfo manual for GRUB ((p)info grub), pay attention to the *map* command found in the index part. The map command is great for making Windows believe that it's installed onto the first drive by "switching the drives", even if it's not. Say on the 2nd, as it was for my setup with an 40 GB running XP for test reasons... worked beyond my expectations Dont't worry, you will work it out. |