Although I have not found a program to help an XP user easily identify programs with memory leakage, I did find the following Web page that describes a method for locating memory leakage:

http://h20015.www2.hp.com/en/document.jhtml?lc=en&docName=bph06569

It is time consuming, but there does not seem to be a simpler method. I did find at least two programs to identify memory leaks in programs while they are being developed, but they are not for the end user. Also, in the aforementioned Web page is a remark that memory leaks are more likely if the user shuts down a program before it is fully loaded for 10 to 20 seconds. I sometimes shut down programs I have begun in error before they have a chance to fully load.

As suggested, I tried a more aggressive memory management program to recapture leaked memory. On the surface it worked good, however, I found that it was moving data to virtual memory so as to release more physical memory. This was counterproductive to increasing performance, so I uninstalled it. I have the virtual min and max memory set equal and low (200MB) to try to force XP to use the 1,024MB of physical memory as much as possible since it is so much faster.

Hope this information is of some use to others.

Tom Mayer
 

               The NOSPIN Group Promotions is now offering
              Mandrake Linux or Red Hat Linux CD sets along
             with the OpenOffice CD...  at a great price!!!
             http://freepctech.com/goodies/promotions.shtml