![]()
[<<]Message[>>] [<<]Author[>>] [<<]Subject[>>] [<<]Thread[>>]
Number : 2763 Date : 2002-09-08 Author : Kan Yabumoto Subject : Re: Exclusion Problem Size(KB) : 3
Ed: After all, it was a bug in XXCOPY! /ex"c:\dos\bats\_clonenot.txt" is a valid syntax but XXCOPY failed to handle it correctly. This is not the first time that I made an assumption that the XXCOPY program was working right and blamed the user for the difficulties and the problem turned out to be a bug. It's always embarrassing to blame the user for a legitimate bug report. Usually I pay attention to who made the report. In your case, I should have known better. I recall you are an advanced user who would not report a false bug-report (in this particular case, the user could easily checked whether or not the file exists --- on the other hand, some novice users who specify a bare filename (without its full path) and often never find it!!!). Any filename for /EX or /CF which is inside a quoted string (which is a valid syntax even if you don't have an embedded space) should be accepted. We will release a fix shortly. For the time being, please select a filename whose path does not have an embedded space and remove the quotes which are not handled right by XXCOPY. ---------------------------------------------------------- The bug which was apparently introduced in recent versions which support a separating colon between the switch alphabets and the optional parameter. We changed the command-line parsing code when we started to support this feature to improve the readability of the command (mostly useful for the /CF command text see XXTB #37). That is, now you can say /X:*.mp3 /ON:c:\temp\mylog.txt /CF:c:\bin\myscript.xcf We had a messy syntactic collision with this scheme with the following pair of switches, /SZ // copy first n bytes /SZ: // select files of n bytes The culprit of this mess was we did not think carefully when we added the /SZ switch for our internal consumption which eventually became an official switch. When we added /SZ: (with its variation) to select files based upon the file size, we just could not find any better mnemonic for the function. Now, we are gradually phasing out the /SZ switch which is now being replaced by the new /TR switch which performs the same function (Truncate at n bytes). As soon as we phase out the /SZ switch completely, we will publicize the syntax for the optional colon more openly. -------------------------------------------------------- Kan Yabumoto =========================================================== At 2002-09-08 09:29, you wrote: >--- In xxcopy@y..., Kan Yabumoto wrote: > > > > edlight0: > > > > As to the error message, the most likely scenario is that > > the file you specified (c:\dos\bats\_clonenot.txt) does > > not exist. > >Version 2.56.3 sees the file; I have been using such an old one for a >long time because of exclusion errors in the other ones. Notice that >in the error message 2.82.3 left off the trailing double quote mark >for the /ex file. > >Invalid switch (/EX"C:\DOS\BATS\_CLONENOT.TXT) > >That should indicate that the error may be in parsing. > > > Caution: The "parameterized" batch file argument using > > "%1" is prone to typing error. >Thanks, but I call it from other batch files. No problems for a year. > > > But, the worst part of this is the combination with > > the /YY switch. > >Thanks for the warning. I created the batch files that call it >carefully. They have been reliable.
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.