NTCMDPROMPT command in XP's CONFIG.NT file

[Larry__Weiss]

Does the NTCMDPROMPT command in XP's CONFIG.NT file have any effect?

I'm trying to get the system to always use CMD.EXE (instead of COMMAND.COM)
for all command line processing, and I expected NTCMDPROMPT to do that for
me. I don't see that happening after I add NTCMDPROMPT to CONFIG.NT.

- Larry Weiss

 

[Rick \Nutcase\ Rogers]

Hi,

Config.nt only applies to 16-bit processes. Cmd.exe is for 32-bit,
command.com is used for 16-bit processes. Why are you trying to do this?

--
Best of Luck,

Rick Rogers, aka "Nutcase" - Microsoft MVP

Associate Expert - WindowsXP Expert Zone

Windows help - www.rickrogers.org

 

[David Candy]

The system does use cmd.exe for all command line processing.

 

[Larry__Weiss]

Config.nt only applies to 16-bit processes. Cmd.exe is for 32-bit,
command.com is used for 16-bit processes. Why are you trying to do this?

After executing some 16-bit programs, the command window is stuck in a
short-file-name mode with non-scrollable content. I was under the
impression that asserting NTCMDPROMPT would prevent that from happening.

- Larry Weiss