Bad command or file name: Difference between revisions
Added short description |
You will review your payment details on Google Pay before completing your order. |
||
| Line 1: | Line 1: | ||
{{Short description|MS-DOS error}} | {{Short description|MS-DOS error}} | ||
{{Notability|date=September 2022}}[[File:Bad command or file name.PNG|thumb|Screenshot of the error in MS-DOS]] | {{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 | '''"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>}} | [[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>}} | ||
Latest revision as of 09:34, 18 September 2025
Script error: No such module "Unsubst".
"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]Template:Quote
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]
See also
References
<templatestyles src="Reflist/styles.css" />
- ↑ Jim Cooper, (2002). Using MS-DOS 6.22. Que Publishing. Template:ISBN
- ↑ Script error: No such module "citation/CS1".
- ↑ Harry Phillips, Eric Skagerberg, (2002). "New Perspectives on Microsoft Windows 2000 MS-DOS Command Line, Comprehensive, Windows XP Enhanced". Cengage Learning. Template:ISBN
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
- ↑ Script error: No such module "citation/CS1".
Script error: No such module "Check for unknown parameters".