View Single Post
Old 12-26-2015, 03:15 AM   #18
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 Ad2 View Post
I was having the same problem as the opening poster Aliarides - only difference is that I'm using a Kobo.

In Metadata plugboards I used all the same info as in the opening post but just changed device from Nook to Kobo. No success. Then tried KoboTouch. No success.

But when I tried 'any device' it worked.
Firstly, you do need to use the correct driver for te device. The "Kobo" driver is for the original Kobo and the Kobo WiFi. The "KoboTouch" driver is for all the devices starting with the Touch. But, the usual reason that selecting the KoboTouch driver here and in other places doesn't work, is that the KoboTouchExtended driver has been installed. If it is, then it will be used in place of the KoboTouch driver and should be selected here.

If that isn't the case, I would like to see a debug so that I can work out what is going on.
davidfor is offline   Reply With Quote