I did something similar. I have two drives: one with Win2k, and one with Linux. I installed Linux while the Windows drive was disconnected. My drives are IDE, but I don't think that will matter; they're just drives from the BIOS perspective. Here's the juicy part of my grub.conf:
title LFS 6.0-7b
kernel /lfskernel-184.108.40.206-7b root=/dev/hdb2
title Windows 2000
map (hd0) (hd1)
map (hd1) (hd0)
Ok, first, I removed the makeactive. Why? Because makeactive actually marks the partition bootable. In my BIOS, that meant my Windows drive would become the default boot drive in the system on the next boot. In other words, I would lose access to grub, because the system would go look at Windows' boot sector first, see it's marked as bootable, and use it (instead of seeing grub on the other drive).
Now, the mapping business... I'd read that Windows requires that it boot from the "first drive in the system" or something along those lines. To my understanding, the map commands "lie" to Windows, convincing its bootloader that it is the first drive. I don't know how it does it (maybe temporarily affecting BIOS information). Anyway, I had seen the same thing you are: the system displays the commands in the grub entry and just sits there. Adding the map commands fixed the problem.
Also note, that the rootnoverify is set up based on the pre-remap. The mapping commands don't affect the drive designations within grub.