There are hardware differences between the TRGpro and other devices, but it
should be compatible at the API level. The largest source of problems are
apps that open databases in read/write mode and don't both check for a
success return code. On the TRGpro, users can easily move databases into
flash (with FlashPro) or to a CF card (accessed through AutoCF). In both
cases the databases become read-only.
The CF slot on the TRGpro is secondary storage, so it has no memory "card
number." When AutoCF is installed, the CF card appears to be part of memory
card 0.
We've also run into a lot of apps that don't handle databases correctly -
for example,. they close them, then continue to access their records. This
happens to work fine when the database is in normal memory, but crashes if
the database is on a CF card accessed through AutoCF.
Trevor Meyer
TRG Products
[EMAIL PROTECTED]
----------
From: Chris Tutty [SMTP:[EMAIL PROTECTED]]
Sent: Saturday, September 16, 2000 8:21 PM
To: Palm Developer Forum
Subject: Re: Any differences in TRG Pro hardware
"Richard Bram" <[EMAIL PROTECTED]> wrote
>
> I don't know the answer, but if it makes you feel better, "me,
too".
> I have a report of a crash that happens only on the TRG Pro,
> only when my hack and one other particular hack are enabled, and
> only when three other specific apps are loaded (in compact flash
only)
> and run in a certain specific order. Weird.
>
Doesn't that device allow multiple cards? Meaning that any code
which is
assuming card 0 for databases will fail if enough memory is used to
force
the database out of card 0.
I've got this on my list of things to check for our app.
Chris Tutty
--
For information on using the Palm Developer Forums, or to
unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
