Path: utzoo!attcan!uunet!wuarchive!sdd.hp.com!uakari.primate.wisc.edu!samsung!olivea!oliveb!felix!dhw68k!arybicki
From: arybicki@dhw68k.cts.com (Adam Rybicki)
Newsgroups: comp.windows.ms
Subject: Re: Limit on global memory handles
Message-ID: <1990Oct9.201745.10552@dhw68k.cts.com>
Date: 9 Oct 90 20:17:45 GMT
References: <8795@helios.TAMU.EDU>
Reply-To: arybicki@dhw68k.cts.com (Adam Rybicki)
Organization: Wolfskill & Dowling residence; Anaheim, CA (USA)
Lines: 14

In article <8795@helios.TAMU.EDU> tony@cs.tamu.edu (Tony Encarnacion) writes:
>
>The SDK manual says "there is a system-wide limit of 8192 global
>memory handles, only some of which are available to any given 
>application."
>
>Does anybody know the actual number of global memory handles that
>a single application can allocate?  that

Well, after Windows is done initializing, it normally leaves a little
more than half of those 8192 handles.  You can use all of the remaining handles
but then other applications will not be able to run at all.  Microsoft advises
to use LocalAlloc whenever possible or to implement your own memory management
if LocalAllocs are not good enough.