When you are debugging a conduit, there are two timeouts that you need to avoid. The first is an automatic-off timeout, the second a HotSync one.
There is a timeout that causes the handheld to go to sleep after a certain time (a power-saving feature). If you’re in the middle of single-stepping through your conduit and the handheld goes to sleep, you’ll have one thoroughly ruined debugging session. To avoid this problem, use the
..3 shortcut (see Section 10.2 for a full discussion). It stops the Palm OS handheld from going to sleep.
Until you do a reset, the Palm OS handheld won’t go to sleep again automatically. Try not to wander away from your debugging to other things. If you do, when you come back to your debugging after a good night’s sleep, your batteries will quite likely have expired.
The other timeout you need to worry about is the timeout of the HotSync protocol. If you are stopped at a breakpoint while in the middle of a synchronization, the HotSync application is not sending information to the handheld. The handheld then thinks that the connection has been lost and ends the HotSync session.
To convince the handheld not to give up, you need to use a secret option that lies hidden within the handheld HotSync application. To get to it, you open the HotSync application ...