Help!-Reinstalling a used hard drive...

  • Thread starter Thread starter TD
  • Start date Start date
T

TD

If a hard drive (Western Dig 60 or 80GB, 7200rpm, with WinXP or 2000) that
was in a previous machine (AMD proc) for a short while and then taken out,
was later installed in a completely different machine (Pentium proc), would
it fail to boot? If so, would it be possible to correct the problem, and
from within that 2nd machine, not knowing the specs of the first machine?

The big question: How?

Thanks for any help on this...

TD
 
JAD said:
It may or may not boot.... repair install of XP after a boot from XP CD


TD:
As JAD points out, the transferred drive *may* boot in the destination
machine even though the components in both machines are completely
different. It's something of a crap-shoot. Sometimes you're lucky, sometimes
you're not. It's worth a try.

Assuming it doesn't boot, you'll have to perform a Repair install as JAD
mentions. I assume from your query that you're unfamiliar with this process.
It's not terribly difficult - roughly similar to fresh-installing XP. There
are a number of web sites that contain detailed info on this process. Just
do a Google search for "XP repair install".
Anna
 
Thanks Anna-- would a 'repair install' involve losing all data already
existing on the drive from installation in the previous machine?
And you're correct- I *am* unfamiliar with it, (like many things in my
life, lol!). But never afraid to try...

TD
 
JAD said:
It may or may not boot.... repair install of XP after a boot from XP CD
Thanks for the quick reply, JAD. Would I be unable to access previous data
while booting from the XP CD?
 
I recently had a similar problem, specifically with a WD drive. It turns out
WD drives are really picky about the master-slave jumper settings. If the
drive came from a two drive system and was the master or slave it is
important to remove the jumper in a single drive system. If the jumper is
set to master in a single drive system, the BIOS will see the drive fine,
but the system will not boot.

Also note if the user on the computer where the drive was originally
installed chose to "make files private" in the My Documents folder you may
not be able to get them back.

Dan
 
access in what way? What will happen is XP will keep your software and
settings (for the most part) in tact and will setup the system to work with
the chipset and features of the new board.
 
Thanks Anna-- would a 'repair install' involve losing all data already
existing on the drive from installation in the previous machine?
And you're correct- I *am* unfamiliar with it, (like many things in my
life, lol!). But never afraid to try...

http://www.webtree.ca/windowsxp/repair_xp.htm
and your data will be intact :P



--
Free Windows/PC help,
http://www.geocities.com/sheppola/trouble.html
remove obvious to reply
email (e-mail address removed)
Free original songs to download and,"BURN" :O)
http://www.soundclick.com/bands/8/nomessiahsmusic.htm
 
It would NOT successfully boot in a different machine with a different
motherboard, and devices.
 
TD said:
If a hard drive (Western Dig 60 or 80GB, 7200rpm, with WinXP or 2000) that
was in a previous machine (AMD proc) for a short while and then taken out,
was later installed in a completely different machine (Pentium proc), would
it fail to boot? If so, would it be possible to correct the problem, and
from within that 2nd machine, not knowing the specs of the first machine?

The big question: How?

Thanks for any help on this...

TD

Even if it booted you couldn't be sure it was configured properly. Do a
repair install. Note, this is not the first set of options you get when
booting the XP CD. I.E. not 'repair console' or trying to repair from a
repair disk. Say no to that screen and go on as if doing a fresh install.

At that point it will find an existing XP installation and ask if you want
to repair it (or do a fresh install over it). Chose yes to repair.

It looks like a fresh install but will save the existing settings.

After the repair the system will be reset to the service pack level of the
CD, since that's what you're installing from, so if you had later service
packs installed you'll need to redo them, as well as Internet Explorer
service packs and/or updates.

If your XP CD is an original issue and you had SP1 or SP2 installed later
you'll get a lot of 'installer' messages telling you it's trying to
reinstall things. Ignore them and cancel. It's trying to 'fix' the fact
that the service pack files are no longer installed, which it can't, of
course. Simply reinstall the service packs and the installer problems with
automagically vanish as the missing files will no longer be missing and,
so, not need 'fixing'.

It's a good idea to download the 'for IT Professionals' full version of the
service pack files before hand so if there is a problem accessing the
internet after the initial repair, and before the service pack files are
redone, that you have the service packs already there and handy.

http://www.microsoft.com/downloads/...BE-3B8E-4F30-8245-9E368D3CDB5A&displaylang=en
 
AND don't forget to tell the original poster that you will have to reinstall
quite a few of the programs because it replaces ALL the registry entries.
Also emails & watched items in newsgroups.
All your program entries in your program list will be gone. (you can save
the folder & replace it later)
Some programs will need re registering.
Be warned.
I have done it but never again. You are better off if you have the ability
to slave it & back up or save everything possible & do a new install.
 
BruceM said:
AND don't forget to tell the original poster that you will have to reinstall
quite a few of the programs because it replaces ALL the registry entries.
Also emails & watched items in newsgroups.
All your program entries in your program list will be gone. (you can save
the folder & replace it later)
Some programs will need re registering.

I didn't tell him those things because they are not true. Not a one.
Be warned.
I have done it but never again.

You may 'think' you did it but you apparently did the wrong thing because
none of the 'problems' you listed happen with a repair re-install, if done
properly.
You are better off if you have the ability
to slave it & back up or save everything possible & do a new install.

That will, of course, ensure the things you listed happen.
 
