Upgrade / Migration from TJ25 to TJ35
 

I have been using Sony Clié PEG-TJ25 synchronising with PalmDesktop. Now I have purchased / upgraded a TJ35.

The two models come along with the same, combined CD-ROM (and same PalmDesktop Software Version).

However, if I try to perform a HotSynch, the TJ35 is propperly recognised and HotSynch works - but the HotSynch of the calendar runs for hours without stopping. Windows XP Task Manager confirms that the HotSynch process is running (no shot down).

Strange:
if I de-select the calendar from the synchronise process, the HotSynch for the other data (address, to do, memopad) is successfully performend within less than a minute...

Do the TJ25 and 35 use the same calendar program-- Datebook?

Here's a possible fix.

First, make a backup of your Palm users file. That's crucial, otherwise you could lose your datebook.

Second, set the datebook conduit to PC overwrites handheld-- not sync.

Third, cross your fingers!

Now, if that doesn't work-- here's a second fix.

Try beaming the datebook database from the TJ25 to the TJ35. You'll need a file manager program--e.g., FileZ-- so that you can find the datebook database file. When it beams over to the TJ35, it will ask if you want to overwrite the datebook database that's on the TJ35-- say yes. (of course, if you already have some new entries on the TJ35, you should make a note of them somewhere--or backup up the datebook database to a memory stick first.)

Once it's beamed over, then change the Hot Sync conduit setting for dateboook to PDA overwrites PC.

One of those two fixes should get you back in business.

Let us know how it goes.

Thank you very much :D

Yes, they have the same calendar program (Datebook).

The first way didn't work out - but the second one :)

It was even easier: I have used the 'CLIE Files' Application on the TJ25/35 to copy the 'DatebookDB' File to/from the Memory Stick. No addional software nor infrared connection was needed. :)

That's great to hear! Glad it worked out. And your solution is even easier. This thread (and your fix) could save others trouble in the future.