cloned drive

  • Thread starter Thread starter shakey
  • Start date Start date
S

shakey

I just installed a larger drive and cloned old drive to it using their, WD,
supplied software.
Made the new drive the boot drive "C". All is fine but I have had two
programs that required reregistering so far causing me to wonder if any
XP-sp3 settings may have gotten changed that I should be aware of.
SG
 
shakey said this on 1/27/2009 8:19 PM:
I just installed a larger drive and cloned old drive to it using their, WD,
supplied software.
Made the new drive the boot drive "C". All is fine but I have had two
programs that required reregistering so far causing me to wonder if any
XP-sp3 settings may have gotten changed that I should be aware of.
SG
Click to expand...
I wrote an application that was built around a very complex licensing
process that was meant to prevent you from moving the app to another
drive or PC. It checked all sorts of hardware changes. It could see a
new hard drive, even reformatting the same drive.
You don't say what apps so its hard to respond with more detail but if I
can do it I'm sure other vendors can exceed my abilities and do even
worse. So it does not surprise me. But that's just my 2 cents.
 
Most cloning/mirroring software doesnt work with xp,xp has too many
built in security settings,the software usually works fine with older windows
OS..XP has clone software built into it,XCOPY..To clone a IDE HD,set the new
hd as slave to C: on the same IDE cable.Once in xp,format the hd with default
settings,once thru,go to run,type: XCOPY C:\*.* D:\ /c/h/e/k/r Agree to
all in
the DOS window.Also,D: being the new hd,if asigned a diffrent letter,then use
that letter instead.
 
shakey said:
I just installed a larger drive and cloned old drive to it using
their, WD, supplied software.
Made the new drive the boot drive "C". All is fine but I have had two
programs that required reregistering so far causing me to wonder if
any XP-sp3 settings may have gotten changed that I should be aware of.
SG
Click to expand...

This happened to me as well when I upgraded to a larger HD,this was several
months ago and other than having to reregister a few products all is well. I
would bet that Big _Al is correct. No worries as long as you have your
product keys.
 
"Most cloning/mirroring software doesnt work with xp..."

From personal experience I can assure you that Norton Ghost, Acronis
True Image, BootIt NG and ShadowProtect Desktop work very nicely with
Windows XP.

"XP has clone software built into it,XCOPY..."

Not correct. XCOPY does not copy metadata. However, XCOPY can be very
useful for file and folder backup.
 
Leonard Grey said:
A clone is an exact duplicate.
Click to expand...

Yes, but there's a important catch in this situation.

The drive contains an exact clone of the *contents* of the previous one.

The drive likely does *not* have the same serial numbers or model
descriptors as the previous drive, and this can kick over a licensing check
made by specialised software.

Yes, the files on the drive are the same, but some may be for verifying
other information on hardware around the system, so that you can't move it
easily.

So. license software may have been influenced. I don't think that XP uses
anything near this level of check.

HTH
-pk
 
Andrew E. said:
Most cloning/mirroring software doesnt work with xp,xp has too many
built in security settings,
Click to expand...

This is, frankly, bullshit. It has no basis in reality.
the software usually works fine with older windows
OS..XP has clone software built into it,XCOPY
Click to expand...

No, it does not. You can copy some files, but it sure is not a clone and
will not boot.

...To clone a IDE HD,set the new
hd as slave to C: on the same IDE cable.Once in xp,format the hd with
default
settings,once thru,go to run,type: XCOPY C:\*.* D:\ /c/h/e/k/r Agree to
all in
the DOS window.Also,D: being the new hd,if asigned a diffrent letter,then
use
that letter instead.
Click to expand...

This, on the other hand, is guaranteed to NOT produce a bootable disk.

-pk
 
Andrew E. said:
Most cloning/mirroring software doesnt work with xp,xp has too many
built in security settings,the software usually works fine with older windows
OS..XP has clone software built into it,XCOPY..To clone a IDE HD,set the new
hd as slave to C: on the same IDE cable.Once in xp,format the hd with default
settings,once thru,go to run,type: XCOPY C:\*.* D:\ /c/h/e/k/r Agree to
all in
the DOS window.Also,D: being the new hd,if asigned a diffrent letter,then use
that letter instead.
Click to expand...

