View Single Post
Old 07-22-2017, 10:00 PM   #75
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
Quote:
Originally Posted by Blossom View Post
Yes the firmware before that one worked fine with Dropbox. I downloaded a few books then sync. It asked me to upgrade to the version in the quote so I did. Right after I upgraded I went back into Dropbox and it no longer work.

And just for the record I'm not reporting this, I just made a comment I hope the latest version fixes this problem and got flack for it.
No, you got flack because you made a statement about something and when I asked, you kept making statements that I could not agree with. You stated "broken completely for downloads". As I had downloaded quite a few files from several very different sites with the firmware version I believed you were using, I knew that blanket statement wasn't true. It took at least five posts before you bothered to mention that it was downloading from Dropbox was the problem. Because of how many problems there have been with Dropbox, that doesn't surprise me. And because of those problems, I'm not immediately willing to concede the problem is with Kobo. Or at least not just with Kobo. GeoffR's tests tell me that 4.5.9587 is broken, but that is something I already knew.

You also got flack because you kept using an indirect reference to the the firmware version. And because your experience was different to mine, that made me question whether I understood you. A simple statement of the firmware version number would have cleared that up. Or saying you couldn't check because you didn't have the device with you. It is frustrating to me when this happens as it can be amazingly hard to get people to answer a simple question like this to clear things up.
davidfor is offline   Reply With Quote