Srinivas, When booting, the OS iterates over all databases, sending the sysAppLaunchCmdSystemReset command to those that contain applications. When iterating, the OS keeps an index of the database it is currently visiting. When a new database is created, this index can now point to the previously-visited database, as the new database can effectively move all others down in order. Thus, when the index is incremented to the next database, it comes back to yours, sending it the sysAppLaunchCmdSystemReset message again.
I don't know if this effect is documented, but the Palm OS engineers I spoke to about this problem a couple of years ago didn't seem too concerned about fixing it. -- Keith At 4:12 AM -0800 1/15/02, Srinivas Padmanabhuni wrote: >I am creating a database using DmCreateDatabase within an >application, which i am launching using the >SysAppLaunchCmdSystemReset. Once i cause a soft reset my application >gets launched and the database gets created alright. But what I get >is a second call to my application thru the >SysAppLaunchCmdSystemReset. I have seen if I do not create the >database, the second call does not come. > >Can someone please tell me why this second call is coming. -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
