View Single Post
Old 09-01-2020, 10:04 PM   #14
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 Gadgetguy View Post
Just for context - I had these errors with a brand new (well, refurb) Forma reader, and removing the plug in's solved it... So as far as I am concerned there is 100% an issue with the plug ins
Sorry, that is bullshit. You have stated this before with no real evidence. I don't even think you bothered to mention what plugins you thought were causing the problem. Even the use of the plural for the plugins is a problem as there is only one that could even remotely be causing a problem. And even that is doubtful as 95% of the code used is actually in the built-in KoboTouch driver. Nearly all of the extra code acts on file on your computer before they are sent to the device.
davidfor is offline   Reply With Quote