[BobC]

Originally Posted by davidfor

Can you run "PRAGMA integrity_check" against the database? This will check if there are any problems with the database.

I ran this with no errors reported

Yes, but what is the problem.

I can only characterise it as loss of connection between the Glo and my XP machine (when Calibre connects via the Touch driver)

I sure hope the ProductID didn't change. x4173 is the id for the Glo. If you had x4163 before, then that is very strange.

I think I explained this in my reply to Joel.

Since 2.3.1 I think, the device name has included the firmware version.

I suspect the issue here is an old registry entry.

That is correct. Most of Joel's driver is changing the file. The base driver and calibre do the file copies any changes to the database. But, the update to the base driver isn't going to change anything. The only changes are an update in the firmware version numbers and management of cover images on the SD card. There haven't been any changes that could affect this for at least a month.

Thanks for the info it might help me eliminate some issues.

You could take a copy of the database. Then log out on the device and get a new one when it restarts. Then see if the communications with calibre still breaks. If it doesn't, then it was a database problem. If the problem is still there, you can restore the copy of the database and try downgrading the firmware.

I had decided to do a factory reset on the Kobo as I was coming to the conclusion that the problem was at that end. Before I did that though I was able to duplicate the problem without using Calibre. I used SQLite to access the database on the Kobo and then compacted the database. When it came to save the database the problem occurred - i.e the drive on the Kobo became invisible to my O.S. This now confirms my suspicion that the problem is at the Kobo end rather than the Windows/Calibre end.

I'll do a factory reset then update directly to 2.50 and see what happens.

Again, thanks for the help.

BobC