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

Number   :  3180
Date     :  2002-12-02
Author   :  listsetc@b...
Subject  :  Re: tripping xxcopy-corrupting filenames
Size(KB) :  2


Kan
Your analysis of my problem is really appreciated; I did not really think 
that it was an xxcopy bug, but it is such a strange problem that I 
thought I should post it just in case your team recognised something. 
The problem usually apppears as I have described it, but sometimes 
other symbols are thrown in towards the end of the name, such as 
exclamation marks and of all things, spaces.
One thing that would seem to exclude xxcopy is that the problem does 
also occur in directories on the target drive on which I never used 
xxcopy (unless xxcopy was still "looking for " the correct directory). 

On 1 Dec 2002 at 14:45, Kan Yabumoto wrote:


>unless you disable it by /NX0 

No I didn't

>Still, the only explanation ... is either a bug  
>or other factor outside of XXCOPY. The only other 
>explanation is that your system is very unstable

No, fortunately this only happens on the target drive (identical and 
delivered at the same time as the main drive). I have a third identical 
drive bought at a later time and intend to swap the target drive out. This 
would address your two suggestions of causes unrelated to xxcopy as 
pasted at the end of this reply.

> What I suggest as a starting point, is to establish whether the
> problem is repeatable exactly.
> Play around and experiment to better characterize the problem so
> that you can list the necessary condition for the problem to
> appear in a consistent fashion.
>reduce the complexity.
>Your careful observation during this
> process will usually lead to a narrow 
>set of conditions that
> cause the problem.

I shall try and follow your advice.

> If 
> I would look for a cause that is unrelated to XXCOPY.
> Viruses, corrupted file system 

At the moment I must admit that the latter looks more likely; it is just 
that I did everything possible to repair things using scandisk, then when 
it happened again a program called mbrwork followed by scandisk, but 
the same problem occurred again. I should also say that the files are 
also sometimes corrupted resulting in lost fragments (although the bulk 
of the data is still usable). The data on this drive was cloned using 
another commercial product, but when I swap it out I will use XXcopy 
because it moves only the files and does not mess with boot sectors 
etc.

Once again, thank you very much for your insights.
Douglas



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