>I suppose this seems more of a customer support issue than developer
>support, but as our app is expected to require Palm OS 3.5, it affects
>development too.
>
>I've read recently that applying the Palm OS 3.5 upgrade can
>render a Palm
>device unusable;
Yes, if you yank it out of the cradle halfway through a flashing process.
=) But then, usually I've been able to set the unit back into console
mode and restart the flash process.
>allegedly writing to the flash ROM more than once will
>damage it. Does anyone know any more about this issue? Perhaps it's a
>misunderstanding, or only applies to a small batch of defective Palm
>devices, etc. I hope that's the case.
There are devices that don't really have onboard Flash memory, but have
masked ROM, like the Visor, m100, pre-Palm III's, etc. Obviously, those
cannot be upgraded. They're not defective in any way, but just built
with a different technology.
I've flashed a Symbol SPT 1700 many times, and had no problems. I've
flashed Symbol SPT 1500's (built on the Palm III architecture) and had
no problems as well. Flash memory is sturdier than you may think. =)
Hope that helps!
-Rus
http://www.act.avnet.com/
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
