Terry Orchard said:
Actually, Dos-man, I'd be interested in a short description of what
this command interpreter does that can't already be done on the normal
dos window command line. It sure wasn't clear in a quick skim of the
doc.
Terry
Well, I will try to list some things that it can do
that the DOS command interpreter can't do, but I don't
have the program or the docs in hand since I am at a library.
* It has a history command that shows the last 10
commands run. Maybe new versions of DOS have this,
but I have never encountered one that did.
* The exist command can check for the existance of folders.
if exist folder c:\batch write 'it exists'
* Takes up less memory because it's 60K smaller (I think)
* Some of the statements such as DEL accept multiple arguments
del file1 file2 file3
You can print out returned errorlevels without needing to
create a DOS batch file to find out what the errorlevel was.
run a program and then type in
write 'The errorlevel returned was ~\*errorlevel~'
These are some interesting things that cmd.com can do. Like I
said, it's not finished. It is probably only half way finished
(shudder).
A few of the commands need to be made to handle wildcard characters,
batch file abilities need to be added, etc.
I don't know that it will ever be finished, but it's an interesting
program, and a lot of work has gone into it. It wasn't meant to be
radically different
from the DOS interpreter - just an alternative.
dos-man