Archived from groups: microsoft.public.windowsxp.general,microsoft.public.windowsxp.help_and_support (
More info?)
You don't actually know a tweak as it only applies to windows earlier than 2000 - NT4, Win95 and 98. And it only applied to explorer.
Unloading the DLL
The Shell automatically unloads a DLL when its usage count is zero, but only after the DLL has not been used for a period of time. This inactive period might be unacceptably long at times, especially when a Shell extension DLL is being debugged. For operating systems prior to Windows 2000, you can shorten the inactive period by adding the following information to the registry.
HKEY_LOCAL_MACHINE
Software
Microsoft
Windows
CurrentVersion
Explorer
--
--------------------------------------------------------------------------------------------------
http://webdiary.smh.com.au/archives/_comment/001075.html
=================================================
"R. McCarty" <PcEngWork-NoSpam_@mindspring.com> wrote in message news:eXUz55BpFHA.496@TK2MSFTNGP10.phx.gbl...
> What memory count are you watching decrement to Zero ?
> Which applications ? How much physical memory does your
> system have available to it ?
>
> Your issue(s) may be more related to the applications than
> the OS. XP's memory management handles almost every kind
> of loading very well. As far as I know, there is only a single
> tweak that modifies relinquishing memory after the program.
> It's a memory management key AlwaysUnloadDLL - but I
> doubt that it would resolve your issue.
>
> "HotRod" <NOSPAM@youremail.com> wrote in message
> news:O9HM6yBpFHA.2904@TK2MSFTNGP12.phx.gbl...
>>I have an XP pro machine that takes forever to release memory. I have
>>several applications that when they need over 100 MB seem to hang the
>>system, when I open task manager I can literally watch the memory count
>>slowly back down to zero. Is there anyway to solve this problem.
>>
>
>