MSDOS command to check existance of command and exit batch if failed

<command> >NUL 2>&1 || ( echo <Command> not found. Please install <command> or check PATH variable! & pause & exit )
This is a command to be used inside of MS-DOS batch files to check existence of commands as preconditions before actual batch processing can be started. If the command is found, batch script continues execution. If not, a message is printed on screen, script then waits for user pressing a key and exits. An error message of the command itself is suppressed for clarity purpose.
Sample Output
bash --version >NUL 2>&1 || ( echo Bash not found. Please install cygwin or check PATH variable! & pause & exit )

Bash not found. Please install cygwin or check PATH variable!
Press any key to continue . . .

By: Marco
2011-03-07 14:27:42

What Others Think

commandlinefu - commandl line for UNIX
RanyAlbeg · 585 weeks ago
Hey RanyAlbeg, why do you rate me down, only because YOU are expecting UNIX only commands? FAQ doesn't restrict this website to UNIX only commands. There are also other non UNIX only commands, like sqlite or git commands.
Marco · 584 weeks and 6 days ago
Here they have shared the MSDOS command to check the existence of command and exit batch if failed. cbd products Everything is very well explained in it. Thanks a lot for the information you have shared here which is so helpful to understand the code
Kaitlyn · 61 weeks and 2 days ago
Here in this post, we can see the details regarding MSDOS command to check existence of command CBD facts and exit batch if failed. The details of the command are mentioned here and I am looking here for more details on that. These kinds of websites are very much useful for students to learn such languages.
Alyssalauren · 49 weeks and 3 days ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this? is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands

Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.


Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: