Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!spool.mu.edu!uunet!nwnexus!hamilton
From: hamilton@nwnexus.WA.COM (Dick Hamilton)
Newsgroups: comp.windows.ms
Subject: Re: Out of resource in Windows 3?
Message-ID: <498@nwnexus.WA.COM>
Date: 2 May 91 00:59:35 GMT
References: <1991Apr29.184300.13990@amd.com> <1950@manta.NOSC.MIL>
Reply-To: hamilton@nwnexus.UUCP (Dick Hamilton)
Organization: Northwest Nexus Inc.; Seattle, WA
Lines: 19

In article <1950@manta.NOSC.MIL> grantk@manta.NOSC.MIL (Kelly J. Grant) writes:
>in the main executables (USER.EXE was one of them...) that keep a lot of 
>information about running processes.  The 'resources available' from the 
>about box is actually the stack space available, not the percentage of
>free memory.  It doesn't matter how much memory you have if these stacks
>fill up. It seems certain programs will hog these stacks if you let them.
>One suggestion is to load the programs in a different order;  this can change
>the way the individual programs allocate space in these stacks.

I have heard that you can actually compact some of the allocated space on 
the stacks by simply viewing the "system resources free" db in Program
Manager or by viewing the hDC FirstApps Memory Viewer with the "Include
Discardables" switch toggled.  This slight increase results in the 
memory area allocated to USER.EXE and GDI.EXE being compacted, well not 
the memory area itself, it's fixed at 64k each, but the space that is 
currently occupied.  

Dick Hamilton
hDC Computer Corporation