View Single Post
Old 05-17-2024, 01:24 PM   #45
DNSB
Bibliophagist
DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.DNSB ought to be getting tired of karma fortunes by now.
 
DNSB's Avatar
 
Posts: 47,242
Karma: 171291590
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by JSWolf View Post
@DNSB how did you solve the problem as you've had it as well?

https://www.mobileread.com/forums/sh....php?p=4343624
That thread was more about the database corruption issue. Otherwise, the name shown for a connected Kobo ereader depends on where you look at it. Other than with some Windows Preview editions, I did not see the incorrect driver being used.

For instance, my Libra Colour shows in the Safely Eject widget as eReader-4.39.22861, in File Explorer, it shows as KOBOeReader, in Device Manager under Disk Drives, it shows Linux File-Stor Gadget USB Drive and under Universal Serial Bus Controllers, it shows as a USB Mass Storage Device.
DNSB is online now   Reply With Quote