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:

    “The North will at least preserve your flesh for you; Northerners are pale for good and all. There’s very little difference between a dead Swede and a young man who’s had a bad night. But the Colonial is full of maggots the day after he gets off the boat.”
    —Louis-Ferdinand Céline (1894–1961)

    “The Modernist’s command was Pound’s “Make it New.” The postmodern imperative is “Get it Used.” The more used the better.”
    —Andrei Codrescu (b. 1946)

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