news | articles | reviews | software | modules | accessories | discussion | faq | mobile | store
VisorCentral.com >> Discussion >> Visor Related >> How To / Troubleshooting
Prism synch error message - whats it mean?

Post a New Thread | Post A Reply

  Last Thread   Next Thread
Author
Topic: Prism synch error message - whats it mean?    
alag8r
Member

Registered: Mar 2001
Location: Dothan, AL
Posts: 6

When I synch, everything transfers correctly, but I get the following error message at the end of my log:

System synchronization failed
Protocol Error: Handheld file not found. (4003)
HotSync operation complete 06/06/01 09:41:24 PM

Should I be concerned? What handheld file is it not finding?

Thanks - rick

alag8r is offline Old Post 06-07-2001 03:14 PM
Click Here to See the Profile for alag8r Edit/Delete Message Reply w/Quote
Azdeadwood
Member

Registered: Jan 2001
Location: Tucson, Arizona, USA
Posts: 50

Looks like you are synching using Palm Desktop verion 4.01.
You get the message because the System files on a Handspring are burned onto the ROM chip. The System files on a Palm are in RAM so the software expects them to be synched.

__________________
Richard Grogan
Email: <A HREF="mailto:[email protected]?subject=VisorCentral">[email protected]</A>
Homepage: <A HREF="http://www.azstarnet.com/~rgrogan/official.htm">http://www.azstarnet.com/~rgrogan/official.htm</A>

Azdeadwood is offline Old Post 06-07-2001 03:56 PM
Click Here to See the Profile for Azdeadwood Edit/Delete Message Reply w/Quote
alag8r
Member

Registered: Mar 2001
Location: Dothan, AL
Posts: 6

Thanks Richard. That makes sense and it sounds like it might be something not to worry about. However, I don't really use the palm desktop at all and the one I have installed is version 3.1. The Hotsync Manager is version 3.1.0Hb.

rick

alag8r is offline Old Post 06-07-2001 04:12 PM
Click Here to See the Profile for alag8r Edit/Delete Message Reply w/Quote
bradhaak
Member

Registered: Oct 2000
Location:
Posts: 380

quote:
Originally posted by Azdeadwood
Looks like you are synching using Palm Desktop verion 4.01.
You get the message because the System files on a Handspring are burned onto the ROM chip. The System files on a Palm are in RAM so the software expects them to be synched.



I don't think so.

I synch a Visor Deluxe, Edge, Plat, and Prism as well as various Palm devices with 4.01 on two computers. Everything works great. Also the system files on Palm devices are on either Flash or masked ROM (like HandSpring). Neither one is synchable.

You can always try the brute force method. Delete the user from the Palm Desktop on your PC and then HotSynch to recreate the user. This shouldn't screw anything up. I have done this a number of times.

bradhaak is offline Old Post 06-07-2001 04:21 PM
Click Here to See the Profile for bradhaak Edit/Delete Message Reply w/Quote
sdoersam
Member

Registered: Aug 2000
Location: Glen Burnie, Maryland
Posts: 205

This error comes from syncing with a Springboard installed in the Visor. It somehow confuses the sync software (probably because the Springboard bus connects directly to the Dragonball processor bus). I get this error everytime I sync with a module installed. take out the module, and it syncs fine.

__________________
Sven

If at first you do succeed, try not to look astonished.

sdoersam is offline Old Post 06-07-2001 04:26 PM
Click Here to See the Profile for sdoersam Edit/Delete Message Reply w/Quote
alag8r
Member

Registered: Mar 2001
Location: Dothan, AL
Posts: 6

Thats it. I removed my Thinmodem plus and synched. No error. I'm not going to worry about the error any more. Thanks to everyone who responded. rick

alag8r is offline Old Post 06-07-2001 05:41 PM
Click Here to See the Profile for alag8r Edit/Delete Message Reply w/Quote
potter
Member

Registered: Feb 2000
Location: SW Virginia
Posts: 290

