Steve Ely wrote:
I have an application for taking inventory that runs on Symbol SPT's.
I have had some customer reports of a fatal alert with in the first
few scans after hotsync. I have not been able to duplicate the
scenario my self but working with a customer who was having the
problem it became apparent that after the soft reset there were no
more fatal alerts until the next hotsync.
We found a temp fix is to do a soft reset after hotsync to prevent the
fatal errors.
This fatal error happens in your app? Or is your app doing its stuff in
the background (responding to launch codes or notifications) while
another app is in the foreground? Either way, you ought to be able to
create some on-device debugging so that the user can help direct you in
what code to look at for the error. You need a cooperative user, who is
willing to work with you, and whose good will is not yet exhausted.
The PDB file containig the items to be counted is created on a PC and
saved in the Palm install folder to be loaded at the next hotsync. I
am probably doing something wrong when creating the PDB but does
anyone know why the soft reset fixes the problem?
When you do a reset it changes the memory state of the device. Suppose
you have an unitiated memory reference in your code. When you try to do
something with that memory location it MAY crash, depending on what part
of the memory you are trying to manipulate. When you reset the device
it will likely point to a different spot, perhaps one where the system
will not permit you to change it, or changing it does no harm, so no crash.
Bob.
--
For information on using the PalmSource Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/support/forums/
