In my first message (below), I forgot to mention that when OS 5.0 reaches the 'new' operation, it does NOT create the object. The same code running on Palm OS 3.x or OS 4.x will create the object without error. I'm using the following library file: "MSL Runtime Palm OS (2i).lib" I don't think this is the problem, since the code works fine on OS3 and OS4. Sorry for not being more clear about this in my first posting.
Thank you, Kraig Ritmanich --- In [EMAIL PROTECTED], [EMAIL PROTECTED] wrote: I have an application that works fine on Palm OS 3.1 to 4.x, but does not work on OS 5.0 on both the Simulator and actual hardware. I determined that the problem occurs whenever the app reaches a point where I create a new object through the 'new' keyword. The application does not generate any fatal errors, it continues to run as if the object was actually created. What can I do to get this application to run on OS5? I thought that any code that worked on the previous OS would work fine on OS5 through POSE as long as the internals of the OS data structures are not accessed directly and there isn't any processor-dependent code in the app. Any suggestions? Thanks, Kraig -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/ --- End forwarded message --- -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
