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

Number   :  201
Date     :  2001-06-15
Author   :  Kan Yabumoto
Subject  :  Re: The /X parameter syntax
Size(KB) :  3



Ed:

1. Nothing has changed with the way the /debug switch works.
What has changed was where the /OX output (the warning messages
which are generated by the pre-processing step of the exclusion
item) is directed. Since the much of the warning message of
which exclusion item was discarded, etc. was mostly boring
info for the user, we decided the right place to put the warning
message was in the log file). Since the log file contents are
viewable only after it is closed, it looks as though the
exclusion list is created at the end of the XXCOPY job.
That is not true. If you add /DEBUG /OX, then, you will see the
exclusion item list displayed on the console (and let you
continue with a keystroke) before the show starts.

2. The contents of the /EX text file is a list of the so-called
"exclusion specifier" which has its formats (with many variations).
You should look at

XXTB #05 for details.

But, it is not true that you need to specify the full path.
You can have a relative path as well. A relative path is
interpreted as relative to the "base directory" which is the
source directory with the longest path levels without a
wildcard (remember now, XXCOPY accepts many wildcards in many
levels of paths).

BTW, there was a bug in /X feature where if you use a path
starting with a backslash without the drive letter (e.g.,
\mydir\xyz\), AND, the current drive is different from the
source directory's drive, the drive letter for the /X items
gets wrong drive!!! This was a bug and we have just fixed it.
(see v.2.56.3). Your observation may be related to this.
With this bug, if you specify an absolute path, add the
drive letter (and colon) always (or, make a relative path
which does not start with a backslash).

We will announce it shortly...

3. /X and /EX can coexist. But, starting with the new release,
we are discouraging the use of /EX switch altogether. The
better way to handle is to use the /CF switch (this feature
deserves a dedicated technical bulletin). Using the /CF file,
everything can be placed in just one file. You can add
comments, (we recommend one-line per command switch with
explanation for it using // a comment just like C++
It allows a syntax to connect multiple lines to form a
very long unbroken logical line (so that an extremely long
pathname can now be specified). Having just one command file
for a huge backup job which contains everything including
the exclusion items seems easier to manage than to have
a separate /EX file. On the other hand, to share a common
exclusion file set by multiple command files is also
a convenience. It's up to you.

But, /X and /EX can certainly coexist.

Kan Yabumoto

====================================================================

At 2001-06-14 16:39, Ed Light wrote:
>OK, Kan, I've got ver 2.56.2 and the exclusions as they affect me are
>fixed, it seems so far, with these conditions:
>
>1. /debug doesn't list the exclusions until after the run - oops!
>2. The full source path must be used each entry in the /ex text file
>3. You can't have /x followed by /ex
>
>Hooray! Kudos!



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