Bad Command Or File Name

COMMAND.COM produces this error message when the first word of a command could not be interpreted. Because this word must be the name of an internal command, executable file or batch file, the error message provided an accurate description of the problem, but easily confused novices. The wording gave the impression that filenames provided as arguments to the commands were damaged or invalid. Later, the wording of the error message was changed for clarity. Windows NT displays the following error message instead (where "foo" is replaced by the word causing error):

"foo" is not recognized as an internal or external command,
operable program or batch file.

Some early Unix shells produced the equally cryptic "foo: no such file or directory" again accurately describing what is wrong but confusing users. Most modern shells produce an error message similar to "foo: command not found".

• Abort, Retry, Fail?
• List of DOS commands