Hi Danko, One possibility is to trap an event that is generated when a module is inserted or removed. This is a key event with the following value defined in HsExt.h. // card removed or inserted (This is in HsExt.h) #define hsChrCardStatusChg (hsChrRangeMin+6) Note that normally the Handspring patch of SysHandleEvent will catch and process this event, so usually the nested event handlers in the event loop won't see it. You could catch it first with your own patch to SysHandleEvent, as an example. Mike Akamine Handspring, DTS -----Original Message----- From: Danko Radic [mailto:[EMAIL PROTECTED]] Sent: Wednesday, February 28, 2001 1:53 AM To: Palm Developer Forum Subject: Handspring module insertion detection by 'extern' app How to detect Handspring module insertion by an application residing in Visor memory, not on the module? Suppose I have an application in Visor memory that is using the module in some way (GlenAyre pager). When inserted, module installs its default apps and overwrites all the 'registrations' that were set before. So, what I need is to detect module insertion and restart my application to set them back. The problem is that 'official' way of module insertion notification goes through sysAppLaunchCmdSystemReset L.C. sent to apps (with dmHdrAttrResetAfterInstall bit set) residing ONLY on module. So, my app in memory receives nothing! Is there any way to catch notification about module insertion when 'you' aren't on the module? Regards, -D.R. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/ -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
