[paulvro]

Thank you Davidfor,

As far as I can guess, what might have happened is that I somehow interrupted the procedure that renewed the software without knowing it. There never was any question to me if I wanted to update the software so I couldn't possibly be aware that I interrupted anything. The moment I saw that the charge-up was completed I unplugged the power supply.

I should perhaps mention something: in my study there is hardly any WiFi signal while in tje living room where I recharged the reader the WiFi signal is very strong. So perhaps that somehow triggered the Reader to update it's software, perhaps my shoving away the question if the Reader should connect to the (not attached) computer did something to activate that update. I have no idea.

Your suggestion to fiddle around a lot with the Reader sounds good, it's the kind of thing I tend to do with any new electronic toy. However, in this case it's not so easy because it's my wife's Reader and she is an avid reader so there's not so much space for me to get my hands on it. And she most certainly would never be convinced to do the fiddling, she is hardly able to use her Windows laptop without asking for my help on an almost daily basis.

You made a misinterpretation of my remark about the power supply. Of course, if I had known that some of them cause that reaction asking if I wanted to connect to the computer while in fact there is none it wouldn't have been such an issue. But the fact that i didn't and that before that reaction did NOT take place the first thing that comes to mind is a fear that I might have used the wrong power supply. I gladly would have paid a few euro's extra to avoid such stressful events. Besides, we happened to get our i-phones only a week before I bought the reader, before that I had no power supplies other than the standard 12V power supplies and in fact the manual of the Reader wasn't terribly clear about what voltage was needed. Considering that even a very simple external harddisk is always sold including a power unit I was amazed that Kobo hadn't bothered. In fact at first I even thought that perhaps there was a packing error.

You asked about the Reader being turned on and off during the last 10 days. I assumed that it was but only based upon the fact that the screen states "sleeping". I haven't found any way to really turn it off, even when "sleeping" the book cover remains visible so I suspect that there must be a way to completely turn it off (?).

I a few minutes I'll be able to rip the reader out of my wife's hands (she'll have finished the book she's reading) and then I'll reconnect it to my PC and check if Calibre now still shows the same error message. If not, the conclusion seems obvious that the error was temporary based on my unknowing interruption of the software update that apparently was in progress. I'll post a follow-up as soon as possible.



PS: As it appears I was too optimistic! Even though the Reader seems to work well again, Calibre insists upon the same error message:

calibre, version 2.85.1
FOUT: Fout: Fout bij communicatie met apparaat

CorruptError: database disk image is malformed

Traceback (most recent call last):
File "site-packages\calibre\gui2\device.py", line 88, in run
File "site-packages\calibre\gui2\device.py", line 511, in _books
File "site-packages\calibre\devices\kobo\driver.py", line 1835, in books
File "c:\cygwin64\home\kovid\sw\build\apsw-3.8.2-r1\src\cursor.c", line 231, in resetcursor
CorruptError: CorruptError: database disk image is malformed


So I'll follow the advice and try to sign out of the Kobo account.