Thread: Glo Can't sideload books (again!) onto my original Glo
View Single Post
Old 10-08-2017, 07:05 PM   #4
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 ilovereading.com View Post
Hi

So it was a software update issue?

I don't know what the 9960 build means or how it can help me?
"9960 build" refers to the version of firmware Kobo released last week. The full version number is 4.6.9960 and is discussed in this thread. This has a fix for the downloading from via the browser bug. Unfortunately, due to a performance problem in the firmware, Kobo stopped rolling it out over the weekend.

Exactly what you should do depends on the firmware version you are running. This is shown on the "Device information" page of the settings. There has been two recent problems with the external SD card. One is with sideloading kepubs onto it, the other is the card is ignored if it doesn't have a label. I cannot think of any other issues. Both of these problems have been fixed in later firmware.

I do occasionally get a problem when inserting the card, but it usually means I fumbled when I was inserting the card and it didn't register properly. When this happens, the message I see is frequently the message you are seeing. Popping it out and back in always solves this.

It is possible that a firmware update has dropped support for FAT16 formatted SD cards. All of mine are formatted as FAT32, so I wouldn't have hit this problem. It could also be Windows messing with the card in a way that the device doesn't like (yes, if all else fails, blame Windows ). Whatever is happening, I would recommend reformatting the card, or another as FAT32. Between the long file name handling and things like the limited number of files in the root directory, FAT32 is the better format for the card.
davidfor is offline   Reply With Quote