The name specified is not recognized as an internal or external command, operable program or batch file.
It means the installation directory of the specified executable is not defined in the PATH environment variable.
To fix this either modify the command to fully qualify the location of the executable file by including the installation folder details or alternatively, just add the installation folder to the PATH environment variable.
Environment Variables Dialog
The PATH is an environment variable so to add or edit this environment variable you need to bring up the Environment Variables dialog shown below:
NOTE: Be careful when editing the PATH as it is used by Windows itself. In the dialog mentioned above, when possible, it is best to make the changes to the User version, leaving the System version alone.
IMPORTANT: Take extreme care when editing this PATH environment variable. Only add to it. Never delete from it.
Depending on which version of Windows and whether you are using UAC the process of bringing up that Environment Variables dialog will vary.
To get to the Environment Variables dialog use the Start Button, Settings Button, select the About option, select System Info option and finally select the Advance system setting option.
To get to the Environment Variables dialog use the the Start Button, select the Settings, About menu, click on the System icon and in the resulting dialog select the Advance system setting option.
When running UAC the two options above will not work as they will edit the environment variables of the admin user and not the current user.
In this case you will need to instead access the dialog using the Control Panel, User Accounts as shown below:
More Details about the PATH
Windows uses the PATH to look for executable and DLL files. An over simplified version of that search logic is Windows searches the current folder and if the file is not found it continues the search using the directories listed in the PATH, searching the directories in the list in a left to right order. This can sometimes cause issues.
Consider the case where the same executable (or dll) is found in multiple locations and those multiple locations are all in the PATH. The executable or dll in the left most location will be the one that is found and used, even though it might not be the correct one.
These types of issues can be resolved using a Dependency Walker.
To see the current PATH, start Zeus, select the Tools, DOS Command Line menu and in the arguments edit field type the following command:
Code: Select all