Disregard this fool. The posts from the fool are not only damned
impossible to read, they're chocked full of error.
 
Quite to the contrary, most cloning software *does* work with Windows XP
but Xcopy absolutely *cannot* clone a booted Windows XP installation.

Let's try a simple little test, it is perfectly safe and so easy to try
that even you, Andrew, should be able to do it.

At a Command prompt issue the following commands, pressing enter after each:

md c:\tempo
xcopy %systemroot%\system32\config c:\tempo /h/e/k/r

So, what happens when you try the above Xcopy command? A pesky little
detail, isn't it? Of course being that you have a sharp eye you will
have noticed that I removed one of your Xcopy switches in my little
example, your way around the pesky error is to add the /c switch to the
command. The /c switch instructs Xcopy to ignore errors, forget about
files causing errors and move on to the next file and keep on copying.
Maybe a good switch to use when backing up user files on a network and
not wanting the whole backup to fail just because one of your users
somewhere on the network has an open file, not such a good switch to use
if you want to "clone" a drive! So now try the test with your set of
switches:

xcopy %systemroot%\system32\config c:\tempo /c/h/e/k/r

So, your command completed and everything looks fine, doesn't it? Now,
go look at the results of your efforts, take a look at the contents of
the C:\tempo folder and compare it to the original
Windows\system32\config folder. The Config folder holds the Windows
registry, your Xcopy cloning method completely fails to copy the most
important set of files to the new drive, a clone made with your Xcopy
method will fail to boot. Xcopy cannot clone a booted Windows NT type
installation so stop posting this nonsense of yours.

John
 
Most cloning/mirroring software doesnt work
with xp,xp
has too many
built in security settings,the software usually
works
fine with older windows OS..XP has clone
software built
into it,XCOPY..To clone a IDE HD,set the new hd
as slave
to C: on the same IDE cable.Once in xp,format
the hd with
default settings,once thru,go to run,type: XCOPY
C:\*.*
D:\ /c/h/e/k/r Agree to all in
the DOS window.Also,D: being the new hd,if
asigned a
diffrent letter,then use that letter instead.
Click to expand...

xcopy cannot clone a system drive; it cannot copy
files "in use" and can not use the Volume Shadow
Services for such a copy.
Neither can XXCopy, BTW.

Twayne
 
Thank you ALL for your input. I now feel better about possible changes that
I was concerned about in XP, I do not now think there were any based on
others experience. IE: security settings, restore, ect, +++++ too many to
check out. INFO: Avast was one of those that did not work after clone.
Interesting also that some very knowable posters from past gave simple but
misleading answers.
SG
 
In regard to the below post which many have helpfully replied to:
Today I tried to make a manual restore point and received the message
"system restore is unable to create a restore point. please restart the
computer, and then run system restore again."
Restarting doesn't help. I do see a restore point listed near the time of
the cloning but thought I would ask here before doing something I would come
to regret.
Thoughts on using that restore point on a otherwise working system?
Or ideas on repair to make restore work, I see ideas after googling it but
most are draconian measures. I prefer the knowledge available here.
Shakey
 
shakey said:
In regard to the below post which many have helpfully replied to:
Today I tried to make a manual restore point and received the message
"system restore is unable to create a restore point. please restart
the computer, and then run system restore again."
Restarting doesn't help. I do see a restore point listed near the
time of the cloning but thought I would ask here before doing
something I would come to regret.
Thoughts on using that restore point on a otherwise working system?
Or ideas on repair to make restore work, I see ideas after googling
it but most are draconian measures. I prefer the knowledge available
here. Shakey
Click to expand...

From your original post I take it that you used Western digital's data
lifegaurd tools for your
image that came with your HD? Me too, but I had to do it twice,the first
image I made I recieved a system restore error just like you have and I
could not get it to work (reading your post is like Dejavu). I kept my old
HD around just in case and wound up starting all over from scratch, the
second time I made the image all was well except for the reregistering.
I might suggest your try true image for your image.

http://www.acronis.com/promo/ATIH/t...oogle&ad=ati&gclid=CKDczvnqupgCFQJ-xgodrm4tZg

I would have used this to begin with but I had a older version at the time
that did not support my new HD size.
Good luck, and again the second time around was the charm using data
lifeguard.
 
Back
Top