[jbellone]

Okay, here's the problem.

I put RH9 on my first hard drive (already had a hard-drive with NTFS windows part. on it) and I loaded up GRUB after installing all the stuff on linux. I changed the grub config to the following:

# grub.conf generated by anaconda
#
# Note that you do not have to rerun grub after making changes to this file
# NOTICE: You have a /boot partition. This means that
# all kernel and initrd paths are relative to /boot/, eg.
# root (hd0,0)
# kernel /vmlinuz-version ro root=/dev/hda2
# initrd /initrd-version.img
#boot=/dev/hda
default=0
timeout=10
splashimage=(hd0,0)/grub/splash.xpm.gz
password --md5 $1$NbySgha1$5Qarf.k2PIbcDgmGaMTLu.
title Red Hat Linux (2.4.20-8)
root (hd0,0)
kernel /vmlinuz-2.4.20-8 ro root=LABEL=/ hdd=ide-scsi
initrd /initrd-2.4.20-8.img
title Windows 2000
rootnoverify (hd1,0)
chainloader +1

Now this is what I saw on a few websites, so I figured it would work. When I select the Windows 2000 option, it just hangs with the command words and "Booting Windows 2000" at the top.

Anyone have sugestions? I need to keep these on seperate hard-drives.

[codejockey]

I suspect the problem is becuase you have Win 2000 installed on your second drive. Windoze always wants to boot from the first drive, even if installed on another drive, so it writes boot information to the first drive. If you put grub on the drive, that may have overwritten the Windoze boot information on the first drive (in which case, you would not be able to boot into Windoze at all).

You can use grub to map your drives so that Windoze will believe it is running from the first drive. Try modifying your Windoze 2000 entry along these lines:

title Windows 2000
        map (hd0) (hd1)
        map (hd1) (hd0)
        rootnoverify (hd0,0)
        root (hd1,0)
        makeactive
        chainloader +1

You can also go the opposite route, and use NTLDR to dual-boot Linux and Windoze 2000; one set of instructions (using LILO) are at http://web.archive.org/web/200202202...inux/ntldr.php

Hope this helps.