Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Missing DOS commands on windows 2003 server

1 view
Skip to first unread message

star...@gmail.com

unread,
May 25, 2005, 9:45:53 AM5/25/05
to
I opened up a command window on a Windows 2003 server yesterday and
found that simple commands like DIR and CD where resulted in a "'dir'
is not recognized as an internal or external command,
operable program or batch file."

I suspect something has gotten screwed up with the path or a similar
system setting, can somebody let me know what a generic windows 2003
install path statement looks like -- or tell me what folder I need to
include -- or tell me that I am completely wrong and tendor another
solution :D

This through me - I thought these commands where generic and included
within cmd itself.

Drummer

unread,
May 25, 2005, 10:18:05 AM5/25/05
to
Very interesting. I've got the exact same problem going right now.
I'm missing all of the shell commands and it just started a few days
ago. I think I applied a critical update right around the same time as
well.

And now my Oracle server isn't running.

Jerold Schulman

unread,
May 25, 2005, 10:31:54 AM5/25/05
to


Sounds like your Path environment variable is messed up.

At a minimum, it should be
Path=C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32\Wbem

Pegasus (MVP)

unread,
May 25, 2005, 11:28:16 AM5/25/05
to

<star...@gmail.com> wrote in message
news:1117028753.5...@g49g2000cwa.googlegroups.com...

Commands such as cd, dir, del are internal commands, as you suspect.
They are included in cmd.exe and do not require a path. Perhaps %cmdspec%
is corrupted - it should point at c:\windows\system32\cmd.exe. What
happens when you launch command.com instead? (This is a band-aid
solution only - command.com is a legacy 16-bit command processor!).
And by the way - there is no DOS under Windows server. DOS is an
operating system, same as Unix.


Henrik

unread,
May 25, 2005, 12:26:46 PM5/25/05
to
This might be a nonsens suggestion, but I seem to remember that the SP1
Security and Configuration Wizard had a setting to disable all 16-bit
programs. I might be wrong about this beeing an option though, and I'm to
lazy to check my configs.
If this happens in the default configuration which Windows suggests as
stardard, it might have caused to DOS tools to no longer function, perhap?

Does all of you which this has happened to, perhaps run SP 1, and have also
installed the SCW and run it?

// Henrik


"Pegasus (MVP)" <I....@fly.com> wrote in message
news:e2EZh5TY...@TK2MSFTNGP12.phx.gbl...

0 new messages