Jose Da Silva wrote:

> You are correct. Pipe is the | char.
> For further info:
[...]
> ">>" is used to append, so if you have a log file, you can append more 
> to it.
> 
> "2>" is normally standard error output "stderr".
> I believe DOS just uses stdout in this case.

It would probably be useful if we started to differentiate between the
various command processors. The "DOS box" in Windows doesn't necessarily
have much to do with MS-DOS, other than that a few basic commands are
similar (depending on the version of Windows).

Up until Win9x, the standard command processor was command.com, and I think
it was similar between the later versions of MS-DOS/Windows. But with Win2k
and WinXP, even though command.com is still present (probably for
compatibility reasons), what most people refer to as "DOS box" or so is
cmd.exe -- which has some of the same commands, but is a quite different
thing.

Regarding supported I/O redirection in cmd.exe (no clue how much of this
works with command.com):

"<file" : read stdio from a file
">file" or "1>file" : send stdout to a file
">>file" or "1>>file" : append stdout to a file
"2>file" : send stderr to a file
"2>>file" : append stderr to a file
">file 2>&1" : send both stdout and stderr to the same file
">>file 2>&1" : append both stdout and stderr to the same file
"cmd1 | cmd2" or "cmd1 0> cmd2" : pipe stdout of cmd1 to stdin of cmd2

BTW, in WinXP the file and directory name completion is enabled by default,
in Win2k it can be enabled in the registry. See also
http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/cmd.mspx

Gerhard
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist