Hi David,
Thank you very much for your reply. I really appreciate, and your message "turned on some lights".
Quote:
Originally Posted by davidfor
I don't think you mentioned before that you were using the KoboExtendedDriver. That explains the time taken to send the books. Each is being modified to be a kepub during the send. I've been doing some experimenting and calibre is sending 1175 books using the KoboTouch driver in a little over 10 minutes. The device imported these in about 15 minutes.
|
Guess what... I was not aware of, it's why I didn't mention...
Basically, I made some tests, I think one year ago, about the difference epub, Kepub, and the added-value a kepub may provide. Finally, I decided that's not really worth... At that time, I activated the extension and... I forgot to deactivate it. So... first action when I read your message: I deactivated the extension and checked all the other ones
Maybe this was also the issue I faced when I tried to upgrade 3.18 to a newer version... Let's check.
Quote:
Originally Posted by davidfor
That error is from the extended driver trying to modify a book. Apparently it isn't a valid zipfile and cannot be unpacked. There is an option to ignore errors like this and send the book as an epub. But, that would cause a problem on the device.
|
Here, I have to say, I'm surprised. In fact, I read the code, but was not able to understand. In my library, I see one single format, which is epub. No Zip format at all... How can it be that Calibre tries to unpack a zip, which is not available in the format?
Quote:
Originally Posted by davidfor
20999 is a weird number to stop on. Using kepubs could be dropping the maximum books the device can see as they use more space in the database. But, I have been discussing this elsewhere and that person is using an account with 60K purchased books in it. I could see issue during the import if you tried to do them all in one go.
For sideloading, if there is a problem with a book, then it can block the rest from being imported. If you are seeing the import screen after ejecting without adding a book, then this is probably what is happening. Unfortunately, there isn't any indication of which book causes this. You have to use trial and error to find it.
|
So, I know that the error is between 20999 and 22000. Not bad for a start
Quote:
Originally Posted by davidfor
If there is an error happening, there could be stack log in the .kobo directory. This will have the name stack_0n.log where the n is a digit. This can give a clue as to the problem, but is usually more use
I'm curious about what is going on, so I'm doing some tests. Unfortunately, the biggest spare card I have is 16GB. I'll see how far I get with that, but I might get a bigger card on the weekend. I'm just adding the same 1145 books multiple times. I know they load OK, so they should work for this.
|
On my side, I'll start a new test with the Glo HD (same config), which is already ready to start... just to see if I face the same error... or a similar one... or no issue at all :-)
I'll need some time to get there, but anyhow, will keep you posted.
Thanks again for your support and I wish you a very nice day.