Quote:
Originally Posted by veereihen6
I think I figured out the problem, I think it was me not checking off the "Attempt to support new firmware" in the device interface plugins in Calibre. I was then able to get the KA1 to read the kepub's. But i don't know why it would not see files dropped into the root directory directly....
Thanks guys!
Edit: something else from GeoffR's comments, I had initially set up the KA1 using Kobo Desktop. On the second try, I skipped that and just did a wifi setup.
|
Sorry, but neither of these were the problem. If you are running an older calibre that doesn't support the firmware, you can still use it. The KoboTouch driver will display the books on the device properly, and allow you to send the books with no problems. What it won't do is the metadata management. That basically means it won't manage collections or the series information.
And doing the setup via WiFi and the Kobo deskop will produce the same thing. I've done both far to many times to think otherwise. And personally, I find the desktop methods safer, especially for the older devices. I have had problems doing the setup via WiFi, but not via the desktop. About the only problem I can think of is if you ejected the device at the wrong time, or something else tried to access it while doing the setup. Running calibre and the Kobo desktop at the same time when a Kobo device is connected is a bad idea. And I recommend that if you use one, disconnect and reconnect the device before using the other.
I don't know why it didn't work. The most likely reason is there was a problem with the books. If you saw the importing screen after ejecting the device and the progress bar didn't move across the screen, it was probably a book failing to import. Unfortunately, there is no indication given of why the import failed. If the import wasn't started, it usually means the device didn't see anything it thought of as a new book. This could be because the book was in the wrong place, all the books had already been imported, the extension wasn't one the device recognised or there was a problem with the name. And, there is always the problem that people can't find the book after the import happened. But, that usually happens after a bit of use when there is a lot of books on the device.
Sorry, this doesn't really help. As things are working now, it mainly about clearing up a misconception.