View Single Post
Old 08-28-2016, 05:24 AM   #26
johnnyb
Cloud Reader
johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.johnnyb ought to be getting tired of karma fortunes by now.
 
Posts: 1,124
Karma: 4000066
Join Date: Aug 2010
Device: Kindle Oasis, Kindle Scribe, iPad Pro 11
Quote:
Originally Posted by davidfor View Post
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?
I was talking about the Kobo-Mac connection (and of course, the implementation of USB on the side of the device). Please refer to post I quoted.
johnnyb is offline   Reply With Quote