>All these are basically software sync failures due to increased tick/sec,
>but is there any change that the hardware can get damaged by using this kind
>of overclocking utilities. For instance, could the unit life time be lowered
>significantly, could the CPU get overheated...
I'm not a hardware engineer, so I couldn't speculate about what could
happen on a physical basis to the components. However the #1 thing you
could expect, if you raised the clock rate enough, would be losing data and
corrupting applications. Where precisely that limit is, will depend on the
precise physical nuances of your specific hardware, and probably the
temperature of your room and/or pocket, the phase of the moon, etc.
Parts are guaranteed to work at speed X. That means the manufacturer has
convinced itself that his parts on average work up to speed X+Y, and that
he knows the quality doesn't vary more than Y. (Quality can vary due to
slight physical differences in the materials, slight imprecisions in the
manufacturing process, any normal source of natural variation.)
So if you get an average part, you could overclock up to X+Y. If you get a
great part, perhaps you can overclock up to X+Y+Y safely. If you get a
part whose limit is exactly X as advertised, then you can't overclock at
all without losing data or having the parts fail in some way. Which is why
the finished devices ship at X: the manufacturer guarantees they'll work
that way.
Overclocking is going beyond the safe zone. The only way to find where it
isn't safe any more, is to try it until it fails.
How fast can you drive before you crash? Only one way to find out! But do
you want to?
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
