Quote:
Originally Posted by davidfor
No you didn't. The Kobo Utilities plugin has absolutely nothing to do with sending books to the Kobo devices. You do not need it for that.
Yes, it is very wrong. Calibre will happily send a book to Kobo devices when the firmware version doesn't match. But, it cannot do other stuff, such as update metadata on the device.
And guess what is the first problem you should have started with? If calibre, or more specifically, the KoboTouch driver could not find the database, then you are in big trouble. And creating the directory to manually to fix it is absurd. It is more likely that the directory was hidden as it is normally marked as a system directory and the OSes tend not to show it. But, that wouldn't have helped as calibre will not create the database. It will only use an existing one.
Honestly, with the problems you are having, I am surprised the device was working at all. At the least I would have expected that it wasn't remembering your books when you added them or read them. And I am a bit surprised that it wasn't rebooting when you disconnected the device and taking you through the setup each time.
Every version of the instructions I have seen is pretty clear about what the files names are. The lack of any other file names should have told you what want going on.
And as you said, the rest is because of this mistake.
|
i assumed it was the kobo utility sending the books, but it is irrelevant, it worked once and then stopped working. after a recent update it is now working again.
regarding the database, my experience says you are wrong or don't understand why it resolved the issue. the log showed me the folder path and it was not hidden or a system file. it didn't exist. once i created the folder in explorer manually and reconnected the device the functions starting working with no errors and files appeared in that folder. and why is it the first problem i should have started with? if, as you say, sending the book doesn't require kobo utilities, then i was using a completely normal and supported method of everything i was doing. load properly named fonts, drag books onto device directly. and it was working, so i believe these were separate issues.
forgive me, but i read everything about the font file names, and verified they all were case sensitive and had the correct formatting. it never dawned on me, nor seems clear even now, that any of those instructoon (except the wiki link that ultimately helped) indicated anything about extra variants being bad. some fonts have more than others, so i assumed the naming simply had to be consistent.
anyhow, i honestly do appreciate the help, so thank you. things are working now.