View Single Post
Old 10-14-2015, 04:41 PM   #3
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,794
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
FWIW - Last weekend we had a similar problem with a couple of tethered camera's that Windows 10 could see and the Breeze camera software couldn't. We solved it by unplugging the camera's and uninstalling the USB controller in device manager. Did a reboot and Windows detected the controller and did its new hardware business, when we plugged the camera's back in, they were visible in Windows and Breeze.

No idea if that will work for e-readers and calibre or if.

If you try this, I suggest you create a System Restore Point before you mess with Device Manager in case something goes wrong, and then Sod's Law will almost guarantee that nothing will go wrong

BR

Last edited by BetterRed; 10-14-2015 at 04:53 PM.
BetterRed is offline   Reply With Quote