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:

    Unpleasant questions are being raised about Mother’s Day. Is this day necessary? . . . Isn’t it bad public policy? . . . No politician with half his senses, which a majority of politicians have, is likely to vote for its abolition, however. As a class, mothers are tender and loving, but as a voting bloc they would not hesitate for an instant to pull the seat out from under any Congressman who suggests that Mother is not entitled to a box of chocolates each year in the middle of May.
    Russell Baker (20th century)

    Children from humble families must be taught how to command just as other children must be taught how to obey.
    Friedrich Nietzsche (1844–1900)

    Probably nothing in the experience of the rank and file of workers causes more bitterness and envy than the realization which comes sooner or later to many of them that they are “stuck” and can go no further.
    Mary Barnett Gilson (1877–?)