View Single Post
Old 10-22-2014, 08:48 PM   #2
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
Sorry, I meant to look at this last night when I had access to the driver code to check. Your post in the Kobo forum reminded me.

I will check tonight, but, could you run calibre in debug mode, connect the device and post the log? The log shows a lot of information that can help me with this. Debug mode can be started from calibre by right-clicking on the preferences button and selecting "Restart in debug mode". Calibre will restarted, then connect the device, wait for the device jobs to finish, or the error to display, and close calibre. The log will be displayed. Post the full contents of the log.

Also, after this error, can Windows still see the device? Can it access the drive?
davidfor is offline   Reply With Quote