Oh, no. Sorry for the confusion.
- My master disk only has a single partition, but it is
designated drive D: when in Windows.
- My Slave disk is recognized as drive C: (also with a
single partition).
Basically, what happened was I previously ran Win98 on
drive C:. In order to play certain games, I needed to use
Win2k, so I installed Win2k on my slave drive at the
time. I eventually decided to stick with Win2k completely
and set the Win2k drive to the master and than Win98 drive
to the slave. Even in doing so, the previous drive
letters remained the same.
So, now I've ghosted my Win2k drive onto a new, larger
drive. It, like the drive it was ghosted from, is also
set to Master and has a single partition.
You can't have two Masters on the same controller channel (primary and
secondary). If the two drives were on different controller channels, then
both can be Masters (should be, in fact, if you also have CDROM or DVD drives
attached), but BIOS will start the boot process from the first bootable
partition on Drive 0. It will boot whatever is on that partition - an OS
(Win98, W2K, Linux, etc etc etc) or a boot manager (which is a micro-OS that
presents you with a choice, and then directs BIOS to load and boot the OS you
select.)
Looks to me like you've got two OS's but no boot manager. BIOS doesn't know
whether to boot W2K-Original or W2K-Ghost. You should prepare your computer
to Move Windows 2000 to New Hardware. Ghosting doesn't work with W2K, because
W2K keeps a very detailed list of all the hardware it deals with, and the
ghosted W2K has a list that doesn't jive with what is sees (itself on a HD of
the wrong size, for one.)
So, first you have to get rid the ghosted W2K on D:. Switch the HDs back to
master and slave as originally configured. The machine should then boot into
the original W2K, and you can repartition or reformat D:. I would create two
partitions on D:, and use E: to store whatever data you don't want to lose -
copy or move files and folders from the C: drive to E:. NB: You will have to
reinstall pretty well all the programs that are now on C:, so make sure you
have either their installation disks, or the zips or self-extracting install
files that you downloaded (you did keep copies of all that stuff, didn't
you?). Simply copying program folders onto E:, and then copying them onto the
new W2K partition, will almost certainly not work.
Now you will have: C: with W2K; D: formatted but empty; E: formatted and
containing data. Shut Down the computer.
Now you are ready to "Move Windows 2000 to New Hardware". The following posts
will help you do this.
Good luck! If all else fails, you can Install W2K onto the larger HD, and
reformat the smaller one (I would keep it as a data backup drive.)
..........................................................................
MOVING W2K TO NEW HARDWARE - several relevant posts
-------------------------------------------------------
From: "Bruce Chambers" <
[email protected]>
Newsgroups: microsoft.public.win2000.hardware
Subject: Re: New Computer, but W2K refuses to run
Date: Fri, 20 Jun 2003 18:43:17 -0600
Greetings --
Normally, unless the new motherboard is virtually identical to the old one
(same chipset, IDE controllers, etc), you'll most likely need to perform a
repair (a.k.a. in-place upgrade) installation, at the very least (and don't
forget to reinstall any service packs and subsequent hot fixes):
How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175
What an In-Place Win2K Upgrade Changes and What It Doesn't
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q306952
If that fails:
How to Move a Windows 2000 Installation to Different
Hardware
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q249694&ID=KB;EN-US;Q2
49694
Bruce Chambers
Help us help you:
----
You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
................................................
From: "James Barr" <
[email protected]>
Subject: Re: Replaced Motherboard
Date: Wed, 28 Aug 2002 20:20:26 +0100
I had the same problem once and did the following which sorted it out:
Create an NT boot disk (format a disk on a 2000 machine [either pro or
server] copy to that disk the following files
boot.ini
ntdetect.com
ntldr
)
then edit the boot.ini and make sure the arc paths are correct for your
system then delete the /fastdetect switch.
Then boot from the floppy disk. Once you've booted once from the floppy it
should be OK to boot from the Hard Disk
Hope this helps
James
.....................................
From: "Bruce Chambers" <
[email protected]>
Subject: Re: changing motherboards and CPU's
Date: Wed, 22 Jan 2003 19:53:20 -0700
Greetings --
Unless the new motherboard is virtually identical to the old one (same
chipset, IDE controllers, etc), you'll most likely need to perform a repair
(a.k.a. in-place upgrade) installation, at the very least (and don't forget
to reinstall any service packs and subsequent hot fixes):
How to Perform an In-Place Upgrade of Windows 2000
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q292175
Bruce Chambers
Microsoft MVP - Shell/User
----
You can have peace. Or you can have freedom. Don't ever count on
having both at once. -- RAH
........................................
[Source of following lost - sorry.]
Boot using your Windows CD
Go to the Repair Console and run the following options.
chkdsk c:
fixboot c:
fixmbr c:
See if they resolve the issue. Sometimes Windows 2000 disks aren't totally
pleased with being popped onto a new board as such.
