10.4.2 vs. Palm Desktop 4.2.1 via iSync 2.1, FIXED!

Problem: New iSync 2.1 insisted that Palm Desktop 4.whatever was "incorrectly installed". (Of course it was installed just fine.) Could not enable a Palm device due to inability to install iSynch conduit.

Fix: 1. Removed "Palm HotSync" folder from /Library/Application Support, archived on Desktop for safe keeping, trashed original, restarted to disable running apps.
2. Ran iSync 2.1 (88.0), which crashed repeatedly for some reason. Decompressed "Palm HotSync" folder and returned to /Library/Application Support while iSync was still running (the one time it didn't crash).
3. Selected option to "Enable Palm Device", and lo and behold, it suddenly offered to move various conduits prior to installing the iSynch conduit.
4. Ran Conduit Manager from with HotSync Manager, selected the option to allow iSync to manage whatever goodies it can.
5. Did so, and suddenly my Palm device (HandSpring Visor Prism running 3.5.3) showed up on the Synch bar.
6. Pressed Synch button in Prism cradle, and success!

Conclusions: Apple didn't do the greatest job of making Tiger work with Palm Desktop, but it must be some kind of gerflummoxed permissions problem and fairly "manual" at that. Go figure. Hope they fix it for regular users soon, or there will be a great wailing and gnashing of teeth in the PDA crowd....

Posted on Aug 1, 2005 8:52 AM

Reply
10 replies

Oct 2, 2005 4:44 PM in response to Jan

I suppose it depends upon what you mean by 'the easy way.' Here is one approach to changing the privileges of these three affected folders:

Macintosh HD:Applications:Palm
Macintosh HD:Library:Application Support:Palm Desktop
Macintosh HD:Library:Application Support:Palm Hotsync

You must change the privileges to 'Read & Write' by either selecting each folders' Properties window using Command-I and including the sub-folders inside each, or by using the Terminal application and entering these commands:

sudo chown -R <shortusername>:admin /Applications/Palm
at this point, you'll be asked to enter your login password
sudo chmod -R 775 /Applications/Palm
sudo chown -R < shortusername >:admin /Library/Application\ Support/Palm\ HotSync/
sudo chmod -R 775 /Library/Application\ Support/Palm\ HotSync/
sudo chown -R < shortusername >:admin /Library/Application\ Support/Palm\ Desktop/
sudo chmod -R 775 /Library/Application\ Support/Palm\ Desktop/

Oct 3, 2005 2:19 PM in response to David Turley1

Where can I get a copy of 4.2.1 revision?

The Palm website only shows and downloads revision A.

Is there an immediate solution to the 4.2.1 problems? How can I back out of this without vast computer knowledge? I just want to get synciing again and 4.2.1 seems to have screwed everything up and I'm seriously running out of patience with the fixes they've offered.

Oct 24, 2005 12:06 PM in response to Jan

Before you upgrade to Palm Desktop 4.2.1 revision D, be aware that while they have fixed a number of issues with it, is still creates serious problems that you - if you are aware of them - can easily fix. If you don't do so, however, iSync will not work properly, and Palm data corruption can result.

The morons - and I sincerely mean that - at Palm saw fit to modify the behavior of the Palm Desktop installer [initially with release B of the 4.2.1 package, but still uncorrected in releases C and D] in such a way that it either updates the creation date of - or replaces with updated copies - the original conduits, and tosses them into the active Conduits folder, along with the current ones which should alone be active for use with the Palm Desktop, and disabled if iSync is installed. The Palm Desktop installer could apparently 'care less' about the presence of iSync. As a result, a simple upgrade to the Palm Desktop cause all sorts of issues which need to be addressed by moving conduits around manually.

And, not to be outdone, some moron at Apple modified the code base for the iSync Palm Conduit in such a way that it will create a second, differentially-labeled
i iSync Disabled Conduits folder,
and move the Palm conduits into that when Palm devices synchronization is enabled for the first time, using iSync, in a pristine environment. They are not moved for you in an existing environment unless, of course, you again select the Enable Palm OS Syncing… option from the iSync Devices menu.

It's easier just to move them manually and not deal with this nonsense. But, until you do, iSync will not work properly and the validity of your Palm data is in jeopardy.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

10.4.2 vs. Palm Desktop 4.2.1 via iSync 2.1, FIXED!

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.