Open main menu
Home
Random
Recent changes
Special pages
Community portal
Preferences
About Wikipedia
Disclaimers
Incubator escapee wiki
Search
User menu
Talk
Dark mode
Contributions
Create account
Log in
Editing
Bad command or file name
(section)
Warning:
You are not logged in. Your IP address will be publicly visible if you make any edits. If you
log in
or
create an account
, your edits will be attributed to your username, along with other benefits.
Anti-spam check. Do
not
fill this in!
{{Short description|MS-DOS error}} {{Notability|date=September 2022}}[[File:Bad command or file name.PNG|thumb|Screenshot of the error in MS-DOS]] '''"Bad command or file name"''' is a common and ambiguous [[error message]] in [[MS-DOS]].<ref>Jim Cooper, (2002). ''Using MS-DOS 6.22''. Que Publishing. {{ISBN|9780789725738}}</ref> [[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]],<ref>{{cite web|url=https://msdn.microsoft.com/en-us/library/cc750871.aspx|title=Instructions|work=[[MSDN]]|date=20 February 2014 |publisher=[[Microsoft]]|accessdate=March 8, 2015|archive-date=June 30, 2018|archive-url=https://web.archive.org/web/20180630214310/https://msdn.microsoft.com/en-us/library/cc750871.aspx|url-status=live}}</ref> 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):<ref>Harry Phillips, Eric Skagerberg, (2002). "New Perspectives on Microsoft Windows 2000 MS-DOS Command Line, Comprehensive, Windows XP Enhanced". Cengage Learning. {{ISBN|1285963679}}</ref>{{Quote|<samp>"foo" is not recognized as an internal or external command,<br>operable program or batch file.</samp>}} Some early [[Unix shell]]s produced the equally cryptic "<samp>foo: no such file or directory</samp>" again accurately describing what is wrong but confusing users. Most modern shells produce an error message similar to "<samp>foo: command not found</samp>".<ref>{{Cite web |title=bash - execute_cmd.c |url=https://git.savannah.gnu.org/cgit/bash.git/tree/execute_cmd.c?id=9439ce094c9aa7557a9d53ac7b412a23aa66e36b#n5586 |access-date=2022-04-12 |website=git.savannah.gnu.org |language=en}}</ref><ref>{{Cite web |title=dash - main.c |url=https://git.kernel.org/pub/scm/utils/dash/dash.git/tree/src/main.c?id=057cd650a4edd5856213d431a974ff35c6594489#n318 |access-date=2022-04-12 |website=git.kernel.org |language=en |archive-date=2022-04-12 |archive-url=https://web.archive.org/web/20220412213943/https://git.kernel.org/pub/scm/utils/dash/dash.git/tree/src/main.c?id=057cd650a4edd5856213d431a974ff35c6594489#n318 |url-status=live }}</ref><ref>{{Cite web |title=zsh - exec.c |url=https://github.com/zsh-users/zsh/blob/06e5ec914fdedac6446e02c9427a1706dda9c505/Src/exec.c#L763 |access-date=2022-04-12 |website=GitHub |language=en |archive-date=2022-05-21 |archive-url=https://web.archive.org/web/20220521092027/https://github.com/zsh-users/zsh/blob/06e5ec914fdedac6446e02c9427a1706dda9c505/Src/exec.c#L763 |url-status=live }}</ref>
Edit summary
(Briefly describe your changes)
By publishing changes, you agree to the
Terms of Use
, and you irrevocably agree to release your contribution under the
CC BY-SA 4.0 License
and the
GFDL
. You agree that a hyperlink or URL is sufficient attribution under the Creative Commons license.
Cancel
Editing help
(opens in new window)