Tom Zerucha wrote:
> On Thu, Jul 06, 2000 at 04:20:53PM -0700, Adam Wozniak wrote:
> > I'm porting a piece of software to the Palm. It's large and complex enough
> > that
> > I don't want to muck with it if I don't have to.
> >
> > I need more memory for data than what's in the dynamic heap. Like 256 K
> > more.
> >
> > Do I have any easy options?
>
> OS 3.5 has a much larger dynamic heap.
>
When I compile the project in CodeWarrior, I get a total of 86K "code" and 280K
"data".
(As well as all the expected link errors which follow).
> > I've begun thinking about tweaking hardware registers to give myself
> > read/write
> > access to upper memory, but I don't exactly know how to tell what areas
> > PalmOS thinks
> > are in use and what areas may be empty.
>
> There are memory unprotect calls that do what DmWrite does to access
> the memory.
>
> > (Yes, I know it's probably a bad idea, but I want to know exactly WHY it is
> > a bad idea,
> > and how to make it as safe as I can).
>
> Is there a reason you need to do lots of small scattered writes so you
> can't just allocate a bunch of records in a regular database and use
> DmWrite (that is what I do in the similar circumstance).
Actually, that was a great question. It looks like a lot of this is actually
just large lookup tables. I suppose I can make them
binary resources of some kind, and then munge a pointer to point at them.
Would that ensure they don't take up memory in the
dynamic heap? Can I rely on these records being locked down for me, or would I
have to lock them myself?
--
Adam Wozniak Senior Software Design Engineer
Surveyor Corporation
[EMAIL PROTECTED] 4548 Broad Street
[EMAIL PROTECTED] San Luis Obispo, CA 93401
--
For information on using the ACCESS Developer Forums, or to unsubscribe, please
see http://www.access-company.com/developers/forums/
