Re: alternating multiple Palm devices for one user, best way ?
"hyperscheduler" <hyperscheduler-/[email protected]> Thu, 08 Mar 2012 00:40:01 -0000
| Newsgroups | gmane.comp.handhelds.palm.datebk |
|---|---|
| Message-ID | <[email protected]> |
Thank you for raising this issue, Voytek. I recently (finally!) found my lost Treo 650 so I have been thinking of this issue quite a bit actually. It never occured to me to use a miniSD card in this particular context. I will need to investigate that. In the meantime, here is how I would like to do it: Pimlical Desktop is HotSynced into the Treo 650. Use the Treo 650 for a solid month, adjusting the DateBk6 settings to be the best possible on the specific device of a Treo 650. HotSync the Treo 650 into Pimlical Desktop throughout the month (every night or three). Then, after performing a final HotSync from the Treo 650 into Pimlical Desktop at the end of the month, engage in another HotSync *from* Pimlical Desktop *to* a Treo 755p. Repeat as above, but use a Treo 755p throughout the month and HotSync into Pimlical every night or three. Then repeat the same process for a Palm TX. Then repeat the same process for a Centro. In this scenario, one's calendar is kept updated in two places: Pimlical Desktop, and that month's particular PalmOS device that is being HotSynced almost daily with Pimlical Desktop. What I have learned from this discussion thread, however, is that some people are doing more than merely HotSyncing their particular "PalmOS device of that month" to Pimlical Desktop. Instead, it appears that some people are performing something like a "horizontal" sync between/from that particular month's actively used PalmOS device *to* the other PalmOS device in the form of a miniSD card. Interesting. Once I get more serious about actually implementing a multi-device system, I will need to address the following: First, is it mechanically possible to beam DateBk6 to the various PalmOS devices, and then will Pimlical Desktop smoothly HotSync into the various PalmOS devices that will all have DateBk6? Second, is it ethical to do this? In other words, should each PalmOS device that runs DateBk6 require a user to independently pay for all of these DateBk6 programs? Third, is it possible to also add a pre-Treo650 device to the above system? As we know, there are two different Pimlical Desktops for PalmOS users: those using devices BEFORE the Treo 650, and those using devices AFTER the Treo 650. As you can see above, all of the PalmOS devices that I plan to use in the multi-device system are either the Treo 650 or post-Treo 650. However, what would happen if I decided to add a Palm m515 to the mix? At first glance, it would seem to be impossible because the Pimlical Desktop that I would use would of course be the Pimlical Desktop for the Treo 650 and later. On the other hand, is there *any* way to add a Palm m515 to the mix? Perhaps the answer would be to employ the new system described by others where I would NOT engage in a technologically impossible HotSync between this version of Pimlical Desktop and the Palm m515 but, instead, I would take a miniSD card from one of the other devices and place it inside of the Palm m515 for all of the calendar information to get inside that Palm m515. Even if this is possible, I assume that it would mean going a whole month without HotSyncing the calendar data between the Palm m515 and my version of Pimlical Desktop. So when the month concludes, I suppose that I would need to transfer the calendar data *from* the m515 *to* a Treo/Centro/TX by using a miniSD card. And *then* HotSync that particular device *into* Pimlical Desktop so that the fun can start again. Best regards, HyperScheduler --- In [email protected], "Voytek" <voytek@...> wrote: > > Just curious is anyone here has more than one device, and, 'rotates usage' ? > > as I have more than one TX, I'm thinking of starting to 'alternate' which > device to use on say monthly basis (equalize wear and tear, backup, etc) > > I'm trying to assess what the best way that won't bite me at unexpected > moment, in case someone here has some take on this, pls let me know > > - sync 1st device, reset 2nd device, sync from PC/Desktop, accept userid > > - NVBackup backup 1st device to SD, restore 2nd device from SD card > > what other path ? > if anyone uses or used any such, please share tips and dos/don'ts > > > main use: DateBk, Hours, MyChequebook, Snapper, pFuel > > > I don't want to be able to use both 'simultaneously' > > (the other day, my 'Hours' application 'malfunctioned', probably 1st time > ever that I've seen Hours 'play up', so I thought I should make better use > of hardware that I have....) > ------------------------------------ USEFUL LINKS AND WEBPAGES FOR PIMLICODATEBK ------------------------------------------- Post a message: [email protected] Unsubscribe: pimlicodatebk-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org Previous messages (view/search): http://groups.yahoo.com/group/pimlicodatebk/messages Pimlico: http://www.PimlicoSoftware.com For information about Pimlical, the desktop calendar: http://www.pimlicosoftware.com/pimlicalpreview.htm To discuss Pimlical, please join the Pimlical group: http://tech.groups.yahoo.com/group/pimlical DateBk4 FAQ: http://www.PimlicoSoftware.com/datebk4faq.htm DateBk5 FAQ: http://www.pimlicosoftware.com/datebk5faq.htm DateBk Cookbook: http://how.to/datebk-cookbook DateBk Wiki: http://oldgods.net/cgi-bin/datebk_wiki Neither Pimlico, the developer, nor the list owner is responsible for content.Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/pimlicodatebk/ <*> Your email settings: Individual Email | Traditional <*> To change settings online go to: http://groups.yahoo.com/group/pimlicodatebk/join (Yahoo! ID required) <*> To change settings via email: [email protected] pimlicodatebk-fullfeatured-hHKSG33TihhbjbujkaE4pw@public.gmane.org <*> To unsubscribe from this group, send an email to: pimlicodatebk-unsubscribe-hHKSG33TihhbjbujkaE4pw@public.gmane.org <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/