CompuServe Messages

Gary, You are erroneously equating a perceived cause-and-effect here. The memory manager looks at two of the MEMF_ bits to determine which memory pool(s) to use to satisfy the allocation request. These two bits are MEMF_CHIP and MEMF_FAST. If _neither_ of these flags are set, then the memory manager's actions are as you describe – first try to allocate from FAST and if that cannot happen, attempt to allocate from CHIP. Therefore, you can specify a "flags" value of 0L to your memory allocation request if this is the desired type of allocation. MEMF_PUBLIC currently is a place holder – it has no effect _currently_ on the allocation. It was intended to indicate a chunk of memory that could be seen by more than one task, but has never been implemented due to the lack of memory protection. Hope this clears up the mystery! …BobR