I'm using POL, so I inherit the functionality of CPalmApp. I redefine the function CPalmApp::AppStart, and I don't think my app responds to any other launch codes. If I'm adding code to that module, it breaks, so the only thing I can figure is I've exceeded some jump distance. I had this problem before & solved it by rearranging the segments. I feel about as dumb as a stick when I do this sort of thing - how can I tell which segment is causing the problem? It will link up just fine, so I think the modules that execute when the program executes aren't the problem. It must be some code in the linked libraries, that gets executed after the program is loaded during a hotsynch, that's causing all the trouble. Which means, it can't be any of the segments that contain only my program code, but must be isolated to segments 1,2,3 or 4, where the libraries are. The only custom code I have is my CPalmApp source in segment 1. The rest of the first 4 segments is POL and Palmos libraries.
Segment 1 contains a few files, don't have it in front of me right now, but there's I think a PalmOS library, then my app.cpp, then a POL library, and starter.cpp, which contains the _startup routine. Something like that. Anyway, I've got my app.cpp sandwiched in between the two libraries so it won't have to jump more than 32K to get to any of the functions in either one. Ben gave me a list of what has to be in segment 1, and that's all that's there. My first thought was to reduce the size of my app.cpp as much as possible, so for instance my implementation of CPalmApp:AppStart now has one line in it - "return utStartApp();", which is defined in another file, utilities.cpp, in another segment. The size of segment 1 has gone down considerably, but still I get this error. Thanks for your help -Mark (((feeling even dumber than a stick today))) --- Robert Moynihan <[EMAIL PROTECTED]> wrote: > Mark Chauvin wrote: > > > Does the fact that I get the error when I install > the app give a clue > > of where the problem is? It's after the emulator > says "Cleaning Up". > > My app isn't even running yet. > > I've not seen a problem like this in my testing. If > an app compiles > correctly, without memory warnings, then it has > always installed > correctly to the device or simulator/emulator. > There may still be > embedded bugs that would cause problems upon > launching the app, but not > during the install. > > The first thing I would look for is an error in any > code that is > processed in response to a sysAppLaunchCmdSyncNotify > launch code. This > stuff will happen automatically upon completion of > the hotsynch, and an > error there can easily cause the type of bug that > you describe. ANY app > that responds to that launch code may be causing > this problem, not > necessarily yours. But, if you can get the error to > turn on/off by > editing your code then it certainly would point to > your app. Try > commenting out any code that you run in response to > that lanch code and > see if the synch works. > > Bob. > > -- > 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/
