OK, I'll say this again, but be more specific, (and wordy)
ram that you have not used IS available...period.
even if it is still available to the program, since the program has not used this ram, it is marked as available for new use, and it is as available as if the program wasn't even running.
this ram does not appear in counters, because the counter only recognizes ram that is not involved in anything...this uninvolved ram is no more available then ram that XP has marked for use.
when an optimizer releases ram, it is releasing ram that is already released.
further, ram optimizers can and will also release ram that has been accessed recently...in other words, ram you are using becomes unusable for that particular process..yes, of course a program might load faster because you did this, but it is at the expense of an activity you are also currently involved with.
in addition, the very act of releasing the ram will slow you up enough to invalidate any claims of performance, even if they were true, which they are not.
any performance gain you might see is at the expense of a performance degradation within an activity that you are currently involved.
as far as releasing the dlls, the dlls that are not in use are already written to disc, any dll not written to the pagefile is in use...all others are written to disc, and the ram is already to be released, they are available for all use, in addition, they are available for native use, if such is called before new use.
as I said, you can only trade performance in this regard, you cannot gain performance.
and the trade will extract a severe dividend in your total performance.
