View Single Post
Old 06-24-2016, 08:36 PM   #8
AnemicOak
Bookaholic
AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.AnemicOak ought to be getting tired of karma fortunes by now.
 
AnemicOak's Avatar
 
Posts: 14,391
Karma: 54969924
Join Date: Oct 2007
Location: Minnesota
Device: iPad Mini 4, AuraHD, iPhone XR +
Quote:
Originally Posted by davidfor View Post
The errors are in code that reads the settings. I think what is happening is that the configuration for the driver was damaged during the initial attempts to use it. Now there is something in it that is preventing it from being read properly.

The fix should be to delete configuration file. This is in the calibre configuration file and is called "device_drivers_KOBOTOUCHEXTENDED.py". Unfortunately, you will need to redo the configuration before connecting the device.
Thanks. This appears to have worked.


Quote:
For the collections, did you check the KoboTouch driver configuration before using it? If you used the driver for collection management in the past, the configuration could still be there and has come into affect now.
I didn't check the KoboTouch config before using it. Have never used Calibre for collection management in the past, but it's possible there was something there that messed it up. I only used that driver once when I first got the device, before I understood that I wanted to use the extended one.
AnemicOak is offline   Reply With Quote