clay36
08-12-2002, 09:24 AM
O.K. I've searched everywhere for a solution to this problem so here goes: I have a Soyo P4S Ultra mobo that uses the Highpoint 372 ATA100/RAID controller, on which I have one Western Digital 60gb HD attached (I don't intend to use a RAID array - just ATA100, which necessitates connecting the drive to the ATA100 connector on the board obviously). Linux in general has problems installing on hard drives connected the hpt372 controller apparently (Mandrake 8.2 for example won't do it and neither will the newest beta), but Highpoint has a patch that allows for custom-modified kernel installation that overcomes this problem and allows Redhat 7.0-7.3 installation (If anyone wants to take a look at the instructions and files for the Highpoint Redhat fix, please see www.highpoint-tech.com and download the driver file for Redhat 7.3).
What I want to do is dual boot between Windows 2000 and Redhat; normally this isn't a problem as long as you don't install grub or lilo to the MBR (doing this will trash the Win 2k NT loader and you have to reinstall Win 2k). The problem is this: the patch which fixes the hpt372 issue *requires* that grub/lilo be installed to the MBR - which as I said will fubar the ability to boot into Windows 2000. Does anyone know of a trick or workaround for this? In essence, I'm guessing that grub (in my case I prefer grub to lilo and that's what I would be using), needs to be fooled into thinking it's being booted from the MBR (?). Again, in order to boot Win2k successfully, you CAN NOT install the linux bootloader to the MBR (although I've come across a number of well-intentioned but misinformed posts saying otherwise)...period. I am aware of the bootsect.lnx workaround (copying it to the c:\ drive and using the NT loader to load linux instead of grub or lilo) but I haven't tried this yet since according to the instructions in the patch provided by Highpoint, the bootloader must be installed to the MBR during the Redhat installation to begin with in order for the custom kernel to work.
Any ideas or suggestions would be warmly welcomed!
:D
What I want to do is dual boot between Windows 2000 and Redhat; normally this isn't a problem as long as you don't install grub or lilo to the MBR (doing this will trash the Win 2k NT loader and you have to reinstall Win 2k). The problem is this: the patch which fixes the hpt372 issue *requires* that grub/lilo be installed to the MBR - which as I said will fubar the ability to boot into Windows 2000. Does anyone know of a trick or workaround for this? In essence, I'm guessing that grub (in my case I prefer grub to lilo and that's what I would be using), needs to be fooled into thinking it's being booted from the MBR (?). Again, in order to boot Win2k successfully, you CAN NOT install the linux bootloader to the MBR (although I've come across a number of well-intentioned but misinformed posts saying otherwise)...period. I am aware of the bootsect.lnx workaround (copying it to the c:\ drive and using the NT loader to load linux instead of grub or lilo) but I haven't tried this yet since according to the instructions in the patch provided by Highpoint, the bootloader must be installed to the MBR during the Redhat installation to begin with in order for the custom kernel to work.
Any ideas or suggestions would be warmly welcomed!
:D