Is anyone syncing with Palm and isync (leopard) successfully?

Paul Reading2 wrote:
Click "Force slow synchronisation" and then sync twice.

How long did slow sync take for you? I have tried that but it seemed to hang and do nothing so I forced a quit after about 5 or 10 min.
Ken

OK, I finally broke down and purchased "Missing Sync," after waiting for Apple to fix this problem. I'm sorry to say that "Missing Sync" does NOT solve this issue completely. It will sync the Address book, but will NOT work with iCal.

Apparently, "Mark/Space" (the makers of "Missing Sync") are aware of the problems, have identified the problem as Apple's, and reported it to Apple. Here are some of the issues noted on the "Mark/Space" web-page...

"This article describes situations under which The Missing Sync may report errors or perfomance issues. One error message is specific to iCal (part of Apple's Mac OS X operating system) and describes errors from iCal that are affecting the ability of The Missing Sync from performing sync functions properly."

"In certain situations, The Missing Sync reports an error message titled 'iCal Sync Errors'. This error is often caused when iCal is attempting to share data with Sync Services. Although this error has little to do with handheld devices, it affects the ability to sync data to or from those devices as Sync Services functions are compromised."

"THIS ISSUE HAS BEEN REPORTED TO APPLE, INC. BY MARK/SPACE."

"Errors that are not reported in The Missing Sync log may be found in the Console.log file."

"Here are some of the error messages you may see in the Console:

iSDSqliteRecordMapper
SQLite locking issue
iSynceConcreteSession
NSInvalidArgumentException
ICalExternalSync
ISyncInvalidRecordException

These error are generated by Sync Services and reported to The Missing Sync."

So, for those of you hoping that "Missing Sync" will solve the problems we are having with various hand-helds, and/or cell phones, it doesn't completely. I am a huge fan of Mark/Space's "The Missing Sync" and have used it many times throughout the years. It's a great piece of software that does a whole lot more than iSync ever has, but it does NOT solve all of the problems that are being reported all over this forum in regards to iSync issues and hand-helds/cell phones.

I already posted a response to the issue you raise in another forum, but for the benefit of others here who might not have been following that thread, there is this:

You are right: it does not solve ALL of the issues with synchronization under Mac OS X 10.5 or later, but it does solve most. Mac OS X Update 10.5.2 correct two issues, and introduced another. The issues are, in fact, reported by the synchronization framework to the Missing Sync and other registered clients, BUT they do not originate their. They originate in iCal 3, and therefore ONLY adversely impact users of Mac OS X 10.5 or later.

The root of the problem lies in the fact that the synchronization component of iCal itself was rewritten from the ground up, and the iCal team obviously didn't get it quite right.

Most errors involve recurring events, though some do not. One way to avoid the issues, which pop up less often than you might be led to suspect, is to avoid using recurring events.

Developers are aware of these issues, but everyone agrees—as does Apple's Sync Services team—that this is clearly something that must be addressed in a fix (or, in a number of fixes) to iCal. And so, until it is, everyone who synchronizes potentially will be affected by the errors thrown up during an event.

This may be of some [help|http://discussions.apple.com/message.jspa?messageID=6805570#6805570]

I have a Palm V connected via its old cradle and a KeySpan USB adapter. This has been working fine through 10.5.2. Let's hope that continues...

Is your USB cable plugged into a powered port? This might be an issue if your cable is doing signal conversion.