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:

    “Minute after minute, aeon after aeon,
    Nothing lets up or develops.
    And this is neither a bad variant nor a tryout.
    This is where the staring angels go through.
    This is where all the stars bow down.”
    —Ted Hughes (b. 1930)

    “Universal empire is the prerogative of a writer. His concerns are with all mankind, and though he cannot command their obedience, he can assign them their duty. The Republic of Letters is more ancient than monarchy, and of far higher character in the world than the vassal court of Britain.”
    —Thomas Paine (1737–1809)

    “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)