Thread: Glo Calibre/Kobo Glo "error communicating with device."
View Single Post
Old 08-15-2013, 12:04 AM   #48
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
I didn't use Calibre at all for this one swap. Calibre transferring ebooks on my WinXP machine always ends up with the failed error and the reader being disconnected.
I've since discovered from the great help in this thread that using my pokey netbook that has Windows 7 on it does work without any errors, so when I transfer any number of books, I do it through the netbook (which is a pain since I use it for travel and rarely have it running at home). But it was a method that worked to make use of Calibre and how it can send titles, shelves, etc.
I just assumed from the rest of the posts that it was through calibre. On my aging Win7 laptop, I don't see any of the problems that have been reported. I have to fire up an old XP laptop I have sitting around and see what happens.
Quote:
But to swap one book only that I was currently reading today I just did a drag and drop to the Kobo Glo, making sure Calibre wasn't sitting in the system tray. I didn't think it would have to do any reloading of content since file names were identical.
Quote:
Originally Posted by DNSB View Post
At one point, I remember that changing the file size caused the book to be reprocessed.
This changed with firmware 2.8.1. Before that, if the book was on the main memory, it would get completely removed from the device: the file would be deleted and the database entries removed. But, if it was on the SD card, the database entries would be removed and the book processed and added as a new book. With 2.8.1, replacing a book on the main memory works the same as for the SD card. And yes, it is triggered by a change in file size.
davidfor is offline   Reply With Quote