You're pretty close to understanding a bit more
🙂
rootnoverify (hd0.0)
chainloader +1
This tells you that the disk has boot up to Grub and is attempting to run NTLDR (loading a boot loader from another boot loaded, a 'chain').
Fixmbr does the same as
fdisk /mbr in that it re-write the Master Boot Record. In other words it will clear the Grub bootloader and return you to the Win2k default one (actually it recovers the MBR from a saved copy). If you're happy enough to reboot a Linux distro. & re-instate Grub, then fine.
IMO it is the lack of a 'target' for Grub (NTLDR) that is the issue. Hence, trying to run
fixboot. I presume that you ran Win2k from the CD - choosing the recovery option also re-writes the MBR (if I remember rightly).
I'm in Mint at the mo' so can't double check but there's another command to scan Win partitions for an OS and add it into boot.ini (mental blank:-(). I suspect that isn't the problem, however.
Various NTLDR versions are available online, including for win2k (match the service pack, to be certain).
Another member here (that uses Win2k) might be able to tell you which files are needed in the 'root' directory.
Right-clicking on the w2k partition should have a mount option.
Or...
In a Terminal and assuming Win2k is using NTFS and that it is in the 1st primary partition (normally is):
sudo mkdir /media/win2000
sudo mount -t ntfs-3g /dev/sda1 /media/win2000
That should mount the partition and allow you to browse.
EJ

Just skimming the surface
Opinions/guidance expressed are intended to benefit the reader (mostly) but no responsibility should be assumed for the accuracy and no warranty is implied/expressed or given - so eBay may pull this post
Demised responsibility