Yes. I tried the up-key several times, it had no effect. (Which confused me,
since Palm said it was due to third party software, and I thought the up-key
reset was supposed to not notify the apps, etc) Your probably right about
the debug mode, thanks. Any idea how to get out of that mode without a hard
reset?
Anyway, my program does use the ptdynlib.prc from Symbol for printing. But
the up-key doesn't affect anything.
Thanks
Howard C. Shaw III
Programmer
Tyrol Data Systems
----- Original Message -----
From: "Peter Hebert" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, July 03, 2000 3:52 PM
Subject: Re: Palm IIIxe stuck in reset cycle
> Are you sure you need a hard reset to get out? You might be able to get it
> to get out of the loop by holding down the up-key ("Don't load shared
> libraries") during a reset cycle. (When you got to the blinky-box mode
> before it was probably because you hit the down-key at the right time).
>
> Does your program use/include shared libraries?
>
> Peter
>
> Howard C. Shaw III <[EMAIL PROTECTED]> wrote in message
> news:<16136@palm-dev-forum>...
> >
> > I recently recoded my company's Palm application to work with OS 3.5. I
> took
> >
> > the short route of including the palmcompatability headers to get the
> > program out more quickly.
> >
> > Now I find that on the OS 3.5 IIIxe's, if the user resets the palm, and
> then
> > resets it again while the Palm splash screen is still visible, the Palm
> will
> > enter a reset cycle. It can be seen to be visibly resetting continously.
> > This is NOT due to the reset button being held down, since I can still
> feel
> > the reset button go down and back up upon the insertion of a paperclip.
> >
> > I did manage once, though I'm not sure how, to break out of the cycle,
but
> > it dropped me to the low-level debugger hookup (with a blinking black
> square
> > in the upper left, even across resets).
> >
> > In either case, the only way out is to perform a hard reset.
> >
> > When the first of our customers encountered this, they contacted Palm,
and
> > were informed that it was due to third party software on the handheld. I
> > have verified that I only get the behavior when my program is on the
palm;
> > i.e. it does not occur after a hard reset.
> >
> > However, the very same code, loaded onto a Palm IIIx, does not exhibit
> this
> > behavior.
> >
> > So while it is indeed in some way due to the presence of my code on the
> > machine, it is also peculiar either to the Palm OS 3.5 or the IIIxe
> > hardware.
> >
> > Does anyone have any idea what my code could be doing to cause this? I
> only
> > respond to the standard launch code, ignoring all the other launch
codes.
> > What changed from 3.x to 3.5, or IIIx to IIIxe, that caused this problem
> to
> > surface, and how can I resolve it? This is particularly disturbing due
to
> > the necessity of using a hard reset to get out, causing data loss.
> >
> > Howard C. Shaw III
> > Programmer
> > Tyrol Data Systems
> >
> >
> >
> >
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
