Nick Anderson wrote:
> Problem: Can't seem to build a program that will run on a Personal ROM,
> that works fine on OS2.04 Professional, TRG boards, Palm III, Ez etc.
>
> File D/L proceeds fine, at the point where I am usually dumped into
> PilotMain, I am instead dumped into assembler [...] with the following
> messages in the Stack
>
> 0x10C5B430(_Startup_)
> 0x10C5B678(PilotMain)
> 0x10C093F2(SysAppLaunch)
> _Startup_
> (0x10C19DC0)ErrDisplayFileLineMsg)
Well, __Startup__() is your app's entry point in the startup code
library. The source is PalmOS_Startup.c included with CodeWarrior.
(Actually the bottom __Startup__ is you, the top one is UIAppShell, but
that's not important here.)
Just looking at PalmOS_Startup.c I see the only ErrDisplayFileLineMsg
call is the ErrDisplay macro after SysAppStartup. It seems to be trying
to report that SysAppStartup returned a failure code. So something is
going wrong before your PilotMain ever gets called.
<GUESS>
Your app may have a large data resource (static/global segment) which is
too big for the 2.0 dynamic heap. During startup the OS tries to
uncompress your data resource into a fresh heap chunk, and this may be
what is failing. If so, you need to reduce your static and global data
size. Look in the linker map file, or in the Data column of the
CodeWarrior project window. How big is the total?
</GUESS>
--
Scott Johnson
Oracle Corp.
(sorry if this is a 2nd posting...)
