"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:
“There is no teaching until the pupil is brought into the same state or principle in which you are; a transfusion takes place; he is you, and you are he; then is a teaching; and by no unfriendly chance or bad company can he ever lose the benefit.”
—Ralph Waldo Emerson (18031882)
“If you are the Son of God, command these stones to become loaves of bread.”
—Bible: New Testament, Matthew 4:3.
Tempter to Jesus.
“A common and natural result of an undue respect for law is, that you may see a file of soldiers, colonel, captain, corporal, privates, powder-monkeys, and all, marching in admirable order over hill and dale to the wars, against their wills, ay, against their common sense and consciences, which makes it very steep marching indeed, and produces a palpitation of the heart.”
—Henry David Thoreau (18171862)