[<<]Message[>>]    [<<]Author[>>]    [<<]Subject[>>]    [<<]Thread[>>]

Number   :  5479
Date     :  2003-09-07
Author   :  des4212001
Subject  :  Re: xxclone: can dst drive have other files on it?
Size(KB) :  3


--- In xxcopy@yahoogroups.com, Kan Yabumoto  wrote:

(snip)

> In either way, when you boot into the cloned (target) volume,
> the system volume will be assigned to C: (the drive letter
> which was originally assigned to the source). This is
> because a lot of applications (if not all) including
> many batch files assume the system disk is C:. Otherwise,
> it will be quite inconvenient for the user. If you keep
> the original (source) volume still attached to the system,
> the original volume is now assigned to D: (XXCLONE swaps
> the assignment between the source and the target) when
> the Windows is booted using the target volume as the
> system drive. Moreover, all other volumes will retain
> the same drive letter assignment.
> 
> I believe this scenario is exactly what the user wants.

For probably 99% of users this is correct. However please consider 
my personal case (which can not be unique?). My 'System' disk 
consists of 6 partitions, assigned C: thru H:. (Intentionally trying 
to reduce the OS it's self to a minimum, as this is 
where 'restoration' has most meaning.) Hence there are many startup 
items on the logical drives (D: thru H:) of the extended partition 
making up the 'System' disk. The 'Backup' drive is assigned I: thru 
N: (all partitions copies of C: thru H:). To swap the drives, 
or "boot the backup", C: thru H: must be swapped with I: thru N:.

A serious exception to "all other volumes will retain the same drive 
letter assignment", above there (if I understand what you're 
saying?) What an interestion mess could result from booting the OS 
partition on the "Backup/Copy" but still tring to use all other 
partitons on the original disk... if it was still connect that is! 
Please tell me my operating senerio isn't too complicated to address.

> 
> The above example used the most common drive letter
> assignment. However, XXCLONE does not assume that
> the source volume is always C:. If you have a
> Windows system with the system disk in E: and you want
> to clone the system volume to C:, there is no problem.
> XXCLONE will make the new cloned volume assign itself
> E: when it is used as the boot drive.
> 
> Currently, XXCLONE performs double-reboot in order
> to copy everything including stubborn files. In
> the future, we plan to make it one-step (without
> reboot) to make the target volume self-bootable.

Hulleluiah! As this means copying those damn System/Locked files 
with Win32 running. And for this you are to be congratulated!

> In essence, XXCLONE is our answer to all those questions
> regarding XP's system disk clone so that the new volume
> become bootable. So, the primary goal is to make it
> bootable and the XXCOPY-like backup operation is strictly
> a convenience (bonus) feature. And, we wanted to make
> the product easy to use (without the need to understand
> technical details as in the XXCOPY case). We don't
> want the extreme versatility like XXCOPY which makes
> it hard to use. We intend to resist all kinds of
> suggestions to suit particular users wish.
> 
> Kan Yabumoto

What a double edged sword, making a Complicated thing look Easy. I 
haven't even used it yet and I'm busy coming up with Complications.

Following from a distance! DES



This message if part of XXCOPY's message Archive.
The archive contains all the messages posted at Yahoo!Groups: XXCOPY.