FYI, MemGluePtrNew is pretty darned solid; I've been able to
allocate 11MB in one shot on the T|T3 (pretty mcuh the entire heap), so I
think in general you can allocate most of the heap in one shot (though
perhaps it varies by licensee?)
So while OS3.5 and later (prior to OS5) you could really only rely
on 180k approx (due to PalmOne's units, as many Sony units had 500k or 1MB
heap evne then), nowadays you can generally assume a lot more.. the T|T1
and T|T2 have 700k of heap, the T|T3 has almost 12MB of heap.
Lets see.. I should build a table and FAQ one of these days, as
I'm forever reposting this info, since its just so darned handy :)
In fact, I've added this to my message board now, with a copy of
this posting as a starting point; if you run MemTest (below) or have any
idea about heap limits on various units, please post to my message board!
http://shadow.skeleton.org/cgi-bin/mb/YaBB.cgi?board=hhgdev;action=display;num=1068648848
T|T1 and T|T2 700k
T|T3 11MB
NX80 7MB
NX70 3.6MB
NX60 3.?MB
T|E 2MB
T|C ??
UX50 lots :)
I can set up a topic in my message board if anyone wants to try
for completeness and try every unit we can find :)
I have a memory test tool which lkets you easily allocate ram in
various chunks on the device until it errors, so you can find out how much
heap a unit has without mucking around:
http://www.codejedi.com/shadowplan/binaries/memtest10.zip
Just enter the number of K to alloc, hit alloc until it errors,
and it shows an accumulated title. So you can try large or small allocs
(using MemGluePtrNew) until your'e blue in the face.
Do a reset afterwards.. looks like MemGluePtrNew returns the
memory as owned by the system, so it doesn't get free'd when you exit the
app.
jeff
--
"Have you played Atari today?"
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/support/forums/
