I can't find a solution to fixing the MBR in the above post. So I decided to simply use my production drive (risky but I simply will take care not to write to the MBR)
So here is what I discovered:
I took the win2k-ntfs drive, changed the jumper and made it the slave (hd1) and took the linux drive and made it the master (hd0).
Then I booted from the GRUB floppy (once i find a solution I'll create a grub.conf) and typed the following at the grub> prompt:
map (hd1) (hd0)
map (hd0) (hd1)
And I got win2k to boot (well sort of). It booted but it seemed a little slow while booting and then it stopped short of displaying the screen where you press "ctrl-alt-del" to enter your password. All that I had was the mouse cursor and a desktop colored screen and nothing else. Pressing "ctrl-alt-del" didn't do anything either. I simply had to turn off my computer.
Alright so here are a few thoughts: on the internet i saw people use root (hd0,0) in place of my rootnoverify (hd1,0) above. First, I can't get it to work without the noverify (which makes sense) and second i need to use (hd1,0) instead of (hd0,0) because when i go to boot it totally hangs w/o getting as far as what I described above. But using (hd1,0) rather than (hd0,0) does not make sense to me because I've mapped the drives around the drives by using the map command.
Jeez this whole dual boot thing is really turning into a pain.
Why is it not possible for me to completely boot win2k-ntfs when it is physically hd1 by using the above commands at the grub> prompt?