The pilotmain for my app only responds to the normalLaunch event. I fixed that last time per Ben's suggestion. Does the program execute anything else on installation, like a dll-self-register kind of thing? I'll double-check the code later tonight & make sure the pilotmain isn't changed somehow.
If the problem is it's trying to execute a jump that's past 32k, is there a way to trap it & see where the jump is coming from? I started my program with cw and then installed it into the emulator, using the hotsync to local network & localhost, then it crashed and codewarrior stopped the thread in the middle of some assembly code, which I couldn't decifer. Dont' know if that's where the break really occurred, but since it looked like Greek anyway, didn't do much good. Or am I going about that the wrong way? Thanks for your help -Mark --- David Fedor <[EMAIL PROTECTED]> wrote: > At 10:04 AM -0800 1/20/05, Mark Chauvin wrote: > >Ben, is that the only notification that happens > when > >an app is installed? Which module is it in? > > There are many launchcodes which an app can get. > Including the ones > which tell you a soft reset happened, that the time > was changed by > the user, that a HotSync operation finished, etc. > > You need to structure your app such that you only > use globals, jump > to other modules, etc. when you're in a normalLaunch > situation or > another one which you KNOW to be safe. > > Typically a PilotMain routine is not much more than > a case statement > looking at the launch codes, and not doing anything > for the default > case. > > -David Fedor > PalmSource, Inc. > > -- > For information on using the Palm Developer Forums, > or to unsubscribe, please see > http://www.palmos.com/dev/support/forums/ > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
