"Ben Combee" <[EMAIL PROTECTED]> wrote
>
> The emulator shipped with CW is several versions out of date. Since it
> was released, there have been 4 updates to it -- the latest version is
> 3.3, and you really should update.
>
Yes, I've been using 3.2 for a while. Damn fine product.
> > The prc loads and runs fine on the emulator, it's the debug attempt
> that
> > produces the problem.
>
> OK... so, when you install it manually, no problem. I think I've seen
> problems like this when applications have bitmap families missing
> members, or other oddness in the resources.
>
Ahh. We had an unexplained corruption with a bitmap for a splash
form. Since we couldn't resolve the corruption using Constructor
(couldn't even work out what was wrong) I just stopped displaying
the splash form and went back to higher priority work. Looks like
I'll have to deal with this now.
Nope, wait a minute, this problem also occurs with another project
so it can't be that bitmap. But that thought got me testing and the
common denominator seems to be apps that are linked with a large
static library we're developing. This library had pushed past 64K but
still seemed to be functional. Perhaps it's size is now revealing problems
that were hidden before? I guess I could split it up into two libraries
and see if that fixes the problem.
> > My problem is slightly different using the PalmOS 4 debug ROMs -
> > the message changes to 'Unknown error code 0x%04x' (still with the
> > Metroworks CodeWarrior title).
>
> These sound like DbgMessage's coming from the Palm OS ROM.
> Try changing the Palm Debugger Setting "View log" to turn the log on.
> Do these messages show up in the log window instead?
>
Nope. The log window never appears for either the 3.1 'not registered'
or the 4.0 'unknown error' message.
Chris Tutty
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
