Dos commands not working

  • Thread starter Thread starter Mark
  • Start date Start date
M

Mark

I have several XP workstations that are not processing dos
commands. Only dir and cd are currently working. The
autoexec.nt and config.nt are fine. Checked command.com
file, wow*.* files and NTVDM.exe and they match my own
files in size and date. Has anyone come across this?
 
Can you please specify exactly which command are you trying to run that is
giving you the problem?
 
Mark said:
I have several XP workstations that are not processing dos
commands. Only dir and cd are currently working. The
autoexec.nt and config.nt are fine. Checked command.com
file, wow*.* files and NTVDM.exe and they match my own
files in size and date. Has anyone come across this?

Is the path set correctly?
Chris
 
Mark said:
I have several XP workstations that are not processing dos
commands. Only dir and cd are currently working. The
autoexec.nt and config.nt are fine. Checked command.com
file, wow*.* files and NTVDM.exe and they match my own
files in size and date. Has anyone come across this?

Hi

Take a look here (most likely the Reg_Expand_Sz vs. Reg_Sz type setting in
registry caused by a rough 3rd party install):

http://home.comcast.net/~stewartb/cmdprompt.html#6
 
I had seen comspec set when I was at a command prompt,
which I had noted initially. When I was checking
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session
Manager\Environment for the path entry I noticed ComSpec
was missing there. I went back into the system properties
and added ComSpec=%systemroot%\system32\cmd.exe. Dos
commands then worked. Thanks for the input! :-)
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Back
Top