The concept of a RAM optimizer is what is bad - not individual products. Actually, to put it more succinctly, they are ineffective.
Windows XP Memory manager already knows how to send items to the pagefile as needed for RAM - it keeps what it needs to in your RAM and gets rid of it if you start a new app that needs more RAM than is currently available. By running a RAM optimizer, you’re increasing the load on the system resources as it will continually try to remove applications from active memory and send them to the pagefile, using more of your HD than is necessary.
Remember, HDs are about 1000 times slower than RAM. You really don’t want stuff paged unless you absolutely have to - and as I mentioned before, Windows XP can take care of that.
If your RAM program is set to always keep a certain amount of RAM free, and all of a sudden WWL runs its download.exe and GetFile.exe programs, there is a good possibility that your RAM optimizer will send them to the page file while they are active in RAM - slowing down the performance of WWL.
After all, the whole point of running WWL is to get live data, or as close to live as you can get. If you slow down that process, you’re slowing down the Live part of the program. And if the program does not receive a response in a timely manner, then it will most likely give you an error.
In your example on how it helped you out - if your computer were truly frozen, you’d never be able to get to your RAM optimizer to run it - so, in effect, you had an app or two frozen, not the entire computer.
Finally, I should have been more concise in my previous post - I did not say uninstall it - I said do not use it - turn it off for a period (say a week) and see how things go.
Also realize this - XP really, really really needs 1 GB of RAM to run efficiently. I understand that not everyone can go out and afford new machines / afford upgrades, but for less than the average tank of gas you can easily make that machine a 1 GB machine or more (if your motherboard will allow it).