The entire code path invoked from your alarm handler needs to be within the first segment. Unless you get very fancy with your startup code, it doesn't help placing a stub in the first segment to invoke the rest of your code. Not sure why this is causing problems with power management; I'm surprised it doesn't crash. -- Andr�
-----Original Message----- From: Ryan Bruner [mailto:[EMAIL PROTECTED] Sent: Thursday, May 29, 2003 6:07 AM To: Palm Developer Forum Subject: Not shutting off after alarm My application has made use of alarms for quite some time. After an alarm fires, I alert the user through the alarm sound and then pop up a FrmCustomDialog to inform the user. This has been working fine. Recently, however, when this alarm fires and the form comes up, the PDA will not shut itself off after the timeout as it is supposed to. (Mine is set to shut off automatically after 2 minutes). The odd thing is that none of my alarm code has changed. The only thing I have done is moved some of the functions I call to handle the alarms into another segment from the first segment. The functions that get called in response to the alarm, however, are still in the first segment...it is just that these functions make calls to other functions in another segment (which were previously in the first segment). So, why would this cause the PDA from not shutting down? Or, is there something else that might cause this? Other than not shutting down, everything is actually functioning quite normally with regards to the alarms. Ryan -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
