Can't do W2K repair on ghosted installation

  • Thread starter Thread starter Robert S
  • Start date Start date
R

Robert S

I have moved an installation of W2K from an old Athlon XP PC to a new
dual-core Intel D, with a SATA drive. Not surprisingly it now won't boot.
I've tried to do a repair installation using a W2K install disk. I get
prompted to insert an emergency repair disk (which I don't have) or "Press
L. Setup will locate Windows 2000 installation". When I do this, I get a
message that "Setup cannot find a W2K installation to repair". I know that
the files are on my hard drive because I can see them when I boot into the
recovery console - which works fine.

How can I make the setup program recognise my W2K installation?
 
Boot from the CD, and look for the bottom bar to prompt you to use F6 to
install drivers. Install the SATA drivers on your new system.
 
Don't repair it, upgrade it in-place instead. Doing a repair with the
old ERD would only try to fix the installation to suit the old hardware,
that's not what you want to do, the setup.log on the ERD wouldn't know
anything about the new hardware. See here for more information:

How to move a Windows installation to different hardware
http://support.microsoft.com/kb/249694/en-us

How to perform an in-place upgrade of Windows 2000
http://support.microsoft.com/kb/292175/

John
 
Stubby said:
Boot from the CD, and look for the bottom bar to prompt you to use F6 to
install drivers. Install the SATA drivers on your new system.
Click to expand...
When I press F6, nowhere does it mention SATA drivers, only RAID and
SCSI. I pressed F6 anyway, and I went through all the menus and it
didn't find anything for what I need.

I'm having pretty much the exact same problem as Robert. What I
noticed is that, although in device manager it says that I have "Serial
ATA" storage controller drivers installed, windows disk manager shows
that my SATA hard drives only show up to a max of 128 GB... in
actuality, they are 500+ GB. So I'm thinking I don't have the right
sata drivers... when I try and ghost a SATA hard drive (which was
taken from an IDE hard drive), I get a blue screen upon windows
boot-up. Using this same ghost image on another IDE hard drive,
Windows boots up just fine.
 
Back
Top