On Monday 13 February 2006 21:50, David Thacker wrote: > >> Mike Durian wrote: > >> > Does anyone know why I can copy an m68k system library from Handheld > >> > memory (we're talking a Palm OS 4.1.2 device here) to Card memory, but > >> > it > >> > is not listed under Card memory to be copied back. It seems strange > >> > that > >> > I can back something up, but not restore it. > >> > >> Do you talk about VFS here? > > > > Not directly. I'm referring to the Copy function that is built into > > the Launcher. If you go to the App menu on the launcher, you can > > select Copy. Using this function, I can copy a shared library to > > the VFS card memory, but I don't get the option of copying them > > back. It seems strange that the launcher would be able to locate > > them in "Handheld" memory, but not in "Card" memory. This applies > > both the the Aceeca Mez1000 device I am using and POSE. > > > > I'd like to use the Card memory for back-up purposes, but if the > > battery goes on the PDA, then I'll only have use of the launcher's > > Copy command to restore my system libraries - and apparently, it > > will only copy the system libraries in one direction. > > > > mike > > Mike, > > Two things: > > 1. The CardBkup utility is in ROM on the MEZ1000 with BCS2 scanner & CF > card. Why not use the CardBkup utility to both backup and restore your > files, regardless of type? It's there for you after hard resetting the > device (from dead batteries, system power down, manual hard reset, etc.). > > 2. What happened when you changed your shared lib type the standard 'libr' > and then tried the Copy function from the Launcher?
David and Nikolai, Thanks for the feedback. I'm going to roll the code that will automatically backup or restore my databases into the application itself. I'll be using Rusell Cagle's ideas on how to update a running database as explained in his post in the "deleting a program currently on the palm" thread. David, to answer your questions. 1) We've still got a couple old Mez units that don't include the CardBkup utility. They can't be updated either since the small ROM needs newer hardware. We're not using the BCS2 scanner with CF either. We use our own custom board and are making backups to the small internal Card memory. The default ROM image from Aceeca no longer makes this Card memory accessable, but they can provide a different ROM if you ask. At any rate, it will be less burdon on the customer if we can automate backups and restores. 2) I'm not using the standard 'libr' type on purpose. I'm using the system library mechanism as a way to manage "plug-in" modules. The main application goes searching for databases of a specific type (not 'libr'). It can then load one of the many it finds and access a standardized function mapping by loading that database as a shared library and making system calls to it. That way the application doesn't need compile time knowledge of an extensible interface. It just makes a system call to "calc", which might end up being "foobar_calc" or "bletch_calc" depending which library is loaded. I don't use the 'libr' type to make it easy for the application to determine which databases it can use (it doesn't know the list at compile time). mike -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
