View Single Post
Old 12-02-2014, 04:56 AM   #9
darryl
Wizard
darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.darryl ought to be getting tired of karma fortunes by now.
 
darryl's Avatar
 
Posts: 3,108
Karma: 60231510
Join Date: Nov 2011
Location: Australia
Device: Kobo Aura H2O, Kindle Oasis, Huwei Ascend Mate 7
Quote:
Originally Posted by Joeldmtl View Post
I don't agree with you when you say that because my Touch worked with an earlier FW version that it doesn't prove that it wasn't a hardware problem. What are you basing this on?

The only thing I can think of is that the memory in my Touch had some type of PARTIAL failure, so that it could not handle the requirements of the new FW. But not being a computer hardware engineer and not knowing the Touches memory hardware configuration, I don't know if this is a possibility.
Exactly. The fact that an earlier firmware does not show the same problems cannot exclude a hardware issue. Your own example is a good one. That is, a corrupt area of memory not used or seldom used by the earlier firmware. This is not only possible, but such a fault is more likely to become apparent with later firmwares which may add additional features and consume more hardware resources, including memory. The example given by GeoffR is also a good one.

In fact, I have difficulty seeing how the problem you describe could be anything but a hardware fault of some description.
darryl is offline   Reply With Quote