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

Number   :  159
Date     :  2001-06-07
Author   :  Kan Yabumoto
Subject  :  Re: Excluded files
Size(KB) :  2


Gabe:

I'm not sure what is causing your problem. Your command syntax
seems correct. It could be a very subtle bug (due to some
unexpected situation outside the assumed behavior) of XXCOPY.
One thing you may try to get around this problem (which may
not work but worth a try) is to use the "relative" path
specification for the exclusion item (see below).

In your case, you may use

/X~*.*

which is equivalent to what you entered:

/X\\asivasrv\d$\*\~*.*

Since the first one does not go through the "pre-processing"
step (which supposedly optimizes the exclusion scheme), if
it is caused by a subtle XXCOPY bug, it could not trigger the
bug.

-----------------------------------------------------------
What is the base directory (the reference point to a
relative pathspec in the /X switch)

This is because a relative path specifier in the /X switch
is interpreted as relative to the "base directory" which is
defined in XXCOPY as the topmost level directory in the source
directory which does not have any wildcard. That is, the
common part of all directories and subdirectories which are
represented by the source specifier.

In most cases, this is simple. If the source is

C:\mydir\abc\

Then, the base directory is c:\mydir\abc\
But, when you take advantage of the recently enhanced
feature (we call "Wild-Wild-Source"), things start to look
more confusing.

C:\mydir\abc*\*.* Base directory is c:\mydir\
C:\mydir\*\abc\*.doc Base directory is c:\mydir\
------------------------------------------------------------- 



By the way, Gabe, please refrain yourself from posting a text
other than in plain text. In your Email handling program, please
select the "plain text" format so that we all do not have to
suffer formatted text which are sometimes very difficult to read
(on my screen your blue text was extremely difficult to read ---
I had to perform a cut-and-paste to a plain-text editor to see it).
Also, in command line programming, even a space character may
play a very important role in syntax and the use of a proportional
pitch font often make it difficult to see a space character.

Kan Yabumoto

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

At 2001-06-07 11:26, Gabe Fineman wrote:
>
> I am using the following command to backup files
>
> XXCOPY \\ASIVASRV\D$ E:\Asivasrv\D$ /A0/H/R/K/BN/DA/E/NX0/FT/CK0/YY/Q/ZE 
/X"\\ASIVASRV\D$\*\~*.*" /OAE:\Bkup.log
>
> I thought that the switch /X"\\ASIVASRV\D$\*\~*.*"
> would exclude all files that started with a tilde anywher
> on the D$ drive. Instead, I get the following:
>
> Discarded Exclude item (not present) \\ASIVASRV\D$\~*.*
> and then the message that the document was copied:
> \\ASIVASRV\D$\BAlves\My Documents\20 compensation\~$nior Director 
of Products and Services.DOC 162
>
> It looks like the \*\ construct is not being applied to
> sub directories. Anyone have any ideas what I am doing
> wrong? It must be too obvious for me to see.
>
> Thanks
>-Gabe Fineman
>



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