Bill in Co. wrote:

> Colon Terminus wrote:
>
>>"John John (MVP)" <audetweld@nbnet.nb.ca> wrote in message
>>news:O6TfJvcuIHA.3792@TK2MSFTNGP02.phx.gbl...
>>
>>>Bill in Co. wrote:
>>>
>>>>PD43 wrote:
>>>>
>>>>
>>>>>"Bill in Co." <not_really_here@earthlink.net> wrote:
>>>>>
>>>>>
>>>>>
>>>>>>Has anyone played around with this extensively to know just what DOS
>>>>>>applications "command.com" (16 bit shell) will run successfully, that
>>>>>>"cmd.exe" (32 bit shell) cannot (under XP)?
>>>>>>
>>>>>>Note: "cmd.exe" is newer and more "featured", of course (and also
>>>>>>handles
>>>>>>long filenames), but isn't quite as compatible for running some DOS
>>>>>>apps.
>>>>>>
>>>>>>Just wondering if anyone has any personal experiences they can share
>>>>>>on
>>>>>>this. I seem to have noticed a few already, but was curious.
>>>>>>
>>>>>
>>>>>Google (it's your friend) "XP command line commands"
>>>>>
>>>>>First reference listed:
>>>>>
>>>>>http://www.ss64.com/nt/
>>>>
>>>>
>>>>Did you READ what I wrote? I have already *read* a bit about it, know
>>>>the differences, and have worked with both of them, but I wanted to hear
>>>>some case histories (as I WROTE) of what some had found they had
>>>>incidents with (i.e., not running well on CMD.EXE, but running well
>>>>under
>>>>COMMAND.COM).
>>>
>>>You need to do more reading. The version of Command.com that ships with
>>>NT versions is not the same thing at all as the MS-DOS/Windows 9x
>>>version.
>>>The NT version of Command.com only runs inside the NT Virtual Dos Machine
>>>(NTVDM) and only has a few internal commands, these internal commands are
>>>used to configure the DOS subsystem from the Config.nt or Autoexec.nt
>>>files, or they are only accepted for compatibility with files from
>>>MS-DOS.
>>>The Config.nt and Autoexec.nt files are processed when Command.com is
>>>launched. The Command.com internal configuration commands are:
>>>
>>>BUFFERS, COUNTRY, DEVICE, DEVICEHIGH, DOS, DOSONLY, DRIVEPARM,
>>>ECHOCONFIG,
>>>FCBS, FILES, INSTALL, LOADHIGH, LASTDRIVE, NTCMDPROMT, SHELL, STACKS, and
>>>SWITCHES
>>>
>>>Any other commands run by Commmand.com are actually run by Cmd.exe. The
>>>NT version of Command.com prepares and passes all of the commands it
>>>receives to Cmd.exe for execution, that is why the two CLI's appear
>>>seemingly to be able to run the same commands, they are because Cmd.exe
>>>runs the commands for Command.com so in fact Command.com can take
>>>advantage of the commands available with Cmd.exe.
>>>
>>>If you want to observe the use of Cmd.exe by Command.com start the the
>>>Task Manager and then launch Command.com and you will see the NTVDM start
>>>in the Task Manager, you will not see Command.com. Now, give a bit of
>>>work to the Command.com 16-bit processor and keep an eye on the Task
>>>Manager and you will see Cmd.exe appear and then disappear when it
>>>executes the command it received from Command.com. If the amount of work
>>>to do is too little you won't see CMD.EXE appear in the Task Manager, the
>>>work will be over before Task Manager responds. A good command to run to
>>>see this would be the DIR /s command from the root folder:
>>>
>>>cd\
>>>dir /s
>>>
>>>The dir/s command will list all the files on the volume, to stop the
>>>output of the dir /s command press Ctrl+Break.
>>>
>>>John
>>
>>Finally an intelligent, understandable answer to the OP's query.
>>Thank you John John.
>
>
> Indeed, and I thank him again.

You are both welcome.

John