MobileRead Forums - View Single Post

Ron46 · 02-05-2011, 06:34 PM

I agree. Lucky recoveries do not add to the knowledge base. I think this is a low level failure that can be precipitated by a rapid, uncontrolled shutdown or other event. My problem with this is that the reset button is not a true reset, because when the reader starts up again, it tries to resume what it was doing before- run within a looped error and remain frozen. Even removing the batteries does not correct it.

I am not a machine code engineer, but there is a section of this reader (where the firmware resides) that we have no access to that can get corrupted. I would like to see a key sequence combined with the reset button that would clear this out so you could reload the firmware at any time. As it is now, if it is frozen, it does not respond to the Power/Right Arrow command for updating the firmware.

One could argue that this is a design flaw- the firmware section of the reader should never get corrupted unless you load bad firmware. It should not be dynamic i.e written to by the reader itself. In 20 or so years of computing, I have never seen a PC bios get corrupted all by itself. You must enter the bios and change settings or reload the bios to mess it up.

02-05-2011, 06:34 PM	#11
Ron46 Zealot Posts: 103 Karma: 110 Join Date: Nov 2009 Location: Massachusetts Device: JetbookLite, EB-1150, PalmIIIXE	I agree. Lucky recoveries do not add to the knowledge base. I think this is a low level failure that can be precipitated by a rapid, uncontrolled shutdown or other event. My problem with this is that the reset button is not a true reset, because when the reader starts up again, it tries to resume what it was doing before- run within a looped error and remain frozen. Even removing the batteries does not correct it. I am not a machine code engineer, but there is a section of this reader (where the firmware resides) that we have no access to that can get corrupted. I would like to see a key sequence combined with the reset button that would clear this out so you could reload the firmware at any time. As it is now, if it is frozen, it does not respond to the Power/Right Arrow command for updating the firmware. One could argue that this is a design flaw- the firmware section of the reader should never get corrupted unless you load bad firmware. It should not be dynamic i.e written to by the reader itself. In 20 or so years of computing, I have never seen a PC bios get corrupted all by itself. You must enter the bios and change settings or reload the bios to mess it up. Last edited by Ron46; 02-05-2011 at 06:41 PM.