Quote:
Originally Posted by Tatezi
The attached screen shots are from Program Files, not Program Files (x86) which also has a Calibre folder. Let me know if I used the wrong one.
|
Quote:
Originally Posted by Tatezi
BetterRed...I posted the screen shots you requested, but forgot to put your name on the post.
|
@
Tatezi 
- thanks a lot, interesting. What that tells us is that the ebook-edit program does not appear to be the 64bit version, even though its in the Program Files folder. If it was the 64bit version it should say so, at bottom left:-
But, the '
[64 bit]' you see in the version number above does not come from the .exe file itself, so we can't be sure :-
I don't know for certain how calibre 'knows/thinks' that it's the 32bit or 64 bit install. One of my neurons suggests it may come from the python run-time environment.
Would you mind running
calibre-debug - g at the command line against the two versions of calibre in
Program Files (X86) and
Program Files. Here's what I get, I've highlighted the salient differences - the fact that the 32bit is 2.25 and the 64 bit is 2.66 is immaterial - I think
32bit debug
C:\Program Files (x86)\Calibre2>calibre-debug -g
calibre 2.25 isfrozen: True is64bit: False
Windows-7-6.1.7601-SP1 Windows ('32bit', 'WindowsPE')
32bit process running on 64bit windows
('Windows', '7', '6.1.7601')
Python 2.7.9
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
64 bit debug
C:\Program Files\Calibre2>calibre-debug -g
calibre 2.26 [64bit] isfrozen: True is64bit: True
Windows-7-6.1.7601-SP1 Windows ('64bit', 'WindowsPE')
('Windows', '7', '6.1.7601')
Python 2.7.9
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
BR