Prev: wake up from Standby doesn't work
Next: How do I get Xp (and Vista please) to remember when I setup afold
From: Lem on 19 Apr 2010 18:32
Anna wrote:
> "Lem" <lemp40(a)unknownhost> wrote in message
> news:OCvSBUA4KHA.4332(a)TK2MSFTNGP02.phx.gbl...
> (SNIP)...
>> The following is a bit old, but is from a poster in the XP newsgroups --
>> Anna -- who is extremely knowledgeable about cloning and disk imaging. It
>> is based on an older version of the commercial Acronis product, but the
>> interface should be very similar to what you'll see with the WD free
>> version.
>> *VERY IMPORTANT: read the "NOTE" after step 13.*
>>
>> <QUOTE from Anna>
>> Step-by-Step Instructions for Using the Acronis True Image Program to
>> Backup & Restore One's Hard Drive...
>>
>> Using the Acronis True Image program there are two different approaches
>> one can take to back up the entire contents of one's day-to-day working
>> HDD, i.e., the operating system, all programs & applications, and
>> user-created data - in short, *everything* that's on one's HDD...
>>
>> 1. Direct disk-to-disk cloning, or,
>> 2. Creating disk images
> (SNIP)...
>> NOTE: Just one other point that should be emphasized with respect to the
>> disk cloning operation should the recipient of the clone be another
>> internal HDD and not a USB or Firewire external HDD. Immediately following
>> the disk cloning operation the machine should be shutdown and the source
>> HDD should be disconnected. Boot ONLY to the newly-cloned drive. DO NOT
>> BOOT IMMEDIATELY FOLLOWING THE CLONING OPERATION WITH BOTH DRIVES
>> CONNECTED. There's a strong possibility that by doing so it is likely to
>> cause future boot problems with the cloned drive. Obviously there is no
>> problem in this area should a USB or Firewire EHD be the recipient of the
>> clone since that device is not ordinarily bootable in an XP environment.
>>
>> <\QUOTE from Anna>
>>
>> --
>> Lem
>>
>> Apollo 11 - 40 years ago:
>> http://www.nasa.gov/mission_pages/apollo/40th/index.html
>
>
> Lem:
> As you possibly may know from my previous posts re this issue of
> disk-cloning/disk-imaging, I'm a rather passionate supporter of the Casper 6
> disk-cloning program and strongly recommend that program for most PC users
> as a comprehensive backup tool.
>
> (I recognize this is probably of little interest to the OP since I take it
> he/she is primarily or exclusively concerned with just cloning the contents
> of his/her (apparently) failing HDD to a newer HDD. And it appears he/she
> may have other problems as well!)
>
> The reason for this post is in connection with my cautionary "NOTE" (above
> quoted) with respect to the ATI program. I wanted to mention that one of the
> principal reasons we prefer the Casper program to other disk-cloning
> programs (such as the Acronis one) is that unlike those other programs
> Casper completely avoids that potential problem that I referred to.
>
> Over the past two years or so since we began working with the Casper
> disk-cloning program we've performed (or have been involved with) hundreds
> of disk-cloning operations involving a wide variety of PC makes/models, HDDs
> (both PATA & SATA), etc. During that time we have never encountered a
> *single* occurrence of the problem alluded to. That is to say a user could
> clone the contents of his/her "source" HDD to another *internal* HDD and
> there would be no (possible) subsequent problem affecting the boot
> capability of the destination (cloned) HDD even when the system was booted
> to the source HDD with the cloned HDD connected *immediately* following the
> disk-cloning operation.
>
> Under that scenario the cloned HDD would of course be treated as a secondary
> HDD with a drive letter assignment of (obviously) other than C:. However,
> should the source HDD be later disconnected so that the boot would involve
> *only* the newly cloned HDD, that drive would boot without incident an be
> assigned the "normal" drive letter assignment of C:.
>
> Furthermore, should both HDDs be connected in the system and the user
> changes the setting of the BIOS boot priority order to accommodate a first
> boot to the cloned HDD, similarly that HDD will boot without incident. And,
> of course, the former source HDD would then be treated by the system as a
> secondary HDD as would be expected under those circumstances.
>
> And should (for some reason) the user decide to boot to the original source
> HDD at some subsequent time, the boot to that drive would proceed normally.
>
> I thought the above info might be of some interest to you & others.
> Anna
>
>

Anna -

Thanks.

As you can tell, I think highly of your posts (and save them for others).

--
Lem

Apollo 11 - 40 years ago:
http://www.nasa.gov/mission_pages/apollo/40th/index.html
First  |  Prev  | 
Pages: 1 2 3
Prev: wake up from Standby doesn't work
Next: How do I get Xp (and Vista please) to remember when I setup afold