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

Number   :  2759
Date     :  2002-09-07
Author   :  Kan Yabumoto
Subject  :  Re: Exclusion Problem
Size(KB) :  2



edlight0:

As to the error message, the most likely scenario is that
the file you specified (c:\dos\bats\_clonenot.txt) does
not exist. Otherwise, it looks good to me.

Caution: The "parameterized" batch file argument using
"%1" is prone to typing error. You should avoid the use
of %1 as the destination specifier (the source specifier
could be equally deadly). You probably have only a
handful of destination directories. I suggest that you
create several batch files like that so that you will
be free from making a typing error that could be fatal.

But, the worst part of this is the combination with
the /YY switch. Remember that a /CLONE operation
performs the removal of any extra file or directory
in the destination that are no longer present
in the source. That's because one of the purposes
of the /CLONE operation is to make the destination
to be a faithful duplicate of the source.

With the /YY switch, you are removing *ALL* of the
safety features that are built in. Yes, the numerous
prompts are really nuisance to users. But, safety comes
first. For that reason, XXCOPY tries to give you
different warnings for different occasions. It is
helpful to read each warning message (and after you
understand what it says) and then remove it by applying
a more targeted prompt-suppressing switch. The easiest
way to do so is to type "?" in response to a prompt
for a context-sensitive help (shows you which switch
to use in order to suppress the warning).

Imagine when you run the batch file and typed a
wrong parameter and hit the Enter key. It could
wipe out the wrong destination (because of the
removal of "extra" files and directory in the
destination) when you accidentally entered a wrong
but existing destination directory. This has happened
to a few users. It is really devastating.

A safe batch file should not have a input parameter
which accepts a wrong (but syntactically valid)
parameter by accident.

Use the /YY switch at your own risk.

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


At 2002-09-07 00:21, you wrote:
>I've been using 2.56.3 because it doesn't give me exclusion problems.
>
>Decided to try 2.82.3
>
>Why would this command line in a batch file (on one line)
>
>xxcopy c:\ %1\ /clone /EX"C:\DOS\BATS\_CLONENOT.TXT"
>/OA"C:\xxcopylog.txt" /OX /yy
>
>give me this error?
>
>Invalid switch (/EX"C:\DOS\BATS\_CLONENOT.TXT)



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