Commands in command window

  • Thread starter Thread starter MS
  • Start date Start date
M

MS

Whenever I open a command window (DOS box) now, and type a command into it
(even chkdsk), press the Enter key, I always get an error message that the
command doesn't exist, internally or externally.

What happened to my command window functionality? How do I fix this?

Thanks in advance to anyone who can help with this problem.
 
Your PATH is probably messed up. See this.

Why don't my commands work?
http://internet.cybermesa.com/~bstewart/cmdprompt.html#6

Bill Stewart has written a small program called FIXPATH that attempts to fix
these problems.

FIXPATH
http://internet.cybermesa.com/~bstewart/files/fixpath2.zip

"Error! Path value not found in registry!"
The Path value is missing.
FIXPATH will attempt to create the value with the correct data type and
contents.

"Error! The registry value type is not REG_EXPAND_SZ!"
The Path value is the wrong data type. FIXPATH will try to fix this.

"Error! The minimum required directories were not found in the Path!"
The Path value doesn't start with the correct directories. FIXPATH will try
to fix this also.

If FIXPATH.EXE successfully updates the Path value in the registry, you will
need to reboot for the change to take effect.

--
Hope this helps. Let us know.

Wes
MS-MVP Windows Shell/User

In
 
Whenever I open a command window (DOS box) now, and type a command into it
(even chkdsk), press the Enter key, I always get an error message that the
command doesn't exist, internally or externally.

What happened to my command window functionality? How do I fix this?

Thanks in advance to anyone who can help with this problem.
Click to expand...

It's not a DOS box. There is no DOS in Windows XP.
 
The OP gave the correct name, then a handy easy name. If he (or I) want to
call it a DOS box, what's the problem?

If it looks like a DOS box and it quacks like a DOS box......

Val
 
Val said:
The OP gave the correct name, then a handy easy name. If he (or I)
want to call it a DOS box, what's the problem?
Click to expand...


The problem is that wrong names for things gives you wrong ideas about what
their capabilities are.

However if you don't care and want to call it by a misleading name, feel
free to do so.
 
The OP gave the correct name, then a handy easy name. If he (or I) want
to call it a DOS box, what's the problem?

If it looks like a DOS box and it quacks like a DOS box......
Click to expand...

.....that doesn't mean it's DOS box. Why? Because it's ..well ...not.
Whether you care about correct terminology or not, there are others who read
this newsgroup who might not know. It's a misconception by some about DOS
being in XP. My reply was to clarify that for others.
 
Rock said:
....that doesn't mean it's DOS box. Why? Because it's ..well ...not.
Whether you care about correct terminology or not, there are others
who read this newsgroup who might not know. It's a misconception by
some about DOS being in XP. My reply was to clarify that for others.
Click to expand...


Yes, and if I may add to that, there's more involved here than just caring
about correct terminolgy. If you don't understand what something really is,
your expectations about what it does and what you can do there will be wrong
(at least some of the time).
 
Back
Top