"Transplant" a hard disk...?

  • Thread starter Thread starter Kenneth
  • Start date Start date
K

Kenneth

Howdy,

My main Win2000 Pro system has died (don't ask...) Its hard drive is
perfect.

I have a new system on order.

I know that if I simply move the hard disk from the old system to the
new one I will have trouble because the hardware is different.

Is it possible to use something like SYSPREP to allow me to do the
"transplant?"

If so, my life would be much simpler.

Thanks for any help on this,
 
Sysprep's "raison d'etre" is to regenerate GUIDs in order to distribute an
OS deployment. It'll do nothing to replace a hardware abstraction layer. The
/pnp switch provided with sysprep won't change a HAL either.

Try repairing the W2K installation once you receive the new system. The
repair procedure does verify and change the HAL.
 
Sysprep's "raison d'etre" is to regenerate GUIDs in order to distribute an
OS deployment. It'll do nothing to replace a hardware abstraction layer. The
/pnp switch provided with sysprep won't change a HAL either.

Try repairing the W2K installation once you receive the new system. The
repair procedure does verify and change the HAL.
Click to expand...

Howdy,

I sincerely appreciate your response, but will need a bit more
detail...

Would this be the procedure you suggest?:

1: Put the old disk in the new system and make it active.

2: Boot the new system (with the old disk and old W2K OS.

3: Run a Windows repair to let the OS find the "new hardware" etc.

If that is correct, how do I do #3? I have read the helpfile but it is
not clear to me which of the techniques will replace the HAL.

Also, is all this a Mickey Mouse approach, or is it a reasonable
method given that I simply want to put my old (complete) system on the
new box?

Very sincere thanks,
 
249694 How to Move a Windows 2000 Installation to Different Hardware

http://support.microsoft.com/?id=249694

292175 How to Perform an In-Place Upgrade of Windows 2000

http://support.microsoft.com/?id=292175

306952 What an In-Place Windows 2000 Upgrade Changes and What It Does Not
Change

http://support.microsoft.com/?id=306952

238359 Differences Between Manual and Fast Repair in Windows

http://support.microsoft.com/?id=238359


--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.
 
249694 How to Move a Windows 2000 Installation to Different Hardware

http://support.microsoft.com/?id=249694

292175 How to Perform an In-Place Upgrade of Windows 2000

http://support.microsoft.com/?id=292175

306952 What an In-Place Windows 2000 Upgrade Changes and What It Does Not
Change

http://support.microsoft.com/?id=306952

238359 Differences Between Manual and Fast Repair in Windows

http://support.microsoft.com/?id=238359


--
Click to expand...

Hi Daniel,

I certainly thank you for your suggestions.

I've read all the articles, but am a bit perplexed:

The article: "What an In-Place Windows 2000 Upgrade Changes and What
It Does Not" says that the upgrade "refreshes the registry" and sets
it to "default values."

That makes sense, but later, it says that the Upgrade does NOT change
installed programs.

I assume that I am interpreting something incorrectly, but installed
software certainly modifies registry values.

Can you untangle that for me?

Also, of these procedures, what would you suggest I do if I want to
use the old Win2K hard disk in the new system. I know that I can
istall the drive and (I assume I can) boot from it, but at that point
the (old) registry will not be "seeing" the new hardware.

Thanks again for your help,



Change
 
249694 How to Move a Windows 2000 Installation to Different Hardware

http://support.microsoft.com/?id=249694

292175 How to Perform an In-Place Upgrade of Windows 2000

http://support.microsoft.com/?id=292175

306952 What an In-Place Windows 2000 Upgrade Changes and What It Does Not
Change

http://support.microsoft.com/?id=306952

238359 Differences Between Manual and Fast Repair in Windows

http://support.microsoft.com/?id=238359


--
Click to expand...

Hi Daniel,

I thank you for your suggestions, and read them with care.

I do have questions though...

The article "What an In-Place Windows 2000 Upgrade Changes and What It
Does Not" says that the upgrade "refreshes the registry" and sets it
to "default values." That would seem to make sense, but later it says
that it does NOT change "instlled programs."

I must be misinterpreting something, but any installed software
modifies the registry, so if the upgrade sets registry values to the
default, does that not have an effect on the installed software?

Beyond that, none of these articles seem to apply to my situation
(again, if I am interpreting things correctly.)

I suppose that I could install the old disk in the new box, and then
instead of booting from the disk, boot from the Windows CD to do the
upgrade. Is that the approach you were suggesting?

Sincere thanks once again,
Kenneth


Change
 
If you're moving to new hardware, (different HAL, different
mass-storage-device-controller, etc.); obviously flattening the machine,
reformatting and reinstallation is the cleanest.

If your new mass-storage-controller requires drivers, make sure you loaded
them on your old system before moving the hard drive (otherwise you'll
probably bluescreen stop 7b). An upgrade "in-place" will refresh certain
core OS registry entries and roll back all service packs/hotfixes (the
servicepack and hotfix files are overwritten with the originals from the
CD). It shouldn't touch on registry entries created by 3rd party software.
This is why applications will continue working after the upgrade "in-place."
Make sure you follow the steps of the "in-place" upgrade closely -- that is,
enter for "new installation", F8 to acknowledge the EULA, select the
installation you wish to "upgrade."

Cheers,
Daniel

--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.
 
Hi Daniel,

Please see my comments inline below...


If you're moving to new hardware, (different HAL, different
mass-storage-device-controller, etc.); obviously flattening the machine,
reformatting and reinstallation is the cleanest.

