Frank,
Microsoft operating systems get confused by R:Base for DOS.
R:Base starts out looking like a 16-bit DOS program, which would
typically use COMMAND.COM, but then switches to 32bit protected
mode by running DOS4GW.EXE. So you can zip to either CMD.EXE
(note the spelling), the 32-bit native NT/W2K command processor, or
its 16-bit baby brother COMMAND.COM.
Open a "command prompt" and type
SET | MORE
You will see that COMSPEC is set to CMD.EXE
Then, at the command prompt, type
COMMAND.COM
When you get back to a prompt, type again:
SET | MORE
and you'll see that the comspec is different, and there may be some
other differences in environment variables that are not used in
COMMAND.COM but that are used in CMD.EXE.
syntax and options are slightly different between the two, so,
depending on what the "whatever" is on your command line, you may
actually prefer to launch CMD.EXE rather than COMMAND.COM. Both
command processors should start from R:Base for DOS.
Bill
On Tue, 25 Sep 2001 18:29:17 -0700, Frank Radice wrote:
>Is the ComSpec correct? Why does it have COMMAND.COM?
Should it be
>CMD.COM? Is this or can this cause a problem?
