Thread: Kobo Firmware 3.11.0
View Single Post
Old 11-07-2014, 10:27 PM   #316
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 Ripplinger View Post
That nasty "error communicating with device" tortured me for awhile. There was nothing wrong with the database, it was just the combination of Calibre with my Kobo reader while on WinXP with an AMD processor. And it would happen on every single connection of the reader. I might be able to transfer 1 book at most once in awhile, anything else would then pop up the error. This started happening with firmware 2.5.x and was told pretty much nothing could be done, and it definitely wasn't Kobo's doing, they didn't change anything that would affect communication between PC and reader.

However I tried downgrading to firmware 2.4.0 and the problem completely disappeared on the same WinXP machine with an AMD processor. That's one of the main reasons I stuck with 2.4.0.

This summer I installed Windows 7 on 1 of my 3 PCs, the main one I use, when I upgraded the motherboard and CPU (still AMD), so the problem doesn't happen anymore even with new firmware. But I'm still convinced Kobo made some change, otherwise 2.4.0 wouldn't have worked perfectly.
That problem had me baffled. The PC and its drivers shouldn't have mattered. But, Kobo must have had a change at that firmware version to affect this. I just don't remember being able to see it. Hopefully the newer machines won't have a problem.
davidfor is offline   Reply With Quote