Windows Batch Files a.k.a. Command Procedures
This branch of the tree contains Windows command procedures I've written over the years to expedite operations or sequences of operatations I need to do frequently when working on Windows systems.
The procedures have been tested on Windows XP and Windows 7. Even though Windows now has more powerful command shells these procedures are all written in the original Windows (and, to some extent, DOS) command language so they should be more widely portable.
It is my intention, as time permits to translate the more useful of these command procedures to Unix shell procedures (if they would be helpful on Unix).
The PATH Variable
Note that all of these procedures assume you invoke them with just their filename. In other words, they expect to be somewhere on the Windows environment PATH variable.
On my systems I usually put C:\bin somewhere on the PATH. The way to this varies between Windows operating systems. Here are some general instructions.
Right-click My Computer and select Properties.
Select the Environment page.
In the System Properties window, click on the Advanced tab.
In the Advanced Systems Settings section, click the Environment Variables button.
In the System Variables area, click on the current path.
Add the new path to the place you want it, followed by a semicolon. For example, if you want to add C:\bin to the path, add the string C:\bin; immediately after the semicolon of the directory you want it to follow. Note that the last directory in PATH need not be followed by a semicolon. If you want to put C:\bin and the end of the PATH make insert a semicolon after the formerly end of the path, if necessary.
Click Apply or OK; the changes take effect immediately.
Note that you can modify the User variables instead of System, but then the changes will affect only you. However, if you do not have administrative access to your system this may be the only choice available (I've not tested this).
Caution: there are lots of web pages that will give you instructions on changing the PATH. One web page I came across had a minor error. It said that if you want to add the current directory to your path and ;. to the end of the path. While this may be true, I've found that the current directory is ALWAYS first on the PATH whether or not it is specified in the environment variable.
Procedures than generate other procedures
Some of these command procedures can generate other command procedures (see pd.cmd). In this case the new command procedure will be created in the same directory as the original procedure that generated it. So it is important that you have write permission to that directory.