Thanks for the response, Ben. At 01:00 PM 10/22/2002 -0500, Ben Combee wrote:
At 10:27 2002-10-22 -0700, you wrote:On a hard-reset Tungsten, I see the following three files for the 'Clock' application, for example:
(Name / CrId / Type)
Clock_PcLK / PcLK / appl
Clock_PcLK_appl_a68k / PcLK / a68k
Clock_PcLK_enUS / PcLK / ovly
Can someone help me make sense of this? Looks like the Clock application has an overlay in English, and I am guessing that it is Motorola 68k code being emulated on the ARM CPU through PACE, hence the mysterious "Clock_PcLK_appl_a68k" database.
What do the PcLK and a68k creatorId/types mean? Does the OS manage the file with the 'a68k' creator ID? Is this something that Hotsync backs up?
PcLK is the creator code of the clock application.
Fair enough...
PACE normally deals with shadow versions of the resources in your 68K apps -- this is a converted version of the resource that follows ARM byte ordering and structure packing rules. These shadow structures are stored in the 'a68k'-typed databases.Looks like OS5 creates these a68k resource caches for where type == 'appl || 'panl', with the sole exception of HotSync.
While your application is running in the emulator, take a moment to use the view/Databases commmand and you can see one of these DBs created for your app. It will have the currently active set of resources, all in their ARM-native formats. This DB will keep the cached structures until the application closes, when they'll be removed.
Can I safely infer from this that these files are created on an as-needed basis by OS 5? I'm working with a utility that backs up a Palm device. From what you're telling me, it sounds like I can safely skip backing up (and restoring) any file with crId == a68k. Moreover, it sounds like I -want- to skip them to avoid the rare event of restoring a stale cache file on top of a fresh version.
-Jeff Ishaq
--
For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
