Command-line 'Where' Tool

Environment: Windows NT 4 SP6, Visual C++ 6 SP3

For a while, I've wished for tool that worked like the csh unix command, where. I.e. a tool to display where an executable is found in the search path. Finally, I wrapped the SearchPath API call in a command-line where utility. I added a couple of options to show version information. Here's the usage:

C:\>where
Usage: where [-v] [-x] [-s] [-d] <executable file>

Finds the file using the rules specified by the SearchPath 
API method:
  1. The directory from which the application loaded.
  2. The current directory.
  3. The Windows system directory.
  4. [Windows NT/2000] The 16-bit Windows system directory.
  5. The Windows directory.
  6. The directories that are listed in the PATH environment variable.
It uses .exe, .com, and .cmd as default file types if none is specified. See the documentation for the SearchPath API for more details. Options: -v Show version info -x Show extended version info -s Save command line settings (or lack of) as default -d Reset default command line settings

Downloads

Download source and exe - 53 Kb


Comments

  • There are no comments yet. Be the first to comment!

Leave a Comment
  • Your email address will not be published. All fields are required.

Top White Papers and Webcasts

  • On-demand Event Event Date: December 18, 2014 The Internet of Things (IoT) incorporates physical devices into business processes using predictive analytics. While it relies heavily on existing Internet technologies, it differs by including physical devices, specialized protocols, physical analytics, and a unique partner network. To capture the real business value of IoT, the industry must move beyond customized projects to general patterns and platforms. Check out this webcast and join industry experts as …

  • Today's agile organizations pose operations teams with a tremendous challenge: to deploy new releases to production immediately after development and testing is completed. To ensure that applications are deployed successfully, an automatic and transparent process is required. We refer to this process as Zero Touch Deployment™. This white paper reviews two approaches to Zero Touch Deployment--a script-based solution and a release automation platform. The article discusses how each can solve the key …

Most Popular Programming Stories

More for Developers

RSS Feeds