[<<]Message[>>] [<<]Author[>>] [<<]Subject[>>] [<<]Thread[>>]
Number : 499 Date : 2001-07-31 Author : rotaiv Subject : Re: Include / Exclude Options Size(KB) : 6
--=====================_1913267873==_.ALT Content-Type: text/plain; charset="us-ascii"; format=flowed At 07/31/2001 05:48 AM, Kan Yabumoto wrote: >Dear Rotaiv: > >Let me first remove the notion that one-line XXCOPY is much better >than four-line XXCOPY script. While it is true that if you can >write a one-line batch file it is more elegant than four-line >batch file (that is, to eliminate the batch file altogether except >you may want to shorten keystrokes to eliminate typing error), >the difference between two-line batch file and 20-line batch file >are rather small. I agree with everything you said with one very minor exception. The /PB switch is by far one of my most favorite additions to xxcopy. However, with multiple xxcopy commands, the /PB switch is reset each time so I do not get a progress bar for the whole copy process. Agreed, this is quite minor but that was one of my main concerns. As I long time user and creator of batch files, I agree with simplicity versus shortness. While we are talking about the /PB switch, would you consider modifying the XXPBAR.EXE to return window focus to the process that called it? Often, with my batch files, I like to pause after each xxcopy command (another reason to do it all in one) so I can see the results. However, XXPBAR takes focus and forces to me to toggle back. Once again, very minor but you are always asking for suggestions. >If you study the >way XXCOPY's wide variety of operations (especially the way the >/X feature works), supporting multiple-source directories will >cause more confusion which we have no way to simplify. Therefore, >it is our deliberate design feature which do not allow for multiple >source specification. Good point, now I understand. >Now, I don't know where you get the C:\NULL ? I used "NULL" because "NUL" did not work - here is my output: C:\>xxcopy c:\nul d:\backup /IN*.xls /IN*.doc /s XXCOPY == Pro Edition == Ver 2.70.2 (c)1995-2001 Pixelab, Inc. Invalid source directory (c:\nul) Directories processed = 0 Action speed (MB/min) = 0.0 Files copied = 0 Exit code = 34 (Illegal command parameter) In writing this email, I decided to double check again just to make sure I was not doing something wrong. To make a long story short, it does not work under NT4 SP6a or W2K SP1 but it DOES work under Win 98 SE. This appears to be an issue unique to NT - I hope this helps diagnose the problem. >We chose the name "NUL" because >it is already a reserved word in Microsoft's OS (you cannot >create the NUL name either as a file or as a directory). Well, under normal circumstances you can't. However, the following will work: echo test > \\.\c:\nul Look in the root of C: and you'll see a file called "NUL". To delete the file, type: del \\.\c:\nul Once again, this appears only to work with NT - it does not work under 98. For more information, reference Q120716. Although this is totally useless and/or trivial information, it became a problem when someone created a file called COM1 on my FTP server and I could not delete it. Regards, rotaiv. --=====================_1913267873==_.ALT Content-Type: text/html; charset="us-ascii" At 07/31/2001 05:48 AM, Kan Yabumoto wrote: Dear Rotaiv: Let me first remove the notion that one-line XXCOPY is much better than four-line XXCOPY script. While it is true that if you can write a one-line batch file it is more elegant than four-line batch file (that is, to eliminate the batch file altogether except you may want to shorten keystrokes to eliminate typing error), the difference between two-line batch file and 20-line batch file are rather small. I agree with everything you said with one very minor exception. The /PB switch is by far one of my most favorite additions to xxcopy. However, with multiple xxcopy commands, the /PB switch is reset each time so I do not get a progress bar for the whole copy process. Agreed, this is quite minor but that was one of my main concerns. As I long time user and creator of batch files, I agree with simplicity versus shortness. While we are talking about the /PB switch, would you consider modifying the XXPBAR.EXE to return window focus to the process that called it? Often, with my batch files, I like to pause after each xxcopy command (another reason to do it all in one) so I can see the results. However, XXPBAR takes focus and forces to me to toggle back. Once again, very minor but you are always asking for suggestions. If you study the way XXCOPY's wide variety of operations (especially the way the /X feature works), supporting multiple-source directories will cause more confusion which we have no way to simplify. Therefore, it is our deliberate design feature which do not allow for multiple source specification. Good point, now I understand. Now, I don't know where you get the C:\NULL ? I used "NULL" because "NUL" did not work - here is my output: C:\>xxcopy c:\nul d:\backup /IN*.xls /IN*.doc /s XXCOPY == Pro Edition == Ver 2.70.2 (c)1995-2001 Pixelab, Inc. Invalid source directory (c:\nul) Directories processed = 0 Action speed (MB/min) = 0.0 Files copied = 0 Exit code = 34 (Illegal command parameter) In writing this email, I decided to double check again just to make sure I was not doing something wrong. To make a long story short, it does not work under NT4 SP6a or W2K SP1 but it DOES work under Win 98 SE. This appears to be an issue unique to NT - I hope this helps diagnose the problem. We chose the name "NUL" because it is already a reserved word in Microsoft's OS (you cannot create the NUL name either as a file or as a directory). Well, under normal circumstances you can't. However, the following will work: echo test > \\.\c:\nul Look in the root of C: and you'll see a file called "NUL". To delete the file, type: del \\.\c:\nul Once again, this appears only to work with NT - it does not work under 98. For more information, reference Q120716. Although this is totally useless and/or trivial information, it became a problem when someone created a file called COM1 on my FTP server and I could not delete it. Regards, rotaiv. --=====================_1913267873==_.ALT--
This message if part of XXCOPY's message Archive. The archive contains all the messages posted at Yahoo!Groups: XXCOPY.