View Single Post
Old 08-06-2016, 05:29 PM   #84
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,450
Karma: 171313058
Join Date: Jul 2010
Location: Vancouver
Device: Kobo Sage, Libra Colour, Lenovo M8 FHD, Paperwhite 4, Tolino epos
Quote:
Originally Posted by taos View Post
I think - if you still have access to a pre-Anniversary Update computer - it might be easier to just use the Windows 10 system that can actually still see the KOBOeReader partition to do the formatting. You don't have to switch computers after the backup, and it will only be one step since you don't have to repeat the formatting.
My original pass at this issue involved doing the backup on my physical machine and then switching to the VM with the Windows 10 Preview to do the create simple volume/etc.

Quote:
Originally Posted by taos View Post
BTW, I tried to format with an Anniversary Update Windows 10. I had to first create a partition in disk management before I could format the unallocated space. I was not asked to repeat the formatting - I could even copy everything back onto the new partition. However, after restarting, my Kobo Glo HD just hang. I had to remove its internal microSD card (that I could not mount with the Anniversary Update but with the older November Update - at least the third partition with FAT32). It seems that all files got corrupted somehow as I could only see those typical fsck chunks that are left after a file system check gone wrong. I had to reformat the last FAT32 partition again so that I could reboot my Kobo. Afterwards, I could connect it again to the computer (November Update), reformat it (just to make sure), and copy everything from the backup. After a restart everything still works fine. I can mount the KOBOEREADER partition (it seems Windows doesn't like lowercase characters in volume names) in both Windows 10 November Update and Anniversary Update.
Interesting with the hang. I haven't had that issue either of the two times I've done the create volume/format/restore backup (once with a Preview build where it broke in a few weeks, the second time with the Anniversary update). As for the volume name, Windows seems to like converting lower case to upper case for them. Microsoft's case sensitivity depends on which APIs you are using.
DNSB is offline   Reply With Quote