View Single Post
Old 06-06-2020, 04:21 PM   #3
ZodWallop
Gentleman and scholar
ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.ZodWallop ought to be getting tired of karma fortunes by now.
 
ZodWallop's Avatar
 
Posts: 11,479
Karma: 111164374
Join Date: Jun 2015
Location: Space City, Texas
Device: Clara BW; Nook ST w/Glowlight, Paperwhite 3
Quote:
Originally Posted by DNSB View Post
Unless you have the original Kobo or the Kobo WiFi (the ones with the D-pads), you don't need the Kobo Reader Device Interface driver. OTOH, my tests with disabling drivers I would not be using did not show any speed gain, lower memory use, etc.

The only reason for disabling the KoboTouch driver when using the KoboTouchExtended driver or vice versa is that they address the same family of Kobo devices.
I disabled KoboTouch as it was doing the same thing as the extended and I worried that two plug-ins trying to do the same thing at the same time might cause issues. That was my same reasoning for thinking about disabling the Kobo Reader Device Interface plug-in. If there's no harm letting both run, then no worries.
ZodWallop is offline   Reply With Quote