Thread: Error communicating with device
View Single Post
Old 04-09-2017, 05:48 AM   #52
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
For this thread and some other reasons, I have been looking at the drive detection code in calibre. The attached file is a beta of the KoboTouch driver to handle this problem. It extends the device detection to make sure that the correct driver or mount point is used as the main storage. I have added code for this for Windows, OSX and Linux. It has been tested for all three OSes, but the Linux and OSX testing was done with virtual machines.

To use this beta, you need to download and install it. Then, disable the KoboTouch and KoboTouchExtended drivers. The configuration for each driver is separate. You will need to copy the configuration from the driver you normally use.

If this works, I will add the changes to the built-in driver. Please test this beta and tell me how it goes.
Attached Files
File Type: zip KoboTouchBeta.zip (1.4 KB, 120 views)
davidfor is offline   Reply With Quote