Bad command or file name
"Bad command or file name" is a common error message in MS-DOS and some other operating systems.[1] It is occasionally used as an example of a computer message that is perfectly accurate yet confusing to the average user[citation needed].
COMMAND.COM produced the message "Bad command or file name" when the first word of a command could not be interpreted. For MS-DOS, the first word of a command was the name of an internal command, executable file or batch file,[2] 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; both OS/2[citation needed] and Windows NT have replaced the message with the following (where "foo" is replaced by the word causing error):[3]
<templatestyles src="Template:Blockquote/styles.css" />
"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".[4][5]
See also
References
<templatestyles src="Reflist/styles.css" />
Cite error: Invalid <references> tag; parameter "group" is allowed only.
<references />, or <references group="..." /><templatestyles src="Asbox/styles.css"></templatestyles>
- ↑ Jim Cooper, (2002). Using MS-DOS 6.22. Que Publishing. ISBN 9780789725738
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Harry Phillips, Eric Skagerberg, (2002). "New Perspectives on Microsoft Windows 2000 MS-DOS Command Line, Comprehensive, Windows XP Enhanced". Cengage Learning. ISBN 1285963679
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
- ↑ Lua error in package.lua at line 80: module 'strict' not found.
