system resource management

Is there any good free programs that release system resources after a
program has been closed? I understand that many programs keep a hold of
system resources even after you shut them down.

--

-Jesse

Noel
Fri Apr 29 00:15:05 CDT 2005

Very few programs 'keep hold of' system resources after they have been
closed - and as far as I know the best solution if you have one that does,
is to stop using it!
The use of 'memory managers' is something to avoid at all costs, as they
frequently cause many more problems than they claim to solve.

--
Noel Paton (MS-MVP 2002-2005, Windows)

Nil Carborundum Illegitemi
http://www.btinternet.com/~winnoel/millsrpch.htm

http://tinyurl.com/6oztj

Please read http://dts-l.org/goodpost.htm on how to post messages to NG's

"KingTek" <no.spam@for.me> wrote in message
news:QYGdnQ0ywvrdOuzfRVn-3A@comcast.com...
> Is there any good free programs that release system resources after a
> program has been closed? I understand that many programs keep a hold of
> system resources even after you shut them down.
>
> --
>
> -Jesse
>
>
>
>

Rick
Fri Apr 29 01:43:49 CDT 2005

KingTek wrote:
> Is there any good free programs that release system resources after a
> program has been closed? I understand that many programs keep a hold of
> system resources even after you shut them down.
>

There's a reg key somewhere... "fast unload .dll's"; most registry
enhancing programs can modify it.


Rick

too lazy to find out what the key is

Ron
Fri Apr 29 13:42:18 CDT 2005

"KingTek" <no.spam@for.me> wrote:

>Is there any good free programs that release system resources after a
>program has been closed? I understand that many programs keep a hold of
>system resources even after you shut them down.

That is not correct. Properly programmed applications will release
their system resource allocations when the program exits, with two
exceptions, neither of which can be overcome by any utility:

1. Programs will often load shared components in addition to the
program itself. The shared components will, by design, remain open
after the application is closed because they could be in use by
another application; and therefore the resources allocated to these
shared items will not be released. Fonts are a small, but classic,
example of this, as each font requires a small amount of system
resources.

2. 16 bit programs (e.g. Windows 3.1 applications) are considered as
one resource pool and therefore resources allocated to 16 bit apps
cannot be released until all 16 bit apps are closed. Example:
Open 16 bit app #1 - some resources allocated to it.
Open 16 bit app #2 - some resources allocated to it.
Close 16 bit app #1 - no resources released because 16 bit app #2 is
still open.
Close 16 bit app #2 - resources allocated to 16 bit apps 1 and 2
released.


See http://www.onlinehelp.bc.ca/tips.htm#resources and also
http://www.aumha.org/win4/a/resource.htm for an explanation of System
Resources.

Hope this explains the situation.

Good luck


Ron Martell Duncan B.C. Canada
--
Microsoft MVP
On-Line Help Computer Service
http://onlinehelp.bc.ca

In memory of a dear friend Alex Nichol MVP
http://aumha.org/alex.htm