The "PC-relative strings" box is checked, and I commented out the entire
program except:
DWord PilotMain( Word launchCode, Ptr cmdPBP, Word launchFlags)
{
Err err = 0
if(launchCode == Normal or SysReset)
{
char *dbNames[] = {/*bunch of strings*/};
}
return err;
}
It still dies :)
-----Original Message-----
From: Jim Schram [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 07, 1999 11:42 AM
To: [EMAIL PROTECTED]
Subject: Re: SystemReset limitations?
At 2:28 PM -0700 1999/07/07, Jeff Valore wrote:
>Can someone please explain what the limitations are for a program running
>after a reset (responding to a SystemReset launch code). I know there are
>no global variables available, but my program doesn't reference any, and it
>still dies on a reset. It runs fine on normal launch, and it does the
exact
>same lines of code.
>
>Here is the basic outline of the code:
>
>DWord PilotMain( Word launchCode, Ptr cmdPBP, Word launchFlags)
>{
> if(launchCode == Normal or SysReset)
> {
> char *dbNames[] = {/*bunch of strings*/};
Are you using PC-relative strings? If not, that may be the problem... make
sure those strings are stored in the same code resource as PilotMain.
Regards,
Jim Schram
3Com/Palm Computing
Partner Engineering
