PillarSoft Utilities

Copyright 2001 - 2003, PillarSoft

 


Disclaimer

The utilities contained in this archive are free for private use and not supported in any way. To make them available at any time from a command line, they should be copied (along with their help file) into any directory listed in your PATH statement or read Consider The Following below.



Program Descriptions

Note: This file (ps_util.htm) must be located in the same directory as the utility help (htm) files for the links to work properly.


Name Description

crlf

Convert LF to CRLF or vice versa on any selected file.
 
dc (Directory Change) changes directories at the command line (like cd) using aliases.
 
ff Find Files by name (or wildcard) on any drive, tree or individual directory.
 
rt Replace Text replaces any string with a new string in selected file(s). May use wildcards for file lists and do complex search and replace operations.
 
slp Search LibPath searches the LIBPATH for DLL files. Handy for for loading order inquiries.
 
sp Search Path searches the SET PATH statement for file(s) as opposed to searching drives or directories.
 


Each of the utilities come with html documentaion that can be started from the program itself. The html file must be located in the same directory as the exe that it documents for the utility to be able to start a viewer for it. Each program searches for a browser to open the Help file with according to the list provided below. This was done to be able to use WebExplorer when available because it is so light (starts quickly). You may also have the option of starting the System Default browser in which case it will start Mozilla, Netscape or whatever is the system default at the time.

Order of search for browsers:


Consider The Following...

After installing a few applications one always runs up against the dreaded mess that our path statements become. Rather than letting every application add to it why not set up a directory for new applications dll and help files and have just the one extra entry for each of these. While we are at it, we can create an "app" directory for 1 or 2 file applications that we may want to use from the command line. Granted, you will not want to copy some larger apps with numerous files into these directories but the smaller apps will use them quite nicely and in a more organized fashion. Suppose I make a "BIN" directory on the root of my boot drive and add directories under it for apps, dlls and help. So I have: Now I can add these directories to the "Set Path", "Libpath" and "Set Help" statements respectively and when I install an application that wants to add to my "Libpath" statement, for example, I can tell the app not to update my "Config.sys" or remove the additional entry it may have made to my "Libpath" statement. Then I can copy all the apps dll's into the C:\bin\dll directory and I'm all set! Another benefit is that anytime I copy files into these directories they are available immediately to the system without having to reboot.

This method is:

 


Copyright 2001 - 2003, PillarSoft
All Rights Reserved