Thread: Error communicating with device
View Single Post
Old 04-29-2014, 10:55 PM   #9
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 Odyssee View Post
Thanks for your help. I cleared all temp directories (on my Win 7 machine). There is lots of free space on my HD. Could it be that the database on my device is corrupt? In that case I suppose a reset to factory settings is the only thing to do?
It might be a corrupt database. The errors reported are usually more obvious.

A factory reset is usually overkill. You can logout on the device and that will generate a new database during the setup. This will also add all the books that are on the device back in.

Quote:
Originally Posted by DoctorOhh View Post
I now nothing about this device but this error happens as theducks inferred when your device is formatted using fat 16 (FAT 32 is not subject to the same problem) and you have a bunch of files in the root directory. Simply place your books in a sub directory and right click to configure your device to use sub-directories. It looks like the device default is to use sub-directories.
The partition on the device that calibre can see is formatted as FAT32. This is done by the device during set-up or a factory reset. I don't think the device would work if someone had manually formatted it as FAT16. Plus the database file that seems to be causing the problem is in a sub-directory.
davidfor is offline   Reply With Quote