VisorCentral.com (http://discussion.visorcentral.com/vcforum/index.php)
- How To / Troubleshooting (http://discussion.visorcentral.com/vcforum/forumdisplay.php?forumid=2)
-- Prism synch error message - whats it mean? (http://discussion.visorcentral.com/vcforum/showthread.php?threadid=15805)

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

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>

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

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.

---

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.

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

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.

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.

---

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).

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?

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

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.