Re: Transferring from HD to HD
- From: "Timothy Daniels" <TDaniels@xxxxxxxxxxxxx>
- Date: Sun, 25 Jun 2006 10:42:09 -0700
"Point" wrote:
I currently have win xp home sp2 installed on a single 40gb HD (master) and
then i have another 160gb HD (slave) with nothing on it. First of all im
going to partition the 160 into a 100 and a 60 partitions and then i want to
copy XP from the 40gb hd onto the 100gb partition of the second HD.
How would i go about doing this? (I know how to partition the 160) but the
transferring bit?
The easiest to use dedicated-to-cloning utility that I've found is
Casper XP. You can use it to clone the 40GB to each of 4
40GB partitions on the 160GB HD, or you can clone the 40GB
to a single 160GB partition on the new HD. I use the former
option to keep multiple backup clones on backup HD that I have
in a removable tray that slides into a "mobile rack" in the PC.
By having multiple entries in each partition's boot.ini file, I can
set any partition "active" and then use it to boot any of the multiple
clones in the backup HD, or I can use the boot.ini file in my primary
system HD to boot any of the clones in the backup HD. That option
of cloning single partitions to a HD that already contains other
partitions can only be done by Casper XP and Ghost 9 and 10
among the major backup utilities that can make clones (Acronis'
True Image will only use the *entire* surface of the destination HD
for clones). I believe that restriction is present in the backup utilities
offered by the major hard drive manufacturers, as well.
If you want to try Casper XP for a no-obligation free 30-day trial,
you can download a copy from www.FSSdev.com/products/casperxp/ .
It will work for 30 days, and if you want to use it after that, you'll
have to pay FSS $50 and they'll send you an activation number.
I have Drive Image 7.1 (the utility that Symantec bought and renamed
"Ghost v.9.0"), and I much prefer Casper XP for cloning.
When you make a clone of any OS in the WinNT/2K/XP family,
do as Ron Sommers says - disconnect the "parent" HD first
before booting up the clone for the 1st time. This prevents the
clone from seeing its "parent" and getting permanently (but subtley)
confused. Thereafter, you can run the clone at any time with its
"parent" OS visible to it, and there won't be a problem. When you
remove the source HD, the BIOS will automatically make the next
HD in the HD boot order the boot HD, so you don't have to readjust
the HDs' jumpers to start up the clone. Thereafter, you can use
either multi-booting via entries in the boot.ini file, or you can re-set
the HD boot order in the BIOS to boot any of the clones.
If you want to understand the syntax of the boot.ini file, you'll have
to have a grip on the meaning of "rdisk()" in the ARC paths - part
of each entry in boot.ini. To understand "rdisk()", Google for the
thread 'meaning of "rdisk()" ' with Timothy Daniels as the author
in January of this year in alt.sys.pc-clone.dell:
http://groups.google.com/group/alt.sys.pc-clone.dell/browse_thread/thread/89410e99d968fed2/173931e294f2a9f0?lnk=st&q=insubject%3Ameaning+insubject%3Aof+insubject%3A%22rdisk()%22+author%3Atimothy+author%3Adaniels&rnum=1&hl=en#173931e294f2a9f0
*TimDaniels*
.
- Follow-Ups:
- Re: Transferring from HD to HD
- From: Point
- Re: Transferring from HD to HD
- Prev by Date: Re: Identifying an application that doesn't display its name
- Next by Date: Re: delayed write failures
- Previous by thread: Re: Transferring from HD to HD
- Next by thread: Re: Transferring from HD to HD
- Index(es):
Relevant Pages
|
Loading
