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

Number   :  8014
Date     :  2004-06-07
Author   :  des4212001
Subject  :  Re: switch for open files
Size(KB) :  1


 
> I'm pretty sure that MoveFiles works the same as MV or INUSE
> from the Resource Kit. It simply adds entries to:
> HKLM\SYSTEM\CurrentControlSet\Control\
> Session Manager\PendingFileRenameOperations
> 
> See also http://www.ss64.com/nt/mv.html for some more info.
> 
> Having said that, I gave it a brief test by attempting to copy
> a registry file to another location and nothing happened. I
> guess that since the registry files are in use as soon as
> windows boots, there isn't any opening to copy them before
> they become locked.
> 
> Movefiles is therefore probably no good for copying the
> registry files. Of course, if you only want to copy the
> registry files, you can use ERUNT in a batch file to copy
> the files to a temporary location then move them to their
> correct location on the cloned copy of the system.
> 
> Garry

Now that's more like it! This MV clearly states "Copy" as opposed 
to "move". (Any operation is supposed to take place at the next boot 
with it or Movefile.) I think I'm catching on that MV(Movefile too?) 
is "the thing" that loads the PendingFileRenameOperations subkey. 
Movefiles' "help" is scary because of the stated results of an empty 
Destination.

BTW, ERUNT is indeed my current registry file handler. I'm just 
still looking for the built-in method that logically has to be 
there. And this appears to be it!

DES



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