|
|
 Originally Posted by GalenMD
That link explains the different names of the databases, and makes sense, except that it doesn't answer the question at hand: Why does the Treo have BOTH of each app listed in RAM?
from the DB5 yahoo groups...
"If you have a Treo-650 or Tungsten T5 - read this ...
With one of these two devices, you have already realized that the
inefficient NVFS storage is awfully expensive when storing small databases -
especially on the Treo-650 which only has 24mb of available memory.
The worst part of this inefficiency is when a third party application tries
to access one of the classic PalmSource PIM apps. As you know, the kludgy
Datamanager patch steps in and creates a mirror of their proprietary
database and populates it with the same number of records, but with NO data.
Normally, this database takes up little room since the only space is taken
up by the record header (I forget exactly, but the header is somewhere
around 6-8 bytes in size). But with the inefficient NVFS storage whereby a
512 byte sector only ever handles one record, these "empty" mirror database
explode in size. For example, a database with 1,000 records will never be
less than 512kb in size (1000 * 512 bytes), whereas on a regular Palm OS
device that database would be only 6-8k or so - an almost hundredfold
increase in size(!).
So the combination of NVFS AND the DM patch is a big problem storage-wise
for Palm users of third party apps.
Now for some important information: the mirror databases ONLY get created if
they are needed. V-5.4a, p7 of DateBk5 does not touch the Datebook database
so the big mirror does not get created. BUT if you had previously installed
an older version of DateBk, the mirror WAS created and won't go away by
itself.
So the first step is to delete the DatebookDB database since your data is in
the CalendarDB database. BUT - you have to be careful when deleting the
DatebookDB database otherwise the palmOne DM Patch steps in and sees the
delete of the datebook data and promptly mirrors the command into the
calendar database, so both databases disappear. However, what you can do is
delete just the Datebook database with a third party file utility like FileZ
(which you can download from almost any Palm Software archive - I also keep
a copy at: http://www.PimlicoSoftware.com/filez.prc).
If you do that, the calendar data should remain intact, and you will gain
back the storage taken by the unnecessary mirror of the Datebook database.
Do the same for the Memos database - i.e. delete MEMODB with FileZ but leave
the MEMOSDB alone. This will save quite a bit storage-wise!! In my case, I
regained over 3mb of memory when I did that(!).
HOWEVER - caution is always advised - make sure you hotsync first AND that
you have a good, separate backup of your Palm data, just in case something
goes wrong.
Now keep in mind that ANY application that attempts to access the classic
Datebook database will instantly cause the mirror database to reappear,
gobbling up all that storage, so keep an eye out with FileZ in case they
mysteriously re-appear!
I still suspect that some funny things are going on in the DM Patch, but
everything above is something that I have done on my device and it
definitely seems to work fine...
Cheers!
CESD, Pimlico Software, Inc."If you have a Treo-650 or Tungsten T5 - read this ..."
|
|
|
