View Single Post
Old 09-02-2011, 10:43 PM   #106
cutterjohn42
Addict
cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.cutterjohn42 ought to be getting tired of karma fortunes by now.
 
Posts: 274
Karma: 1029955
Join Date: Feb 2009
Device: Palm IIIx, EBM-911, REB-1100(dead), PRS-505
Quote:
Originally Posted by the.Mtn.Man View Post
So the update is supposed to fix the storage error, but if your device has the storage error then it can't update? That's ironic.

But my Kobo Touch appears clean (no error message when I cycle the power), so that's not the problem for me. I notice you're in Canada, so maybe the update just hasn't been propagated to the US servers yet.
Actually this is a legitimate limitation. They cocked up, and can't restore db consistency so you've GOT to restore to a known good state BEFORE updating, o.w. you'll be left in the same mess or likely even worse off.

The REAL problem is that this bug occurred at all! They've got some major sw process problems that need to be addressed.

[EDIT]
NEW BUG FFS! PREPEND AT LEAST HTTP:// to IP ADDRESSES AND DOMAIN NAMES FFS!

i.e. IP addr phail whale w/o http:// manually added christ!
[/EDIT]

Last edited by cutterjohn42; 09-02-2011 at 10:52 PM.
cutterjohn42 is offline   Reply With Quote