> Perhaps in response to the sysNotifyVolumeMountedEvent you need to > do the following:
Yeah, I'm thinking of something like that - but there are still a lot of things that are not clear to me and it is messy, as I said above. > 2) Setup a notification, alarm or event to run your program (in > background) Alas, I can't run anything in the background, sigh... But I know what you mean. > When your program is subsequently called from the > notification/event/alarm you generated: > 1) Scan the start.prc program No, not only that. I want to scan the whole card. If I scan the whole card, obviously start.prc would be scanned too. > 2) If clean, run it by sending an appropriate notification. There *is* no notification for running it. :-( I have to copy it to the main memory and execute it from there myself. And then figure out how to delete it. And what to delete. And when. Arrggghh! And do I run it with SysUIAppSwitch or with SysAppLaunch? I'll post more questions relevant to this topic in a separate thread... > Some of the PalmOS events and notifications only support > lightweight or minimal processing and expect you to delay > anything more significant to a later time. Well, why isn't the documentation stating clearly what you can and cannot do from any particular notification?! Oh, you can't use globals unless your're launched normally. Oh, but you can, if you've launched yourself. Oh, but you can't use the user interface when launched with some launch codes. Oh, but nothing in the documentation tells you which ones they are. Arrgghhh! Come on, folks, why is this stupid thing so *limiting*?! Even on the cheapest devices, you have a couple of megs of memory and a reasonably fast CPU. I'm not asking for a protected-mode preemptive multi-tasking OS - but even Windows 3.x could do cooperative multi-tasking while running over MS-DOS on a 640 Kb machine with a similar CPU... Sigh. > I suspect your problems are caused by violating this rule. Yeah, well, you know who's going to have what kind of problems if reaction to security issues is "delayed to a later time"? :-) > One useful Palm OS characteristic is that alarms are not > responded to at certain points like this, so by setting an alarm > for "now" during this period, the alarm will actually be called > right after the OS processing has finished. A classic use of this > is responding to the HotSync event, where the program receiving > the event isn't supposed to do more than trivial processing and > the common trick is to set an alarm, taking advantage of the > suppression of alarms during HotSync, which ensures your program > is called right after HotSync completes. Thanks for the hint - scanning of the device after HotSync completes is another thing I want to implement. Although you're probably thinking of the sysAppLaunchCmdSyncNotify launch code - while I'm talking about reacting to the sysNotifySyncFinishEvent event. I guess I'll have similar problems there? Sigh... Regards, Vesselin -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
