View Single Post
Old 08-07-2016, 11:59 PM   #38
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 Dave R View Post
Couldn't agree more . If the people on this forum can come up with workarounds so quickly, then Kobo developers ought to be able to do the same.
These are completely different things. The people on this forum have found a workaround that can be used by other people with a reasonable amount of technical knowledge. And probably won't survive a factory reset.

And we haven't actually worked out why it is happening. All we know is that Win10AU doesn't like something about the partition that the Kobo device is presenting it. We don't know what it is that is wrong. Is it the partition, or the file system? Or something else.

Kobo need to come up with a solution that any user at any level of competence can do. And preferably without losing data. It probably will need a format of the partition, but, hopefully it won't need a factory reset. The solution also has to survive a factory reset. And it has to continue to work with Macs. And hopefully continue working with Linux machines.
davidfor is offline   Reply With Quote