funny thing is i'm debugging on the same unit i am running it on afterwards.
i did one thing where b4 i call anything, or do anything, i put a frmalert,
and it still gives the fatel exception when running alone. but when i run
it with debug it is ok. the only features i'm using work infact with a few
other apps (sysBatteryInfo, rf connection, and h.w. background light...)
-----Original Message-----
From: Tim Hewitt <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>; [EMAIL PROTECTED]
<[EMAIL PROTECTED]>
Date: Thursday, December 02, 1999 4:01 PM
Subject: Re: Debug and running
>Charles Rezsonya wrote:
>>
>> interesting thing happened today. i wrote up a small app that is quite
>> small. does just a few tiny things (this is using CW5). i run it
through
>> the debugger and it works properly, then i run it on the handheld and it
>> gives me a fatel exception. is there anything that the debugger might
skip
>> or not check that when ran on a handheld alone might cause it to crash?
>
>I know this is the obvious question, but are your testing using the same
>ROM revision as the device you are trying to run on? Calling a 3.n
>feature running on a 2.0 ROM will result in a fatal exception.
>
>-Tim
>--
>Tim Hewitt
>Principal Software Engineer
>Fairchild Semiconductor
>