Could anyone who has experienced this problem please report it to Handspring via either:

  • The Product Support line at (716) 871-6448 from 8am to 10pm Eastern Standard Time Monday through Friday and 10am to 7pm Saturday and Sunday.
  • The Customer Support: Contact Support web form.
I do not expect them to give anyone a solution to this problem, for when I reported it the answer I got back was as follows:
quote:
Thank you for contacting Handspring Technical Support.

We do not recommend that you hotsync your Visor with the Flash Module installed. Even though the computer doesn't exchange data withe module. It can be "seen" during the hotsync process and sometimes cause hotsync errors such as the one you mentioned in your e-mail to occur. Remove the module from the Visor before you hotsync.
I am living with this answer for now but I do not like it. I do not like it because:
  1. If I remove the module before Hotsync'ing then any application that has an associated conduit can not be put on the module. Otherwise the conduit will not run when the module is removed.
  2. Leaving the module in causing this error during the execution of the system conduit (a.k.a the backup conduit). I am not convinced, one way or the other, when this error occurs, the backup conduit did not completely back up my data (as well as it is designed to).
Currently I just Hotsync with the module in place most of the time, and occasionally without the module.

Any way, the more who report people to report this problem, the more likely Handspring well eventually fix it.

Some additional information: After some further experimentation after I got that reply from Handspring I found that that Palm Desktop 3.01 as distributed from Handspring's Website does not have this problem (Hot Sync Manager 3.0.2Hb). Palm Desktop 3.1 as distributed from Handspring's Website does (Hot Sync Manager 3.1.0H). However the backup conduit in Hot Sync Manager 3.0.2 does a poor job of managing the backup directory.

potter is offline Old Post 06-08-2001 08:24 PM
Click Here to See the Profile for potter Edit/Delete Message Reply w/Quote
alanf
Member

Registered: Oct 1999
Location:
Posts: 110

Should have read this first!

Well, it pays to read the boards. I noticed exactly this error earlier today, and looking through my log found that I've had it as far as the log goes back - which is AFTER I got my 8mb flash module. Called HS tech support before looking here, and they told me exactly the same - remove the module and it will sync. True, but what's realy going on?

Potter - you were concerned that a conduit wouldn't function properly if its associated application was on the module. Maybe I'm missing something about flash modules - I thought that data on the module was not accessed during the hotsync process anyway (because - I think - it needs to be moved into RAM before being edited). Do I have this wrong?

alanf is offline Old Post 06-11-2001 07:26 PM
Click Here to See the Profile for alanf Edit/Delete Message Reply w/Quote
Pathdoc
Member

Registered: Feb 2001
Location: Minnesota
Posts: 216

If you use Backup Buddy, you will not get this error when hotsyncing with a module in place. I also noticed this error when hotsyncing with my ThinModem Plus in place and would remove it whenever I hotsynced. Someone here on the message boards suggested using Backup Buddy and that took care of the problem. (Of course, you also get the benefit of backing up the data on your module.)

__________________
Donate Blood!!!
Visit here to see how: America's Blood Centers

Pathdoc is offline Old Post 07-19-2001 09:15 PM
Click Here to See the Profile for Pathdoc Edit/Delete Message Reply w/Quote
VTL
Member

Registered: Apr 2000
Location: Seattle, WA
Posts: 604

I've had this error message too, forever. I never really worried about it, as it otherwise works fine - all my data gets exchanged. However, it's nice to hear an explanation.

VTL is offline Old Post 07-19-2001 11:12 PM
Click Here to See the Profile for VTL Edit/Delete Message Reply w/Quote
All times are GMT. The time now is 07:56 PM. Post New Thread    Post A Reply
  Last Thread   Next Thread
[ Show a Printable Version | Email This Page to Someone! | Receive updates to this thread ]

Forum Jump:

Powered by: vBulletin Version 2.3.4
Copyright ©2000, 2001, Jelsoft Enterprises Limited.