This is theoretical vs. reality discussion. On a PIII, there is ~96k heap
minus 32K for TCP which leaves ~64 for OS and apps. Once the OS is running
and your app is up, you have about 40k free to do MemXXXNew() allocations.
If you use more you'll probably run out of memory. But theoretically (in
the OS) a chunk can be 65506 bytes long. Plus, the DATA heaps are also
managed by the same method, so thus you could (and it would be OK to)
allocate a DmNewHandle() or a record of 65506 bytes.
Alan Pinstein
Synergy Solutions, Inc.
http://www.synsolutions.com
1-800-210-5293
>Bob,
>
>Thanks for the help. I'm missing something. Here's what I don't understand:
>If the sum of all allocations should be less than 40K, how can a single chunk
>be 65506 bytes. Are you saying "should" as in "it's a good idea"?
>
>My app can have about 50K of data that it needs to organize and work with.
>Are
>you saying I can't use the heap for that?
>
>Thanks,
>
>At 5/17/99 07:14 PM, you wrote:
>>No single chunk in *any* heap may be larger than 65506 bytes. (64K - 30
>bytes)
>>
>>The sum of *all* allocations in the dynamic heap should be no more than
>>about 40K bytes on OS 3.0 and later, and no more than about 15K in OS 2.0
>>and earlier.
>>
>>4 chunks of 7500 bytes each should (barely) fit on OS 3.0 devices, but if
>>you're using much more dynamic memory you're probably going to be in
>>trouble.
>>
>> -Bob
>>
>>
>>
>
>
>- Alan Macy
> http://www.ResponsiveSoftware.com
> Time and Billing for Consultants and Others
>
