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

Number   :  4472
Date     :  2003-04-28
Author   :  J. Merrill
Subject  :  Re: Many Copy Failures
Size(KB) :  1


Please excuse me if you put this info in another message that I haven't looked at recently.

We (and perhaps you) could probably tell if the problems are due to "file opened exclusively by another program" if we had a few sample file names (including full path). If that's the problem

There is no good reason for software to open a file in a way that prohibits anyone else from opening the file (even read-only), unless the file's contents are changing constantly and thus you can't rely upon any particular "snapshot" of the file's contents while the software that writes to it has the file open. In that case, it's not desirable to make a copy of the file while it's in use, as the copy could be corrupt.

I wonder if there's an easy way to run XXCOPY relatively early in the boot process, so that fewer files would be opened by the O/S. I don't know another real solution, as MS is unlikely to stop opening files exclusively (instead of, for example, use locking to prevent other tasks from reading inconsistent data).

At 10:20 PM 4/26/2003 +0000, jim_66666 wrote
>This third system (the XP Home one I mentioned) was copying from NTFS 
>to NTFS and had hundreds of file copy failures.
>
>So that makes hundreds on my XP Pro system. Hundreds on my friends 
>W98 system. And, hundreds on his friend's XP Home system, and these 
>were permanent/repeating. None of which were between different file 
>systems/formats.
>
>I don't understand how a problem this serious and common is not well 
>known?
>
>jim


J. Merrill / Analytical Software Corp



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