Tom LaPrise
Member
Registered: Jan 2000
Location: Monroe, Michigan, USA
Posts: 244 |
VoxDei (and forvisor):
Actually, I double-checked; it seems I moved the big Launcher III file to the module (the app itself), and have copies of the three smaller files associated with it in RAM and on the module. Maybe this is the secret...I don't know. I have done several soft resets in the last couple of months to deal with third-party apps not working right, etc., and have pulled the module out and replaced it several times to demonstrate the Springboard idea, and haven't had any problem with apps reverting back to any single tab (they stay in the tabs I renamed/created and assigned them to).
As for the memory module "blowing," it doesn't at all. As long as you keep in mind you can't put apps which write to themselves or DB's which are written to by the app on the module (actually, you can keep copies of the apps or DB's on the module as backup; the Visor will write to what's in RAM, and you can periodically recopy the DB to the module), you shouldn't have any problem at all. I have almost 3 megs of images, documents, apps, copies of DB's (including AddressDB, DatebookDB, etc.) on the module and have no problems whatsoever. I never have to worry about running out of RAM or losing documents or apps to a hard reset.
Yes, it would be easier to use the backup module if that's what you want to mainly do, but you couldn't free up RAM by storing stuff on the backup module. To get at what's on that module, you would have to restore the whole thing to RAM, and it would only hold whatever is in your Visor's RAM at the time of a backup. I can use the whole 8 megs of my module on a Deluxe or on a 2MB Visor, and I can transfer apps/DB's to someone else's Visor selectively with the Flash module.
|