View Single Post
Old 07-31-2018, 06:37 PM   #7
DMcCunney
New York Editor
DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.DMcCunney ought to be getting tired of karma fortunes by now.
 
DMcCunney's Avatar
 
Posts: 6,384
Karma: 16540415
Join Date: Aug 2007
Device: PalmTX, Pocket eDGe, Alcatel Fierce 4, RCA Viking Pro 10, Nexus 7
Quote:
Originally Posted by kovidgoyal View Post
There are zero differences between portable and desktop versions when it comes to scanning filesystems, they both use the same underlying OS APIs. If you are noticing a difference, then it is because something on your system is interfering with the 64bit application but not the 32bit one. Try turning off your A/V which is the most liekly culprit for this kind of thing.
I don't use third-party A/V. Windows Defender is entirely adequate. (And if it was A/V getting in the way, I'd expect that to bite the portable version of Calibre too. For that matter, I'd expect A/V to throw up a screen telling me it blocked access.)

I assumed there were no differences between the portable and desktop versions beyond 32 bit vs 64 bit.

This worked yesterday. It fails today. There have been no changes on the system that would account for it.

Something is obviously blocking the 64bit version's access to the card. I'm trying to discover what it is.
______
Dennis
DMcCunney is offline   Reply With Quote