"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:
“Too bad that all the people who know how to run the country are busy driving taxicabs and cutting hair.”
—George Burns (b. 1896)
“An actor must communicate his authors given messagecomedy, tragedy, serio- comedy; then comes his unique moment, as he is confronted by the looked-for, yet at times unexpected, reaction of the audience. This split second is his; he is in command of his medium; the effect vanishes into thin air; but that moment has a power all its own and, like power in any form, is stimulating and alluring.”
—Eleanor Robson Belmont (18781979)
“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?)