BruceM said:
AND don't forget to tell the original poster that you will have to
reinstall quite a few of the programs because it replaces ALL the registry
entries.
Also emails & watched items in newsgroups.
All your program entries in your program list will be gone. (you can save
the folder & replace it later)
Some programs will need re registering.
Be warned.
I have done it but never again. You are better off if you have the ability
to slave it & back up or save everything possible & do a new install.

I have done many in place repair installs and have never had registry
changes for any programs. The only program I have problems at all with is
Outlook and I always follow a repair of XP with a repair of Office XP and
that takes a couple of minutes and fixes the Outlook problem. I use Outlook
as my mail and news handler and my wife uses Outlook Express for mail and
news and after an XP repair the Outlook newsreader combines with Outlook
Express as default (which is normal since it IS Outlook Express actually). A
repair of Office XP separates the two and I don't retrieve her mail
everytime I open Outlook newsreader. The whole idea of the repair option is
to save all those settings in the registry so you don't have to reinstall
programs. Outside of the above little glitch I have never had any other
problems doing a repair install.

Ed
 
BruceM said:
AND don't forget to tell the original poster that you will have to reinstall
quite a few of the programs because it replaces ALL the registry entries.
Also emails & watched items in newsgroups.
All your program entries in your program list will be gone. (you can save
the folder & replace it later)
Some programs will need re registering.
Be warned.
I have done it but never again. You are better off if you have the ability
to slave it & back up or save everything possible & do a new install.

But to do that, Bruce, wouldn't it have to be able to be booted in the 2nd
machine?
 
Good to hear. Thanks for the detailed responses, David. My concern was not
losing previously created document and/or image files. I can't remember
exactly what was on the drive, but I'm pretty sure there are at least a few
things I'd like to save. So, that's really the core of my question-- besides
the programs, will any existing files remain after a repair install?
 
Well, what I mean is, open up any previously created files. Will any of
those remain after a repair install?

Thanks for your help, JAD.
 
Here is "TD's" original posting...
"If a hard drive (Western Dig 60 or 80GB, 7200rpm, with WinXP or 2000) that
was in a previous machine (AMD proc) for a short while and then taken out,
was later installed in a completely different machine (Pentium proc), would
it fail to boot? If so, would it be possible to correct the problem, and
from within that 2nd machine, not knowing the specs of the first machine?


The big question: How?"

Later, he added...

"Thanks for the detailed responses, David. My concern was not
losing previously created document and/or image files. I can't remember
exactly what was on the drive, but I'm pretty sure there are at least a few
things I'd like to save. So, that's really the core of my question-- besides
the programs, will any existing files remain after a repair install?"

Then came the following...

TD said:
Well, what I mean is, open up any previously created files. Will any of
those remain after a repair install?

Thanks for your help, JAD.



data while booting from the XP CD?


TD:
We'll assume that the HD you're planning to transfer to another machine
(both machines in an XP environment) boots properly in its present machine,
is free of any system files corruption, and contains no malware that might
cause you future problems. In other words, the drive is a nice clean one
without any problems that you're aware of. Is that a reasonable assumption?

If it is...
First, before you do anything, copy whatever critical files you need from
that drive before you begin the transfer process. That's just a sensible
precaution to take in case anything goes wrong in the future, right?

After doing this, install that drive in your destination machine. There's a
fairly strong possibility that the drive will boot even if the components in
the two machines are completely different. As I informed you previously,
it's something of a crap-shoot. If you're lucky, it will boot. If it does,
then, of course, you may have to install whatever drivers XP doesn't pick
up. But you will *not* have to undertake a Repair install in this situation.
I have transferred scores of HDs from one machine to another that initially
booted. I have never encountered a *single* instance of any subsequent
problem with the drive that could be traced to the fact that a Repair
install was not undertaken under those circumstances. This, of course
assumes that the transferred drive was "clean", as I mentioned in my opening
paragraph. It (nearly) goes without saying that if you transfer garbage,
garbage is what you'll get, right?

There is, however, a strong likelihood that the transferred drive will *not*
initially boot in the destination machine. In that case, as you've been
informed, a Repair install will be necessary. And I think you've been
referred to a number of web sites that contain detailed information on
undertaking a Repair install. Not a difficult process at all.

Again, as I believe you have been informed, all the data on the transferred
drive will be intact following the Repair installation. After all, that's
the purpose of this process in transferring a HD to another machine. But, as
I and others have informed you, there's always a chance things can go wrong.
So make sure you have backup copies of any critical data before undertaking
the Repair install.
Anna
 
TD said:
Good to hear. Thanks for the detailed responses, David. My concern was not
losing previously created document and/or image files. I can't remember
exactly what was on the drive, but I'm pretty sure there are at least a few
things I'd like to save. So, that's really the core of my question-- besides
the programs, will any existing files remain after a repair install?

Yes, existing data files will remain. However, as with any major
manipulation of the disk it's a good idea to backup important data before
the operation.
 
End of last summer and into fall I had a board with failing capacitors that
gave me one large set of file corruptions after another every few weeks...
pointing to all sorts of mysterious issues that did not exist (real hair
puller that suggests you may not ever want to own a K7S5A). I ended up doing
5 or 7 repair installs and standing upgrades and never had a single issue
with programs that did not work and I've got a *lot* of programs of many
many varieties and ages.

I would get the Service Pack disk, though, as I had to go all the way back
to my original release version every time. Some minor customizations with
some appearances were lost but they were insignificant.

Not being an expert, though, I guess anything is possible.
 
Back
Top