> So APPARENTLY, the PalmOS PARTITIONS the free space and only allows > the OS a set portion of available memory to use. It seems like this > percentage is LOW -> around 20% on the larger heap sizes. Can ANYONE > shed some light as to the PalmOS 5 algorithm for partitioning heap > usage? It seems nonlinear.
your problem may be simply the fact that the heap doesn't have a large enough CONTIGUOUS block of ram to allocate to you. have you tried making a call to HeapCompact() or similar API's to shift things around so that a large enough contiguous block is available? some of the Mem* API routines allow you to check the maximum contigous block available - you can look at that as well. > NOTE: This is why I so enjoyed being able to gain true access to VRAM > on the OS 4 CLIEs (via WinScreenLock). Because I could use VRAM for > my buffers and not use up valuable heap space. By the results of the > test, I conclude that some devices out there MAY have only 512K HEAP > size, and then I can't do 16-bit graphics. > > Does anyone out there know a trick in OS 5 where you can create a > screen buffer and not use heap RAM? we have a trick on pre OS5 :) thats how we were able to have > 400k of dynamic ram even on palmos 3.1 :) OS5 removed that ability, so, like you, we were stuck with dynamic heap only :( --- Aaron Ardiri [EMAIL PROTECTED] CEO - CTO +46 70 656 1143 Mobile Wizardry http://www.mobilewizardry.com/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
