Hack managers like HackMaster and Xmaster don't work under PalmOS 5.x. To have your application run on system reset, it indeed has to handle the sysAppLaunchCmdSystemReset launch code. There could be many reasons why your device is hanging - for instance, you must not access any global variables when handling the non-normal launch codes.
Also, during the handling of some launch codes you aren't allowed to use the user interface (i.e., call FrmAlert and so on). I don't know whether sysAppLaunchCmdSystemReset imposes such a restriction (it probably does) - but sysAppLaunchCmdSyncNotify, for instance, definitely does. If you *have* to use the user interface, on reset just set an alarm and exit. When you get notified by the alarm manager (and during any other notification), you can use the user interface. If you want your application to do something when the system wakes up, your application has to register to receive notifications about the sysNotifyLateWakeupEvent event. Alternatively, you could use a third-party freeware autoexec launcher to launch your application on reset: http://www.freewarepalm.com/utilities/autoexec.shtml Regards, Vesselin -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
