Bad_command_or_file_name Bad_command_or_file_name

Bad command or file name - Definition and Overview
Related Words: Cobol, Fortran, Ability, Acme, Address, Administer, Administration, Animus, Appetite, Artistry, Ask, Assembler, Assurance

A request has been made on Wikipedia for this article to be deleted in accordance with the deletion policy.

This request is being discussed to form a consensus whether this is, or could be, an article appropriate for Wikipedia. Please see this page's entry on the votes for deletion page for details. Also see possible outlets for removed articles. If you feel deletion is not justified by Wikipedia deletion policy you may vote against its deletion. Please do not remove this notice or blank this page while the question is being considered. However, you are welcome to continue editing this article and improve it, especially if you can address the concerns of those who believe the article should be deleted.


Bad command or file name was an infamous error message on Microsoft's MS-DOS operating system.

It was the same as a "Syntax error" message on BASIC interpreters of the 1980's, and both resulted from mistyping a command or the path to the file being loaded is incorrect.

Novices had trouble understanding the message, so in later versions it was changed to "'xyz' is not recognized as an internal or external command, operable program or batch file."


Gnome-system.png 		 This computing-related article is a stub. You can help Wikipedia by expanding it (http://www.wordiq.com/definition/Bad_command_or_file_name).

Example Usage of command
trillian: I know it's too early in the morning when even the mv command foils me.
stevenmaxson: Charlie taking command of the Pride of Bruges http://www.flickr.com/photos/ftconline/4061088047/
35ozNin: now i command you niggas to get money
Copyright 2009 WordIQ.com - Privacy Policy  :: Terms of Use  :: Contact Us  :: About Us
This article is licensed under the GNU Free Documentation License. It uses material from the this Wikipedia article.