Bad command or file name
COMMAND.COM, the primary user interface of MS-DOS, produces this error message when the first word of a command could not be interpreted. For MS-DOS, this word must be the name of an internal command, executable file or batch file, so the error message provided an accurate description of the problem but easily confused novices. Though the source of the error was often a mistyped command, the wording gave the impression that files named in later words were damaged or had illegal filenames. 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" for the same reasons. Most modern shells produce an error message similar to "foo: command not found".
- Jim Cooper, (2002). Using MS-DOS 6.22. Que Publishing. ISBN 9780789725738
- "Instructions:". MSDN. Microsoft. Retrieved March 8, 2015.
- Harry Phillips, Eric Skagerberg, (2002). "New Perspectives on Microsoft Windows 2000 MS-DOS Command Line, Comprehensive, Windows XP Enhanced". Cengage Learning. ISBN 1285963679
- "execute_cmd.c - bash.git - bash". git.savannah.gnu.org. Retrieved 2018-11-17.
- "main.c\src - dash/dash.git - DASH Shell". git.kernel.org. Retrieved 2018-11-17.
- "zsh-users/zsh". GitHub. Retrieved 2018-11-17.