Unloading DLL

[trodas]

Prior to Windows 2000 this registry tweak works and removed the DLL from ram "sooner", or almost immediatelly after aplication that load them, closed and there is no use of them anymore:

REGEDIT4

;always unload dll - myth for better memory management, removed
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer]
"AlwaysUnloadDll"="1"

However todays this thing does not work - I hope no-one is using Win95 or Win98...

http://mywebpages.comcast.net/SupportCD/XPMyths.html
"For operating systems prior to Windows 2000, you can shorten the inactive period by adding this registry key."

http://msdn2.microsoft.com/en-us/library/bb776795.aspx
http://support.microsoft.com/kb/196480/en-us


So, this does nothing on WIndows 2000 or XP.
How and is there somewhere specified the time, for witch is the dll kept in memory in Win2k/XP...? And it is editable by regedit or one has to go low-level and user resource hacker or even HEX editor...?

Anyone know?

 

[AsRock]

Been using it for years using TuneXP 1.5 as that has a few nice tweaks

 

[trodas]

I'm much more interesed in registry tweak, to be honest, because it can be easily applied upon reinstall and stored indefinitively, always ready to deploy, etc. Futhermore I would also like to understand things

Not just blindly apply something "recommended" Usualy it is a hoax

 

[AsRock]

I'm much more interesed in registry tweak, to be honest, because it can be easily applied upon reinstall and stored indefinitively, always ready to deploy, etc. Futhermore I would also like to understand things

Not just blindly apply something "recommended" Usualy it is a hoax

http://tacktech.com/display.cfm?ttid=377

TuneXP 1.5 is far far from a hoax app.

 

[trodas]

Well, really?

Well, tell us then, how they do it

I bet they just tweak the myth AlwaysUnloadDLL - other than that, they have to provide time options for the OS how long to wait before removing the DLL from memory, when the usage count reach zero

Run the promoted utility, tickle the option and look out for the AlwaysUnloadDLL in registers. I willing to bet you find it set to "1"

 

[AsRock]

So ?. thats the way it done right ?.. All so that program has other good stuff with it.

There's only 2 programs i use to tweak windows and thats XPTune 1.5 and nLite about all i need to use to get it how i want.

Main reason i use TuneXP is the rearranging boot files which works better for me than MS's program does well with system at least different story with my 3800x2 as both worked good..

 

[trodas]

Well, this is the question - eg. HOW they do it.

Can you tell us? Can you tickle that option and then fire up regedit and search for "AlwaysUnloadDLL" in thre registers and tell us, if found or not...?

 

[Solaris17]

mines set to 1 i use vista manager....how does it not work?

 

[AsRock]

All though this program is old so if MS has changed it since then i don't know. Never really needed any thing else since nLite.

HKEY_LOCAL_HARDWARE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Explorer\AlwaysUnloadDLL\

2 string values ones (Default) set at (value not set )

The other (Default) setting 1

 

[trodas]

Solaris17 - this does not work at all in Windows 2000, Windows XP and Windows Vista.

APPLIES TO
• Microsoft Windows 95
• Microsoft Windows NT Server 4.0 Standard Edition
• Microsoft Windows NT Workstation 4.0 Developer Edition

AsRock - so it obviously use the very same mythical "solution" Case closed. This simply does not change a thing, besides more recent Windows do this automatically. The only one question that there is is, how to change the wait time, before dll is removed from ram.

 

[Darknova]

Unloading the DLL is pointless. We're no longer in the era of 128Mb of RAM. It's like paging the core files. You get better performance just leaving it all in RAM.

There are no adverse effects to leaving a DLL in RAM. It's designed to work that way for a reason, namely making the program quicker to boot up and allowing other programs access to the same DLL without having to unload and reload it.

It's another of these options that were once very useful, but now aren't even though we are lead to believe they still are.

 

[Solaris17]

ya id have to say with 4gb of ram i kinda dont care anymore :/

 

[trodas]

Guys, guys... have you ever heard about memory fragmentation and largest chunk problem?

 

[AsRock]

Unloading the DLL is pointless. We're no longer in the era of 128Mb of RAM. It's like paging the core files. You get better performance just leaving it all in RAM.

There are no adverse effects to leaving a DLL in RAM. It's designed to work that way for a reason, namely making the program quicker to boot up and allowing other programs access to the same DLL without having to unload and reload it.

It's another of these options that were once very useful, but now aren't even though we are lead to believe they still are.

True that lol.. even more so if ya on 8GB like i am...

Guys, guys... have you ever heard about memory fragmentation and largest chunk problem?

memory fragmentation yes but the programs don't seem to do any thing to make them worth buying.

 

[W1zzard]

Unloading the DLL is pointless. We're no longer in the era of 128Mb of RAM. It's like paging the core files. You get better performance just leaving it all in RAM.

There are no adverse effects to leaving a DLL in RAM. It's designed to work that way for a reason, namely making the program quicker to boot up and allowing other programs access to the same DLL without having to unload and reload it.

It's another of these options that were once very useful, but now aren't even though we are lead to believe they still are.

exactly. actually constantly loading and unloading dlls will cost you more performance than losing a little bit of memory

 

[Darknova]

Guys, guys... have you ever heard about memory fragmentation and largest chunk problem?

Yes, but do you leave your PC on for weeks or months on end?