[<<]Message[>>] [<<]Author[>>] [<<]Subject Thread
Number : 163 Date : 2001-06-07 Author : Gabe Fineman Subject : Re: Excluded files Size(KB) : 9
------_=_NextPart_001_01C0EF7B.59777230 Content-Type: text/plain Thank you for the quick reply. I will try it tonight and let you know if it does not work. Perhaps it is the quotes around the address even though there is no space in it. I am also sorry about the message format. I default to HTML, but if I am replying to a message, it is supposed to use that format. I was replying to one of your messages on the board that came through as HTML. I use Outlook and it seems to do whatever IT wants to do despite any documentation or previous patterns. I will try to use only plain text in the future, but this message is in plain text and I still see blue references to what it things are Internet addresses or files. I think that is a function of the reader program. -Gabe -----Original Message----- From: Kan Yabumoto [mailto:tech.xxcopy@d...] Sent: Thursday, June 07, 2001 1:16 PM To: xxcopy@yahoogroups.com Subject: Re: [xxcopy] Excluded files 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 > Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: xxcopy-unsubscribe@yahoogroups.com Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service. ------_=_NextPart_001_01C0EF7B.59777230 Content-Type: text/html Content-Transfer-Encoding: quoted-printable RE: [xxcopy] Excluded files Thank you for the quick reply. I will try it tonight and = let you know if it does not work. Perhaps it is the quotes around the addre= ss even though there is no space in it. I am also sorry about the message format. I default to HT= ML, but if I am replying to a message, it is supposed to use that format. I= was replying to one of your messages on the board that came through as HTM= L. I use Outlook and it seems to do whatever IT wants to do despite any doc= umentation or previous patterns. I will try to use only plain text in the f= uture, but this message is in plain text and I still see blue references to= what it things are Internet addresses or files. I think that is a function= of the reader program. -Gabe -----Original Message----- From: Kan Yabumoto [mailto:tech.xxcopy@d...] Sent: Thursday, June 07, 2001 1:16 PM To: xxcopy@yahoogroups.com Subject: Re: [xxcopy] Excluded files Gabe: I'm not sure what is causing your problem. Your com= mand syntax seems correct. It could be a very subtle bug (due = to some unexpected situation outside the assumed behavior) of XX= COPY. One thing you may try to get around this problem (which = may not work but worth a try) is to use the "relative&q= uot; 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-pro= cessing" step (which supposedly optimizes the exclusion scheme), = if it is caused by a subtle XXCOPY bug, it could not trigge= r the bug. --------------------------= --------------------------------- What is the base director= y (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 relativ= e 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 direct= ories and subdirectories which are represented by the source= specifier. In most cases, this is sim= ple. If the source is C:\mydir\abc\<= /FONT> Then, the base directory i= s c:\mydir\abc\ But, when you take advant= age of the recently enhanced feature (we call "Wi= ld-Wild-Source"), things start to look more confusing. C:\mydir\abc*\*.*&nb= sp; Base directory is c:\mydir\ C:\mydir\*\abc\*.do= c 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 p= rogram, 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 characte= r may play a very important role in syntax and the use of a pr= oportional pitch font often make it difficult to see a space charac= ter. Kan Yabumoto <tech.xxcopy@d...> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D= =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D 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<= /FONT> > > I thought that the switch /X"\\ASIVASRV\D$\*\~= *.*" > would exclude all files that started with a tilde a= nywher > on the D$ drive. Instead, I get the following= : > > Discarded Exclude item (not present) \\ASIVAS= RV\D$\~*.* > and then the message that the document was copied:<= /FONT> > \\ASIVASRV\D$\BAlves\My Documents\20 compensation\~= $nior Director of Products and Services.DOC &nbs= p; = 162 > > It looks like the \*\ construct is not being applie= d to > sub directories. Anyone have any ideas what I am do= ing > wrong? It must be too obvious for me to see. > > Thanks >-Gabe Fineman > Yahoo! Groups Sponsor To unsubscribe from this group, send an email to: xxcopy-unsubscribe@yahoogroups.com Your use of Yahoo! Groups is subject to the Yahoo! Terms = of Service. ------_=_NextPart_001_01C0EF7B.59777230--
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.