If your new mass-storage-controller requires drivers, make sure you loaded
them on your old system before moving the hard drive (otherwise you'll
probably bluescreen stop 7b).
Click to expand...


Well sir, that may be the dealbreaker... I neglected to say tha the
old box is dead. It is not possible for me to load the MSC drivers
before putting the old disk in the new box.

But what if I put the old disk in the new box, but did not try to boot
off the disk. Instead, I would boot off the Win CD. If I did that, and
ran a repair, or upgrade, might I get things to work?

An upgrade "in-place" will refresh certain
core OS registry entries and roll back all service packs/hotfixes (the
servicepack and hotfix files are overwritten with the originals from the
CD). It shouldn't touch on registry entries created by 3rd party software.
This is why applications will continue working after the upgrade "in-place."
Make sure you follow the steps of the "in-place" upgrade closely -- that is,
enter for "new installation", F8 to acknowledge the EULA, select the
installation you wish to "upgrade."
Click to expand...

Part of your comments above leave me confused. If I put the old disk
in the new box, the disk will have Win2K on it. It would seem that I
would not want to select "new installation", but I might be missing
something. Can you clarify?

Sincere thanks as before,
Kenneth
 
Dear Kenneth:

I did it a year ago, it works:

1) In another PC backup your hardisk using Ghost. Or better, Ghost
your old disk to the one that comes in your new PC, which normally
will be bigger.

2) Mount the harddisk in the new hardware as a primary disk

3) Don't boot from the harddisk, but boot from the Win2k CD instead.

4) Choose install Win2k *over* the old installation. Don't choose
"repair" or to install Win2k in another subdirectory.

If you selected the menus correctly, you will have what you want. My
actual harddisk comes from three generations of older Thinkpads. Step
1 is very important if you type the wrong choice in the menus, but
they are easy to catch.

Kenneth said:
Howdy,

My main Win2000 Pro system has died (don't ask...) Its hard drive is
perfect.

I have a new system on order.

I know that if I simply move the hard disk from the old system to the
new one I will have trouble because the hardware is different.

Is it possible to use something like SYSPREP to allow me to do the
"transplant?"

If so, my life would be much simpler.

Thanks for any help on this,
Click to expand...

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Email: (e-mail address removed)
Note: Please forgive me for my bad English, I am trying to improve it!
 
Dear Kenneth:

I did it a year ago, it works:

1) In another PC backup your hardisk using Ghost. Or better, Ghost
your old disk to the one that comes in your new PC, which normally
will be bigger.

2) Mount the harddisk in the new hardware as a primary disk

3) Don't boot from the harddisk, but boot from the Win2k CD instead.

4) Choose install Win2k *over* the old installation. Don't choose
"repair" or to install Win2k in another subdirectory.

If you selected the menus correctly, you will have what you want. My
actual harddisk comes from three generations of older Thinkpads. Step
1 is very important if you type the wrong choice in the menus, but
they are easy to catch.



Thanks
Juan I. Cahis
Santiago de Chile (South America)
Email: (e-mail address removed)
Note: Please forgive me for my bad English, I am trying to improve it!
Click to expand...

Hi Juan,

First, your English is wonderful and I thank you for writing!

Next, your note makes me feel more optimistic.

I already have an image on a third machine. (Not Ghost by the way, but
a product called v2i Protector from Powerquest, the folks who make
Drive Image. It has the ability to make incremental images. It works
extremely well.)

