'Processing / Importing content from an SD card'...My Gripes

[compurandom]

As almost suggested, you could also put a portion of your books in a hidden folder, let the rest process, and then move some out of the hidden folder, and process again...

Smaller batches might be more likely to succeed.
I've had to do this a couple of times after database corruption and a factory reset.

Usually database corruption is caused by me being stupid and forgetting to eject before unplugging the usb, but occasionally from some combination of stranger events.

[JSWolf]

The problem could be some book that has errors. You need to check all of them and see which ones have errors, fix the errors and then you can load them.

[davidfor]

Originally Posted by Telemachus

Nickel only processed about 3000 books, something went wrong,

It probably means that there was a bad book in there that failed to be processed and stopped the rest. Or that the battery ran out before it finished.

the interface also became sluggish. Too many books I guess.

I have close to 5000 books on my Glo HD. They've been added over the last couple of years. The interface is probably slower than when I started, but not enough to worry me.

I tried the hidden folders approach and it worked elegantly with KOReader. No slowdown in performance. If this solution isn't in the tips and tricks thread it should be.

Yes, you should suggest it get added to the KOReader tips and techniques.

[Ken Maltby]

Good, Bad, mildly objectionable, KOReader will likely still be able to display the text in the file using one of its two reader engines Coolreader 3 engine (cr3) or the MuPDF based engine. Although there are those at the Github project who want to take the User Interface (UI) in a more graphic and data collecting direction, so far any feature that requires extensive "processing" of the files, can be optionally disabled. There is currently no check on the "quality" of the book format, of the file as it is added to the file structure, just the normal checks that it is a structurally sound file with one of the many extensions that the KOReader reader engines can handle. (Some extensions that could be read, are not normally implemented, but can be added.)

There is no special treatment that differentiates between files for ebooks bought from Kobo and those acquired elsewhere.

Luck;
Ken

[davidfor]

Originally Posted by Ken Maltby

Good, Bad, mildly objectionable, KOReader will likely still be able to display the text in the file using one of its two reader engines Coolreader 3 engine (cr3) or the MuPDF based engine. Although there are those at the Github project who want to take the User Interface (UI) in a more graphic and data collecting direction, so far any feature that requires extensive "processing" of the files, can be optionally disabled. There is currently no check on the "quality" of the book format, of the file as it is added to the file structure, just the normal checks that it is a structurally sound file with one of the many extensions that the KOReader reader engines can handle. (Some extensions that could be read, are not normally implemented, but can be added.)

The nickel book processing seems to only be validating that the OPF and NCX are valid. It might also check the file structure, but it doesn't check the validity of the HTML code. For the NCX, it doesn't check the files and locations it points to exist, just the structure is valid. I haven't had a file that broke the processing for a very long time.

There is no special treatment that differentiates between files for ebooks bought from Kobo and those acquired elsewhere.

There isn't for nickel either when you disconnect the device. Purchased books are downloaded handled as they are downloaded to the device, or by the desktop app when it syncs the books. (I'm only commenting on this because you seem to be making a point, but I don't know what it is.)

[mkkdkp]

Can anyone send me a link to the N613 firmware to take a image or image?
Please, please, please....

[DNSB]

Originally Posted by mkkdkp

Can anyone send me a link to the N613 firmware to take a image or image?
Please, please, please....

Probably too late to help you here but if you look in the Kobo Developer's Corner, you'll see Index of Firmware Request Threads which should lead you to the right spot to make your request. You should find the right thread to ask for firmware for a Kobo Glo N613 there.