|
@PeterT
No problem with the Kobo desktop - it seems to work fine.
@davidfor
I've tried it on another USB port without any improvement, without Calibre loaded I can load the database over USB into a SQLite browser and examine the tables (I'm not going to modify them as that might seriously screw things up).
Filesystem scan didn't throw up any errors.
It seems clear that "something happens" after the initial communication between the Touch driver and the Kobo which then makes the drives allocated to the device invisible to the O.S. - Device Manager can see the hardware but not any drives associated with it. The same goes for Computer Management's Logical Disk Manager which, prior to the Calibre connection shows both drives as Healthy FAT32.
Everything worked fine before the 2.50 upgrade.
I noticed that with 2.50 the ProductID for the Kobo was upped from 4163 to 4173 and instead of being simply having a device name of "eReader" it became "eReader-2.5.0" though USBDeview shows them as otherwise the same.
I see Joel's Extended Driver has been updated so I enabled that to check if there is any improvement but no, nothing has changed there (I don't know if that would help though until the basic driver has been updated).
It looks like I need to revert to 2.4 to see if the problem then goes away or if the update was just a co-incidence. - I think the fact that I can happily communicate with the Kobo for as long as I want until the Touch Driver comes into play does rule out any hardware issues (ports, cables etc).
Thanks both for the ideas though.
BobC
|