Thread: Thinking about returning to kobo
View Single Post
Old 08-27-2016, 09:26 PM   #24
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 johnnyb View Post
That is entirely possible in my case... Guess Kobo’s not *really* to blame but they could do what Amazon (and Tolino, Pocketbook, Sony, basically everyone else outside the reader business) can do, write a USB driver that’s not that extraordinarily sensitive...
What makes you think that any of those companies wrote a driver? I think you will find that none of them did. The are all mounting using the Windows USB drivers, most likely the USBMSD driver. What Kobo did was use some bytes in the boot sector that had no predefined use for something. MS decided that this was a problem and hence the errors Win10 gave. Kobo probably shouldn't have done things this way, but it has been like that for at least five years. The question then is why did MS suddenly decide it needed to change this? And why didn't they tell anyone?
davidfor is offline   Reply With Quote