My first guess is that you didn't get all necessary functions into
the first segment. As a rule of thumb, any function called directly
from a first segment function (i.e., one that NEEDs to be a first
segment function) must be in the first segment. If it is called
by the system (i.e., a form's event handler) it doesn't need to
be in the first segment. But, of course, finding the offending
little guy is another matter.
As a practical person, were I in your shoes, I would launch the
application under the control of a debugger (Metrowerks works just
fine for this) stopping at the first line of PilotMain, then single
step until I hit the crash. If you can do this and if the problem
is as I conjecture, the offending call should stand out like a
sore thumb (stack traces are great)...
-----Original Message-----
From: Ayers Family Member [mailto:[EMAIL PROTECTED]]
Sent: Friday, April 20, 2001 6:37 AM
To: Palm Developer Forum
Subject: MSL problem! Help!
My application has grown past puberty and needs to become a multi-segmented
app. As always, I went to palmos and looked at their Knowledge base. It
clearly tells me that I need to replace StartupCode.lib with MSL Runtime
Palm OS (2I).lib (for non-4byte boundary apps) and make sure that Link
Single Segment switch is off and that all necessary functions exist in the
first code segment. I followed the instructions dutifully. Of course, I
wouldn't be writing this message if it had turned out in my favor.
I loaded the application into the Emulator (3.0a7), and upon opening the
app, the Emulator crashes hard. I have no idea why this has occurred. I
followed the instructions and it fails.
Jeff Ayers
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palmos.com/dev/tech/support/forums/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
