Quote:
Originally Posted by compurandom
There's been some of those too, but I actually tested with calibre 5 and repeatedly watched it not eject the device when it said it ejected it.
Then I switched to calibre 4.23 to see if it had the bug too (it didn't), and then switched back to calibre 5 and couldn't repeat it. So the only conclusion I can reach is that something in the shared config between calibre 4/5 was corrupt and calibre 4 fixed it. I wish I had copied the config so I could diff it, but oh well.
I suppose it could have been a config problem on the device that calibre 4 fixed.
|
For me, if I eject from calibre and the device doesn't actually eject, it means that something else is using the device. That usually means I opened the database to look at and forgot to close it, but it can be something else. In those cases, I need to close whatever it is and then use Windows to eject the device.
In your case, I doubt it was something in the configuration. Maybe a library wasn't replaced. But, it would have been interesting to see what it was that was blocking the eject. Probably an open file, but what was doing this is the question.