At 06:42 PM 8/14/2005, you wrote:
So can you answer a question for me Ben? If I am handling notifications in the "background" (ie. my application is no longer the running applicaiotn but is responding to registered notifications) How do I reliably use callbacks on an NVFS system? I think the same question holds true for ProcAlarms. I can't seem to maintain any level of stability using these techniques. Will the memory addresses used in the registration process for both of these calls (callbacks and ProcAlarms) remain valid if I lock down code segment 1?
The NVFS code should never move a locked handle. However, since the original NVFS code was tied to database records rather than memory handles, the best way to ensure stability is to use notifications that use launch codes instead of address-based notifications. If you do pass the address, make sure that you've done a DmProtectDatabase, and you lock your resource handle, and you don't call DmReleaseResource on the resource either.
-- Ben Combee, Senior Software Engineer, palmOne, Inc. "Combee on Palm OS" weblog: http://palmos.combee.net/ Developer Forum Archives: http://news.palmos.com/read/all_forums/ -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
