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

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


--- In xxcopy@yahoogroups.com, Kan Yabumoto  wrote:
> 
> 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

Ah Ha! This is what I was trying to say in an earlier post, when you 
got hung up on semantics. I had called disk 0 (my C: thru H:) 
the "system" disk. And I even understand now that you prefer to call 
a "partition" a "volume". Just picking a nit here, but I always 
thought a Volume was 2 or more partitions linked to be accessable as 
1 drive letter? But frankly, I don't care what it's call, as long as 
we both agree what we're talking about.

I even understand your argument about trying to "keep it simple" by 
only dealing with the "system\OS" partition\volume. I was only 
mentioning my perhaps unusual configuration of breaking my 
operating "copy" (everything that comprises my total operating load) 
out into 6 partitons as a thing that you would run into. Wah-Lah, 
above. Sorry, I'm just in a "contrary" mood here. But 
unfortunately "simple" means "the way we understand it."

This is what I understand. If I've made an image of an OS partition 
with anything that copies everything (Win32 not running), then there 
is only 1 change needed to make that copy bootable (provided it is 
then connected as IDE 0, drive 0.) That's assigning the copy as C: 
(thru whatever, if comprised of more than 1 partition\volume) at 
HKLM\System\MounteDevices, DOSDevice values. (And this works fine by 
the way.)

So, the only problems I've got is: 1) Copying those damn 
System\Locked\Registry files without shuting down Win32. (Well, I 
have a way, I just don't like having to use a seperate application 
for 14 crummy files!) And 2) "Simply" performing the registry edit 
above. So, I'm following XXClone as a method of obtaining everything 
in one app. It looks like you're getting there, and definitely 
deserve a Compliment (this was it)!

And all this talk about MBR, etc. has me confused? Could this be 
because I always start with an Image of the Original first before 
then maintaining the Backup\Copy with Win32 tools?

Sounding off: DES



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