🚀 go-pugleaf

In article <1991Apr29.184300.13990@amd.com> indra@brahms.amd.com (Indra Singhal) writes:
>With 12Meg Ram and 4Mb Cache, 2Mb Ram disk 16Mb permanent swap, with a
>dozen windows including 3-4 hDC microapps I run 'out of memory or other
>windows resource'. Even though hDC memory viewer shows I have 11Mb or
>memory available (must include swap)...
>

In this month's BYTE magazine is a great article on standard Windows problems.
Sorry I can't give a page reference, but the magazine is at home in the
library :-).  I believe it was in the 'Hands On' column. (Also, there is a
fabulous article on packet drivers, what they are, how they work, etc..)

Anyway, the gist of the article is that there is are a couple of 64K stacks
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.

Anyway, the article is good reading.  If you can't find it, email to me and
I will send the volume/page reference.

Kelly

-- 
Kelly Grant        grantk@manta.nosc.mil   (619) 225-2508
Computer Sciences Corp          ^^^^^^^^ Important: manta.UUCP won't get to me
4045 Hancock Street      "If you are given lemons.....see if you can trade for
San Diego, CA 92110       chocolate" - me