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

Number   :  2858
Date     :  2002-09-27
Author   :  Kan Yabumoto
Subject  :  Re: Problem with corrupted directory
Size(KB) :  2


Philippe:

I wish you had shown (just to cite a few line of) the
pop-up message box that you observed repeatedly.
I have a hunch that the warning/error message was
generated by some software module which is responsible
for the Zip Drive operation, rather than XXCOPY itself.

The reason why I can say this is that currently there
is only place where XXCOPY generates a pop-up message
box (it is not related to a file I/O error).

----------------------------------------------------
The only pop up message that XXCOPY generates has
the following text in it. It appears when XXCOPY
detects an excessive number of errors in SFN-
preservation operation (by /NX).

XXCOPY detected an excessive number of
failed attempts to preserve the short
name in destination. An OS mismatch
for the file system is suspected. You
may disable the feature by adding the
/NX0 switch.
----------------------------------------------------

All other forms of error/warning reporting are done
as a regular text inside the DOS Box whose typical
reply is also confined to the keyboard entry to the
DOS Box ---- no pop-up dialog window.

So, XXCOPY cannot help in your case.

To kill a running XXCOPY job, it accepts a 
key between file-copy operations. So, in theory,
you should be able to terminate "gracefully" rather
than by killing a running task.

As a side note, I have experienced that when
I "killed" an XXCOPY task in the middle of a huge
file copy operation on an NTFS volume using XP-Pro,
I later found the volume having a non-removable
chunk of allocated section on the volume which
was too stubborn to reclaim ---- I had to reformat
the entire volume. So, I generally avoid killing
a running task.

Maybe, it is time for you to consider the CD-RW as
a Zip drive alternative...

Kan Yabumoto
==================================================

At 2002-09-27 04:50, Philippe wrote:
>I use XXCOPY 2.82.4 on WinNT 4 Server sp5/FAT16 + IE4's new shell (Active
>Desktop).
>I made a batch script to update a tree of folders with source code and
>binaries to a Zip 250 drive.
>It works fine and fast in clone mode.
>One line of my batch is:
>xxcopy "F:\_Work\CNS2.3\cgi\" Y:\23\cgi\ /EXDev_NoBackup.lst /CLONE /YY/ZS
>I know about /YY culprit, but as I said, it is tested and OK.
>
>The problem is that Zip drive (or its driver) is quite unreliable. Today, I
>had a directory reported as corrupted, confirmed by the system.
>XXCOPY reported the problem in a dialog box. Good.
>But it displayed the dialog box for each and every file it tried to put in
>this folder. Argh! I had to kill the job brutally...
>
>My suggestion: either avoid to report the same error twice (or, say, more
>than thrice to emphasize the problem?), or provide something like a checkbox
>labelled "Skip this error for this folder", or just add a Cancel job button to
>the dialog box...
>
>Thank you for your wonderful utility.



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