Quote:
Originally Posted by PeterT
Only problem with that is that Kobo Desktop DOES safely update the database on the Kobo.
|
I don't know how the Kobo Desktop application does this. If you automate the steps I described above, then any application could do it. I want to use calibre (and improve it by solving problems I encounter).
Quote:
Originally Posted by PeterT
Also, I and many others have used this driver for aeons with no such similar problem.
|
That does not change the fact that my (relatively new) KT does have these problems, that it does keep the DB opened and that many manipulations of said database while connected via USB do corrupt the DB beyond usability. Maybe it can be attributed to the fact that it is new and uses an up-to-date firmware (as opposed to being in use for aeons).
I don't want my efforts to be misunderstood as criticizing the KT driver or Davidfors work. Neither am I implying that the malfunction are the drivers fault or that every kobo user has this problem. Quite on the contrary in fact: If I thought the driver was not worth its salt I would not have spent this much time trying to get this to work. I want to make the driver work with my KT too... and possibly help others by doing so.
I assume that other users
may be having similar problems (though not as severe hopefully) that might be attributed to the same cause. However I fear that most other users will not go about searching for the cause of a problem in the same way as I and will only report "books gone missing" or "KT crashing". If they report it at all.
This is just my analysis of my problem with my KT and I want to notify other users that
if they are facing problems, this is how I tried to solve it. In particular I want Davidfor to know that this problem does exists. If I am an isolated case, I am actually glad about it.
In any case: I have found my workaround as previously posted, which closes this case for me
