Quote:
Originally Posted by BetterRed
Main difference is on large conversions which need lots of memory - they will fail. Day to day stuff doesn't make any noticeable difference. There are plenty of users who use the 32bit version by way of using the Portable version and they never run into the limits, I think books with very large numbers of internal links are problematic.
It doubt it is of any consolation, but you're not the first person to run into this situation, when the 64 bit has 'weird' errors and the 32bit works.
Just recently, Kovid told us how to create a 64bit Portable ==>> Calibre portable 64bit. It's very simple, and you already have the wherewithal to do it -- it won't solve the problem, but it would confirm that it's a bittedness issue.
Have you tried Safe Mode, and running with minimal number of processes, I'm thinking of startup tasks, windows shell extensions, 3rd party codecs, unusual devices etc.
BR |
It's a Surface Pro 3 with an external drive attached, there isn't really anything special going on.
"Resident" apps are AVG, Steam, GOG Galaxy, OneDrive, OneNote, nothing really special. I typically have Trillian, Firefox, Outlook actually running.
The only thing I can reasonably think of causing a problem is that I'm on the tech preview for Windows; it's possible that the current release I'm on has a bug. If that's the case I'd like to report it but I'd probably need to be able to collect more data for investigation.
I was asking about performance since 32-bit applications handle addressing differently, plus there are limitations on how much memory they can access, and is definitely a factor in 32-bit vs 64-bit operating systems.