Chipp Jansen wrote:
Thanks for the reply! I'm not using an globals (and checking the subLaunch flag) in the load. In fact, it's before my app. is launched that it's causing the problem. Do we have any idea what's going in emul68kcommon.c at the point in the code? I know that Palm knows...
It doesn't matter much what emul68kcommon.c is doing exactly at this place, but in general it is doing the m68k emulation to let your app for example or any other app which has itself registered for the Reset notification, know about the reset which just occure. If you're sure, you didn't registered for the notification and you're sure you don't have code accessing other segments (than segment 0) or global variables during none-normal lauchcodes, then it might be still your app which trashes memory so badly, that the OS doesn't even can reboot anymore. Have you ever checked it with the simulator or even better the emulator, at least the parts which could run?
Regards Henk -- ------------------------------------------------------------------------- Henk Jonas [EMAIL PROTECTED] Palm OS ® certified developer Please contact me, if you need an off-site contract worker. ------------------------------------------------------------------------- -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
