You only have win2k installed?
If you have a multi OS and you can access i think this all relates to how your Boot.ini file reads.
You have to be able to access c: drive and edit this file.
There is a line within that should read like this and points to the win2k system:
multi(0)disk(0)rdisk(0)par
By adding a new ide 2ndary master drive you have bumped the order up 1.
I'd suggest that the "rdisk" key has to be changed. Where it was probably 2 it now has to be 3.
If the system is win2k only and its all NTFS then i'd suggest reinstalling win2k using the recovery option.
Main Topics
Browse All Topics





by: pabgilanPosted on 2000-04-15 at 15:13:22ID: 2719556
When you add a new drive, drive letters are inserted or appened, matching an order. The order is:
Primary Master - Primary Partition
Secondary Master - Primary Partition
Primary Slave - idem
Secondary Slave - idem
Primary Master - Logical/Extended Partition(s)
Secondary Master - Logical/Extended Partition(s)
.... and so on
If you add a Secondary Master with a Primary Partition on it, and you have Win2k installed in a Extended Partition (not primary), the letter drive of your Win2k partition is "pushed up" so NTloader is unable to find the archives of Win2k (they are necessary to boot or validate an user)
This explanation is valid for IDE drives; I don't have any SCSI HD but I suppose that it's the same reason.
Suggestion: remove any primary partition on the HD you are installing. Only extended (logical) partitions, or a blank, unformatted HD if possible. You can format the disk later from Windows 2000's disk manager without having any problem.
I hope it helps