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

Number   :  5523
Date     :  2003-09-10
Author   :  Kan Yabumoto
Subject  :  Re: xxclone: can dst drive have other files on it?
Size(KB) :  2



Anders Thoresson wrote:
>> Although I have never experimented, I guess you may move the
>> entire \Documents and settings\ directory (also called
>> "profiles" directory which is kept inside
>> \Winnt\profiles\ in NT4) into another volume.

> If you can move it after installation, I don't know.
> But if you run an unattended installation, you can specify
> on what partition you want \documents and settings on.
> How it can be done is explained here:
> http://support.microsoft.com/default.aspx?scid=kb;enus;Q314459.
>
> I have c:\windows and d:\documents and settings. If
> I've understood everything in this groups right, this means
> that I can't use XXCLONE out of the box?

I knew someone would do this. Currently, XXCLONE assumes
that the profiles directory (\documents and settings\)
is in the same volume as the system volume.

If you run the current version of XXCLONE, it will
create a \Documents and Settings\ directory in the
destination volume and saves the contents there.
This includes the registry files (NTUSER.DAT and
USRCLASS.DAT). Of course, when the target volume
will be used for reboot, a funny thing will happen.

The new Windows environment (booted from the target
volume) will work as if everything were fine (as long
as the volume of the original \documents and settings\
directory is still present under the same volume name
in the target environment. In this scenario,
the old (original) \Documents and Settings\ directory
will serve as the active directory for that (not in
the target volume's).

We plan to address this issue in the future. When
that happens, the likely method of implementation will
be to accept additional parameter for the secondary
volume (where the \Documents and Settings\) directory
should be saved (either in a GUI-dialog, or from a
command line switch) and proceed as it should.
It is technically feasible, albeit a messy one.

In this case, basically the problem is that the
situation is not simply described as the simplistic
model of operation:

one-source ---> one-target

Rather, it will be like

window-source ---> windows-target
profile-source ---> profile-target

As long as we clarify this point, things should to
well.

I guess the ultimate clone model should then be like

windows-source ---> windows-target
profile-source ---> profile-target
other-source1 ---> other-target1
other-source2 ---> other-target2
other-source3 ---> other-target3
...

It could be quite a mess, but can be done, I guess.

Kan Yabumoto



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