I'm pretty sure this isn't hardware related though I can't say why it only seems to happen on XP machines. The Windows-Glo connection remains rock solid unless you connect via the Calibre driver. This would not be the case if hardware was the source of the problem. At times when I have been unable to remain connected via the driver, if I disable it and connect Calibre to my Glo as a folder device there are no problems.
It appears to me that the problem is being triggered when Calibre's driver tries to manipulate the Kobo SQL database. On a couple of occasions when I haven't been able to retain a connection via Calibre I have been able to sort things out by using a SQL database browser to vacuum the Kobo's database. Once the database has been compressed Calibre will connect via the driver until I do something else to upset it (typically deleting or updating a book via Calibre).
I have mentioned in other threads that the problem seems to have similarities with that noted in
http://www.linux-usb.org/gadget/file_storage.html :
Quote:
|
AN IMPORTANT WARNING! While MSG (Mass Storage Gadget) is running and the gadget is connected to a USB host, that USB host will use the backing storage as a private disk drive. It will not expect to see any changes in the backing storage other than the ones it makes. Extraneous changes are liable to corrupt the filesystem and may even crash the host. Only one system (normally, the USB host) may write to the backing storage, and if one system is writing that data, no other should be reading it. The only safe way to share the backing storage between the host and the gadget's operating system at the same time is to make it read-only on both sides.
|
(my emphasis)
It occurs to me that if Calibre is making changes to the Kobo's SQL database and some process is still running on the Glo which is also doing housekeeping the above conditions might apply. This is just a theory - I don't have the tools or skills to investigate further.
BobC