In this article, the topic of Bad command or file name will be addressed from different perspectives, analyzing its importance, impact and relevance in today's society. Various aspects related to Bad command or file name will be explored, as well as its implications at a social, cultural, economic and political level. Throughout the article, different opinions and points of view will be presented, with the aim of offering a comprehensive and enriching vision about Bad command or file name. In addition, possible solutions and initiatives will be examined to address the challenges that Bad command or file name poses, in order to encourage dialogue and reflection around this topic.
![]() | The topic of this article may not meet Wikipedia's general notability guideline. (September 2022) |
"Bad command or file name" is a common and ambiguous error message in MS-DOS.[1]
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,[2] 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):[3]
"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".[4][5][6]