"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
Some early Unix shells produced the equally-cryptic (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 .
Famous quotes containing the words bad, command and/or file:
“The Harmless Torturers. In the Bad Old Days, each torturer inflicted severe pain on one victim. Things have now changed. Each of the thousand torturers presses a button, thereby turning the switch once on each of the thousand instruments. The victims suffer the same severe pain. But none of the torturers makes any victims pain perceptibly worse.”
—Derek Parfit (b. 1943)
“I at least have so much to do in unravelling certain human lots, and seeing how they were woven and interwoven, that all the light I can command must be concentrated on this particular web, and not dispersed over that tempting range of relevancies called the universe.”
—George Eliot [Mary Ann (or Marian)
“While waiting to get married, several forms of employment were acceptable. Teaching kindergarten was for those girls who stayed in school four years. The rest were secretaries, typists, file clerks, or receptionists in insurance firms or banks, preferably those owned or run by the family, but respectable enough if the boss was an upstanding Christian member of the community.”
—Barbara Howar (b. 1934)