David W. Poole, Jr. wrote:
> On Sat, 16 Jul 2005 07:01:08 GMT, "jm7" <firstname.lastname@example.org> was
> understood to have stated the following:
>>I have a Palm Treo and 2 PCs that is synchs with. When I hot sync with PC
>>1 and then do another hotsync with PC2 - the ALTERNATE hotsyncs always
>>very long time. Hot syncs on the same PC are always quick as you know.
> Of course. The process of synchronizing your PDA with the last PC it
> was synchronized with is known as a fast sync, otherwise it's a slow
> sync. From the developer documentation from Palm for writing conduits:
> Fast and Slow Synchronization
> The HotSync process is designed for maximum efficiency, which
> means minimizing the data that needs to be transferred whenever
> possible. HotSync Manager accomplishes this by using two forms of
> record-level synchronization:
> ? Fast sync, or fast synchronization of records, sends data
> between the handheld and desktop only if a change has
> occurred since the most recent synchronization. Fast sync
> should not transfer records that have not been modified.
> ? Slow sync, or slow synchronization of records, is used in
> situations in which fast synchronization is not possible. This
> happens when the record status flags on the handheld cannot
> be reliably used because the desktop computer and handheld
> were not most recently synchronized with each other. Slow
> sync compares each record in the handheld database with the
> corresponding record on the desktop computer to determine
> how to synchronize the records.
> HotSync Manager automatically determines which synchronization
> form is appropriate, and communicates this to each conduit upon
> Is Fast Sync Possible?
> HotSync Manager retrieves the user ID and the PC ID of the most
> recent synchronization from the handheld. It compares these values
> with the values stored on the desktop computer. If the PC ID values
> match, then conduits can perform a fast sync, meaning that they can
> depend on the modification flag in each record to determine
> whether the record requires synchronizing. Figure 4.3 shows how
> HotSync Manager determines whether conduits can perform a fast
You hit two bird with one stone. This explains why I sometimes get a slower
HotSync process. My Windows 98 laptop is used for HotSync and it only has
32 megabytes of RAM, which gives you a rough idea of the need for
efficiency. It wasn't long ago that I disabled synchronisation of all
applications apart from a few that I actively use.
>>Is there some way of tricking the PALM into thinking that it is SYNCing
>>the same PC? Perhaps just copy a particular file that is onvolved in the
> If there was a way to trick the Palm into thinking a different PC is
> the one to be synchronized with, it wouldn't be a wise thing to do. At
> least, not if the data you're synchronizing is important to you.
> As another person mentioned, if you want to minimize your first sync
> at a computer that's different than the last one you've synced with,
> set the actions (BUT NOT THE DEFAULTS!) of EACH of the conduits to
> "Handheld overwrites desktop." Of course, make sure there are no
> edits on the "new" desktop that you want to keep, because they most
> certainly will be lost.
This appears to offer an unsafe solution that is troublesome over the long
run. I suggest that the OP learns to tolerate the slow HotSync or give up
one of the synchronisation nodes (desktops). Multiple desktops are better
off avoided where possible, also when it comes to general filesystem
management. Bookmarks, domains, E-mail and so forth likewise.
Roy S. Schestowitz