I just did some tests that shows it's a hardware problem. I returned the
Palm back to it's virgin state by deleting my app and then doing a hard
reset. Turning it on now gives me a weird display that looks like a cross
between prison bars and a UPC code. I also found that I can change the
pattern of bars by flexing the case ever so slightly.
Guess I'm off the hook.
'til next time.
> -----Original Message-----
> From: Elia J. Freedman [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, March 03, 1999 10:52 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Can a program break a Palm?
>
> Try uninstalling your app, soft reset and play with it. Also, run
> gremlins
> for a while on your application with POSE. If you are accessing low
> memory
> or writing over something, a fatal exception can happen. The debug rom
> will
> pick up almost all memory imperfections. I had an application on my Palm
> III (not mine) that seemed to work fine but caused a fatal exception
> everytime I tried to do a system find. And it was a very simple
> application
> that I don't think needed to do anything special as far as code is
> concerned.
>
> Elia
>
> -----Original Message-----
> From: Fawcett, Mitch [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, March 03, 1999 6:51 AM
> To: 'PalmDevForum'
> Subject: Can a program break a Palm?
>
>
> What's the likelihood that one of my programs could trash my Palm? In the
> program I am writing I only use the documented API's. I don't get into
> memory management beyond what's in the GNU tutorial and the O'Reilly book.
> I don't use hacks (not even sure what they are).
>
> It's a replacement Palm that I just got from 3Com. A few minutes after I
> hotsynched and loaded my program, I started having display problems and
> fatal errors in all my apps, including the built-in ones. Unfortunately I
> didn't spend any time using the pilot before I hotsynched, so I don't know
> if it would have had the problem anyway.
>
>
>
>