The new disk and the old are the same size.

I intend to remove the new disk from the new system, install the old
disk in its place, boot from the Win2K CD, and then install Windows
"over" the old system.

We shall see if it does what I need, and I sincerely thank you,

Kenneth
 
Dear Kenneth, that is exactly you need to do. Is remember that I found
the correct menu choice at the second or third level, but not on the
"repair" tree, but on the "install" one.

After the process is done, you will need to reboot a couple of times,
and to install the machine specific drivers of the new machine, if
they are very sophisticated.

After that, go, in the new machine, to "Control Panel" => "System" =>
"hardware" and look for the extra new drivers you need to manually
install.

Kenneth said:
Hi Juan,

First, your English is wonderful and I thank you for writing!

Next, your note makes me feel more optimistic.

I already have an image on a third machine. (Not Ghost by the way, but
a product called v2i Protector from Powerquest, the folks who make
Drive Image. It has the ability to make incremental images. It works
extremely well.)

The new disk and the old are the same size.

I intend to remove the new disk from the new system, install the old
disk in its place, boot from the Win2K CD, and then install Windows
"over" the old system.

We shall see if it does what I need, and I sincerely thank you,

Kenneth
Click to expand...

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Email: (e-mail address removed)
Note: Please forgive me for my bad English, I am trying to improve it!
 
Dear Kenneth, I found exactly the tree:

Boot win2kCD => "Install" (*not* "repair") => The installer checks the
hardisk => "Repair the installation found in XXXXX" (not "Install a
new copy", that will install win2k in other partition or
subdirectory).

I am translating from Spanish, so you could have some differences in
the menu titles, but this is the idea. A suggestion to Microsoft: The
correct choice above should have been labeled "Reinstall the
installation found in XXXXX"!!!!!

Juan I. Cahis said:
Dear Kenneth, that is exactly you need to do. Is remember that I found
the correct menu choice at the second or third level, but not on the
"repair" tree, but on the "install" one.

After the process is done, you will need to reboot a couple of times,
and to install the machine specific drivers of the new machine, if
they are very sophisticated.

After that, go, in the new machine, to "Control Panel" => "System" =>
"hardware" and look for the extra new drivers you need to manually
install.



Thanks
Juan I. Cahis
Santiago de Chile (South America)
Email: (e-mail address removed)
Note: Please forgive me for my bad English, I am trying to improve it!
Click to expand...

Thanks
Juan I. Cahis
Santiago de Chile (South America)
Email: (e-mail address removed)
Note: Please forgive me for my bad English, I am trying to improve it!
 
Howdy,

My main Win2000 Pro system has died (don't ask...) Its hard drive is
perfect.

I have a new system on order.

I know that if I simply move the hard disk from the old system to the
new one I will have trouble because the hardware is different.
Click to expand...

This should work: Install the old HD in the new system (you may remove
the new HD if desired, or leave it in place). Power on the new system
and enter the BIOS and do whatever setup you need to do, make sure it
recognizes your HD and IDs it correctly.

Then allow the system to boot but you MUST hit F8 at the proper time
and boot into safe mode.

Now open the device manager and delete all the hardware that's
different such as Video card, CDs, USB devices (if they're not the
same), NICs, etc. Then restart and allow the computer to reboot
normally, it should find and install all the new hardware and all your
software should be intact.

NOTE: IF there is some kind of IDE or RAID driver that needs to be
installed during the initial setup of Win2k, the above very likely
won't work.
 
An "in-place upgrade" is the procedure you are describing, Juan.

--
--
Daniel Chang
Server Setup Team

Search our Knowledge Base at http://support.microsoft.com/directory
Visit the Windows 2000 Homepage at
http://www.microsoft.com/windows2000/default.asp
See the Windows NT Homepage at http://www.microsoft.com/ntserver/

NOTE: Please reply to the newsgroup and not directly to me. This allows
others to add to and benefit from these threads and also helps to ensure a
more timely response. Thank you!
This posting is provided "AS IS" without warranty either expressed or
implied, including, but not limited to, the implied warranties of
merchantability or fitness for a particular purpose.
The views and opinions expressed in this newsgroup posting are mine and do
not necessarily express or reflect the views and / or opinions of Microsoft.
 
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;Q249694


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
 
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;Q249694


Bruce Chambers
Click to expand...
Hi Bruce,

The two systems are significantly different... so the in-place upgrade
is the way I will go.

I thank you for the links and will hope for the best!
 
Back
Top