View Single Post
Old 08-08-2016, 07:23 PM   #58
eschwartz
Ex-Helpdesk Junkie
eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.eschwartz ought to be getting tired of karma fortunes by now.
 
eschwartz's Avatar
 
Posts: 19,421
Karma: 85400180
Join Date: Nov 2012
Location: The Beaten Path, USA, Roundworld, This Side of Infinity
Device: Kindle Touch fw5.3.7 (Wifi only)
I am pretty sure Kobo is using bog-standard `mkfs.vfat` to create the drive, I don't see what is so obscure about that.
Perhaps something about the way it is exported?

Regardless, the fact that every operating system for years and years and years has never had a problem, up until this one version of one operating system, implies that it is indeed Microsoft's fault.
And I very much doubt it is necessary for whatever reason they may have had to modify the USBMS driver.

...

Yes, ideally Microsoft will fix this rather stupid bug.
But I guess Kobo cannot rely on that.

I do wonder how Kobo can possibly fix it properly, given that their devices keep a factory restore firmware which will still contain the code which triggers Microsoft's bug.
eschwartz is offline   Reply With Quote