View Single Post
Old 09-25-2016, 01:34 PM   #285
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,084
Karma: 169815798
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
So your saying that the current Win 10 does work correctly with Kobo? If that's not the case, then any discussion in this thread is off-topic as there would be no more problem.
How are you defining the current Win 10 version? To me it's Build 14931.1000. For you, it likely to be that antique 14393.187 which is patched to work with Kobo ereaders -- or more precisely, software defined mass storage devices with non-standard boot sectors. Since that is not a preview build, it's off-topic here.

Until the next CB release of Windows 10 (rumour has it that Microsoft is looking at two major updates to Windows 10 in 2017, check Nathan Mercer's blog at What New For IT pros in the Windows 10 Anniversary Update) or until Microsoft supplies an update to Windows 10 AU which breaks USB connections to Kobo ereaders, my personal opinion is that maundering about using the CB release is extremely annoying behaviour.

I don't know about other people in the Insider Preview program, but around here, we don't run preview builds in our production environment. We do run Windows 10 and preview builds in our test lab and it is very useful for us in finding potential issues so we can attempt to fix them prior to rolling out Windows 10 into our production environment. If nothing else, it's going to be 'fun' to redo all our group policies and then test them.

Anyhow, 'nuff said. It's past time to send JSWolf to Coventry.

Last edited by DNSB; 09-25-2016 at 01:45 PM.
DNSB is offline   Reply With Quote