Bad Command or File Name

"Bad command or file name" is a common error message in Microsoft's MS-DOS and some other operating systems.

In command.com, the message Bad command or file name is produced if the user mistypes the first word of a command line. This first word must be either the name of a built-in "command", or of an executable file or batch file. Therefore the error was printing what, to the programmer, was an accurate description of the problem: there was no such command and there was no such file. Novices, in general, had trouble understanding the message, so later operating systems changed it; for instance, OS/2 and the Windows NT (and newer) family use is not recognized as an internal or external command, operable program or batch file.

Some early Unix shells produced the equally-cryptic : no such file or directory (because they searched for a file matching the command name and this is the strerror when a file of a given name is not found). Most modern shells produce : Command not found.

Famous quotes containing the words bad, command and/or file:

    “It was evident that, both on account of the feudal system and the aristocratic government, a private man was not worth so much in Canada as in the United States; and, if your wealth in any measure consists in manliness, in originality and independence, you had better stay here. How could a peaceable, freethinking man live neighbor to the Forty-ninth Regiment? A New-Englander would naturally be a bad citizen, probably a rebel, there,—certainly if he were already a rebel at home.”
    —Henry David Thoreau (1817–1862)

    “By his command these words are cut:
    Cast a cold eye
    On life, on death.
    Horseman, pass by!”
    —William Butler Yeats (1865–1939)

    “I have been a soreheaded occupant of a file drawer labeled “Science Fiction” ... and I would like out, particularly since so many serious critics regularly mistake the drawer for a urinal.”
    —Kurt Vonnegut, Jr. (b. 1922)