T3 Sync Problems

A

Adelle

New member
I've been struggling with a problem on my T3 for most of the last dayy or two.

If I go to Hotsync on the T3, I can see the Hotsync screen underneath, but get a Fatal Alert/Fatal Exception. There's no other clue to where it's coming from.

There's a Reset button, but it doesn't do anything.

I have made some progress in diagnosis. If I perform a warm reset, the problem disappears and syncing works. If do a normal soft reset, it comes back. I've tried a hard reset and reload. I've tried the same without a keyboard driver. I've tried deleting the saved_preferences.prc.

I've downloaded SuperUtility so ought to be able to make some sense of the differences between a warm and soft restart, but am not sure where to start, really.

Is there a way to easily see what files are being loaded between the two different resets?

Thanks

Bob
 
Well, as is often the case, asking for help was enough to solve the problem.

It seems, and I have just repeated the process to force it to fail, that I got the problem if VersaMail was not configured before my first hotsync after a hard reset!

If I configure VersaMail, the system syncs just fine.

Time for taking the integrated apps out of Flash, I think!

Bob
 
Hmmmm.... Well I thought I'd sussed it. but it seems not.

Still flaky and I'm just not sure where to look.......

Any ideas appreciated.

Bob
 
Actually that was wonderful deductive reasoning, and I have not heard of that before (VersaMail's non configuration causing crash).

I got rid of VersaMail for space reasons, and the fact that I could SEND email but couldn't get it to configure properly with the OP3 stuff to SRECEIVE email on hotsync. I will tell you that removing from ROM still leaves someMultiMail ("MM") remnants; if you get a utility that shows you your Saved preferences, (either SysTool or Filez, both free -- I like SysTool) you can go ahead and DELETE anything with MultiMail - but there are STILL remnants in ROM. Just so you know.

I'm wondering since no one else has brought that to the Forum's attention if it wasn't something "quirky" in your specific case (and believe me the T3 is QUIRKY!) but I'm glad you fixed it.

Other problems solved by "pulling stuff out of ROM" are the Documents to Go nightmare of having 6.002 in ROM and the newest 6.008 (should you upgrade to it, which you should) in RAM. Same goes for Kinoma Player 2.0, now available free. These apps should never have been put in ROM - they should have been on the Palm Desktop Install CD for YOU to choose which you took.

I'm glad you solved your problem; my hotsynching with the T3 has easily been the most troublefree I've ever had -- MUCH better than the previous M505 - hopefully it will "sail along" for you now and you won't have any more problems. Think twice before yanking VersaMail out of ROM, as I don't know if it's provided in any other media (CD or otherwise).

Take care buddy and congrats!!
 
WE muyst have posted at same time -- thought it seemed odd. PM Mooseman or Genoahous or Abid - they may have some clues for you that I don't, other than reinstall the Palm Desktop (GROAN!!).

Sorry you're having trouble.
 
I've just realised why it was inconsistent.

If I press the sync button on the cradle, it works and syncs every time. If I use the UI to try to do it, it bombs!

It hadn't occurred to me that they might not be interchangable. Doh!

In fact, after hotsyncing using the cradle button, any touch on the screen bombs the system. OTOH, if I use a button to go to another app, the system stays stable.

After a warm reset the system is fine however I access Hotsync.

At least I think I have consistency now.

Bob
 
Bizarrely, and for not apparent reason, today it's all working beautifully!!!

I did use Filez and deleted apparently orphaned preferences, but I'm sure it was still failing last night after that.

Still, as long as it keeps working!!!
 
Just as a follow up for anyone else that was having trouble.

I continued to get glitchy problems and finally decided it might be hardware. Palm took the unit back and 'repaired' it. I suspect that they put a different/fixed/update ROM image into it.

However, it is now working properly (fingers crossed!)

Bob:) :)
 
Back
Top