Talk:Bad command or file name

Untitled
This article was proposed for deletion. See Votes for deletion/Bad command or file name for a record of the votes and discussion; the result was a lack of consensus to delete. Postdlf 23:10, 10 Feb 2005 (UTC)

God damn it, if Wikipedia deletes one more article, I'm gonna go beserk. I hate coming back to wiki for information only to realize that some snooty jackass deleted the article. I bet you the article count is actually dropping on wiki because of all the snooty jackasses. Keep this article dammit.


 * Well said, anonymous! I added an image of Windows XP error - can someone place it properly, thanks Travis (talk) 05:39, 11 December 2007 (UTC)

Unsourced claim in the beginning of the article
"It is occasionally used as an example of a computer message that is perfectly accurate yet confusing to the average user.{{citation needed|date=March 2015} is an anecdotal, and has no source. Without a source there is no reason for this sentence, as it is not verifiable. We are not here to spread opinions but stick to verifiable fact


 * Sorry, you are right about this one, the message has not entered into common lore. Also the fact that it is accurate yet misleading is already in the text, which is what is interesting about it.

Fair use rationale for Image:Win xp cmd bad command.png
Image:Win xp cmd bad command.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.

Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.

If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.

BetacommandBot (talk) 05:47, 19 December 2007 (UTC)

B4d (0mm& 0r /-1!3 n@m3
Hey! cd HTPR\wikipedia.org\wiki edit Wikipedia:Articals for deletion\BCFN Bad command or file name —Preceding unsigned comment added by 76.79.154.26 (talk) 23:27, 16 July 2009 (UTC)

Edits - March 3

 * Original research tag justification: There is no evidence for paragraph 2, note 2 is NOT a source, and note 2 is a specific example and does NOT represent unices as a whole.
 * Windows NT (and newer): There is no successor to Windows NT family (yet). Windows 10 is still part of the Windows NT family, and so are Windows XP, Vista, and 7.
 * General fixes: Readability improvements were made and some of the unclear antecedents were fixed.
 * Tense changes: I'm not sure what tense guidelines are for WP, but I changed some of the tenses anyway.
 * Note 2 didn't make much sense with the ambiguous pronouns; I (this is a shared IP, so expect vandalism from idiots) fixed up the grammar, but I also don't know much about shells and may have made an incorrect assumption.
 * This article still needs more sources. The Microsoft Knowledge Base may hold reliable sources for the Windows and DOS side of this article. man pages from die.net may help for the *NIX side of this article. — Preceding unsigned comment added by 204.234.74.238 (talk) 16:36, 3 March 2015 (UTC)

Edits - March 5, 2015
98.23.203.121 (talk) 21:05, 17 March 2015 (UTC)
 * "mistyped the first word > "typed an incorrect first word" (fluency)
 * Recent > later (English connotations)
 * "the Windows NT" - Windows NT is a family, and modern English does not need "the" prefixed
 * Yes, MS-DOS spat out the same output for a missing file, since MS-DOS does not distinguish between system commands and files like *nix shells do. (Those who do not learn history are doomed to repeat it.)
 * Mistyped command or unrecognized (nonexistent) command - MS-DOS has the same error for both situations.
 * Like I've stated previously (albeit ambiguously), "because they searched for a file matching the command name and this is the stderror when a file is not found" is clunky English. Everything in *nix is a file, so shell commands were actually executables. ("due to a nonexistent file" covers both shell commands, *nix executables, and data files.) Obviously the  is the first word of the command)" - conflicts w/ Spitzak on 6 Mar 2015
 * The UNIX paragraph needs more sources. Just because tclsh is cited does not indicate other shells have similar messages. bash and tcsh/csh are currently what the majority of OS X and Linux users use, so citing them helps cover "most modern shells" without citing 4 or 5 shells. --Actually, I'm removing the last part of the last sentence until an actual source for tclsh can be cited.
 * TODO: Dump some of the second paragraph into the first paragraph to intro the topic better.
 * @Spitzak: Windows NT is still ambig. on the version when this message was changed; do you have a source that can be cited?
 * @Spitzak: Please watch out for sentence fragments; commas don't join sentences.
 * @Spitzak: "attempt to obfuscate" and "whitewashing" - Please assume good faith. Not everyone vandalizes Wikipedia for fun.
 * @Spitzak: "Bad command or file name" is both ambiguous and misleading. It has a double meaning and gives (the user) the wrong impression. The connotations of ambing. and misleading are about the same. However, I used "clarity" instead to say that the wording was changed to avoid double meanings and that the message wasn't just changed because Microsoft could change it (which goes for a lot of features).


 * I certainly remember Unix doing this but I'm not sure how long ago. It happens if the shell blindly calls perror after not finding the command, since the most likely last failed system call was an attempt to open the file. Tclsh certainly does it still for the "exec" command. I thought it was interesting that the same mistake as MSDOS did was done years earlier in Unix shells.
 * I am basing the "Windows NT" on previous text in this page, I have no citations for it. It may be easier to locate the first version of normal Windows that had command.com altered to produce a different error.
 * I thought it was obvious from the previous text why they changed the message, but, whatever.
 * Generally looks good now, with a small type I'm going to fix now.Spitzak (talk) 04:03, 18 March 2015 (UTC)

MS-DOS Mobile
MS-DOS mobile for the Windows Phone emulates the "Bad command or file name" error message. We should add it to this article sometime to show that this infamous error mesage is still remembered by many :) 75.90.67.169 (talk) 22:22, 1 April 2015 (UTC)
 * Edit: I wasn't joking. This was posted on April 1st but I'm being serious. 98.23.197.224 (talk) 17:28, 6 April 2015 (UTC)