From: Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Full screen mode under Win2k???
Date: Sat, 11 Jan 2003 15:32:20 CST
Organization: Rice University, Houston TX
Lines: 18
Message-ID: <3e208d64.sandmann@clio.rice.edu>
References: <3e1f3e70 DOT 5a0c DOT 0 AT net DOT hr> <cjjv1vo86smq22rqd1nhlepki5g8e8u0mt AT 4ax DOT com> <3e2026c0$0$30570$91cee783 AT newsreader01 DOT highway DOT telekom DOT at>
NNTP-Posting-Host: clio.rice.edu
X-Trace: joe.rice.edu 1042321407 20700 128.42.105.3 (11 Jan 2003 21:43:27 GMT)
X-Complaints-To: abuse AT rice DOT edu
NNTP-Posting-Date: 11 Jan 2003 21:43:27 GMT
X-NewsEditor: ED-1.5.9
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

> > There are two on 2K & XP and they do work slightly differently.  

> Why two?

CMD.EXE is the native 32-bit command interpreter.  There is no limit on 
the path length, or on environment variables.  It has enhanced syntax
which allows you to redirect stderr (or put stderr into stdout):

myprog 2>my.err >my.out
myprog 2>&1 >allout.txt

It also has dozens of other extensions which make it easier to use,
but may not be 100% compatible with the way command.com behaved.
I personally strongly prefer CMD.EXE and haven't had any problems
using it with DJGPP.

command.com is present primarily for compatibility reasons (truncated
path and environment, programs that open it by name).