View Single Post
Old 08-11-2017, 11:23 PM   #33
icallaci
Guru
icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.icallaci ought to be getting tired of karma fortunes by now.
 
Posts: 819
Karma: 6528026
Join Date: Sep 2012
Device: Kobo Elipsa
Quote:
Originally Posted by davidfor View Post
I was wrestling with my Aura ONE yesterday until I changed cables. There were no problems with the Aura H2O with the same cable. That's interesting as the Aura H2O has a lot more books on it. I haven't tried the Glo HD with the cable, but it has been having problems with another cable. The Glo HD hardware is closer to the Aura ONE, so it might have the same issues.

What is happening with the Aura ONE is that it connects and Windows mounts the drive OK. Calibre detects it and starts trying to fetch the books. Then calibre displays an error about connecting to the device. The error shows different positions in the code. At about the same time Windows shows a message about problems with the connected device. Testing this is a pain because when it happens, the USB port is put into some sort of error state. The only way I have found to fix this is restart the laptop.

When I do get the device reconnected, about 50% of the time, Windows will want to do a scan for errors. I don't remember errors being found.

All this suggests there is something different about the newer devices. Whether it is hardware or the drivers on the device, I don't know. I have to think about what more to test. I haven't tried deleting the driveinfo.calibre file yet. It will be a few days before I get to do much more.
This is exactly what is happening to me. I did try deleting drivinfo.calibre, but it didn't seem to make any difference; I still got the error. I've tried a couple of different cables, and sometimes it seems to help but other times not, so I'm not sure if the cable is making any difference or if it's just such a random occurrence that it would have worked without changing cables. Thanks for looking into it; I'm traveling for the next few days, so I can't do much testing until I get back home.
icallaci is offline   Reply With Quote