64 bit calibre on Windows

[Alexmark]

Originally Posted by kovidgoyal

Hi all,

After several weeks of fun getting all of calibre's dependencies to build on Windows 64bit, I finally have a working 64 bit build of calibre in Windows.

The installer is designed to install calibre 64bit alongside an existing calibre 32bit install. So you can switch between them until you figure out which one you want to use. The shortcut for launching calibre 64bit is named "calibre 64bit - E-book management" and when running it the status line at the bottom of the main calibre window will say [64bit].

The advantages of the 64 bit build are it can use all the RAM on machines with more than 3GB of RAM, which allows conversion of certain large and messy documents. There also may be small performance improvements.

The downside is that since this a new build there may well be some bugs that lead to crashes.

So if you are running a 64 bit version of Windows, try out the new calibre 64bit build and let me know how it goes.

http://status.calibre-ebook.com/dist/win64

Note that calibre has had 64 bit builds for linux and OS X for years.

Thanks for all help you are giving for all of us, and hope that you as a guru can help me as well.
I have an Android 4.0 tablet (Sophix) with a Kindle App installed on it. I want to transfer my downloaded ebooks through USB cable and got a problem from the very beginning. I can't make Calibre running on my Win7 64 bit Toshiba laptop.
I tried older versions (7.20, 7.38) and 9.13 64 bit as well. The installation is running smooth, but I can't launch Calibre. I tried all FAQs and HELPs. I uninstalled it 10 times, restarted, deleted the folder Calibre, Calibre2 in Program Files, in Programm Files x86. I deleted folder "caliber" in C:\User\AppData...I installed it in C:\library folder (if I got you right)....I've never found metadata.db file, that's why I didn't delete it....
And finally, after I spent hours, I ran debug, and asking for your assistance.
Help please,

Here is my debug log:

Python function terminated unexpectedly
(123, 'CreateFile', 'The filename, directory name, or volume label syntax is i
ncorrect.') (Error Code: 1)
Traceback (most recent call last):
File "site.py", line 132, in main
File "site.py", line 108, in run_entry_point
File "site.py", line 50, in load_module
File "site-packages\calibre\__init__.py", line 21, in <module>
File "site.py", line 50, in load_module
File "site-packages\calibre\startup.py", line 65, in <module>
File "site-packages\calibre\utils\localization.py", line 94, in set_translator
s
File "site-packages\calibre\utils\localization.py", line 55, in get_lang
File "site.py", line 50, in load_module
File "site-packages\calibre\utils\config_base.py", line 440, in <module>
File "site-packages\calibre\utils\config_base.py", line 352, in __setitem__
File "site-packages\calibre\utils\config_base.py", line 366, in set
File "site-packages\calibre\utils\config_base.py", line 298, in set
File "site-packages\calibre\utils\lock.py", line 113, in __enter__
File "site-packages\calibre\utils\lock.py", line 32, in __init__
pywintypes.error: (123, 'CreateFile', 'The filename, directory name, or volume l
abel syntax is incorrect.')
C:\library\pylib.zip\calibre\ptempfile.py:27: RuntimeWarning: Parent module 'cal
ibre' not found while handling absolute import

The system cannot write to the specified device.

*******************
I fixed it. I had created an account in Windows in Cyrilic letters long time ago. I renamed it later, but the User name stays the same. That's why I had syntax error all the time. As a solution, I had created a new admin account with English letters and everything is running like a charm.

Thanks again.

[MontyJ]

Originally Posted by kovidgoyal

Hmm nothing comes to mind that could cause crashes with a combination of Win8 and SSDs. It's likely something else you have in common. Unfortunately the number of variables is so large that it's rather hard to guess what that might be.

I finally concluded I had gone as far as I could to 'isolate' the problem. I did a complete Windows 8 "Reset", using the "Thorough" option, which as near as I can tell wipes and re installs W8 totally.

With this squeaky-clean install on the SSD, I only loaded Calibre x64 and fired it up, intending to load one program at a time until it failed; if it would fail! I have now loaded all my critical programs and utilities and Calibre continues to perform w/o issue! And yes, I have the same plug-ins and settings as used in the previous installation that was failing.

It is a bit disconcerting to "not know why", but that is just my tech mindset and background! But, it is working w/o issue now, so onward and forward
If perchance I now load some obscure program or driver that causes it to fail, hopefully I am now in a position to narrow it down...

And kudos on a great job done on Calibre!!

Monty

[kovidgoyal]

@MontyJ: Glad you got it working. The wipe and re-install is a traditional method of fixing windows problems

It is unfortunate that there are so many programs in windows that interfere with other programs. Not a week goes by without someone reporting some kind of random crash/freeze in calibre on windows that is caused by some interfering antivirus/malfunctioning driver/other random utility.

[taustin]

For what it's worth, I've been running Calibre 64 bit on a out-of-the-box Dell Optiplex with 8 GB or RAM, apparently almost from when it was first available (the computer was fairly new), and have had zero problems of any kind, even through updates.

[country0129]

Originally Posted by toomuchreading

Just a quick note for those thinking about installing the 64 bit. I just installed it, an the installer looked at everything I had already set up. I did not have to use any wizard to point to my existing library or re-load my plug-ins. Kovid designed it so that if you had a preexisting installation, all the libraries and plug-ins from your 32 bit would be immediately available in the 64 bit. Since Kovid originally said that the two versions could be run and installed at the same time, I had made the assumption that the 64 bit would require configuration upon installation even if you had the 32 bit version installed. It didn't require any special configuration and it's working great on my system so far.
I must say a huge thank you for making the installation seamless and stress free.

Ditto

[lar0chelle]

Originally I had the 32-bit version installed but when the 64-bit version was released I installed it. Now when I open the 64-bit version (0.9.17) I get this message:
Could not change the on disk location of this book. Is it open in another program?
It is not opened anywhere else. I'm sorry if this is already discussed somewhere, I'm new to forums and am not sure how to get around. If someone could just point me in the direction to the answer to my problem I would really appreciate it. Thanks.

[theducks]

Originally Posted by lar0chelle

Originally I had the 32-bit version installed but when the 64-bit version was released I installed it. Now when I open the 64-bit version (0.9.17) I get this message:
Could not change the on disk location of this book. Is it open in another program?
It is not opened anywhere else. I'm sorry if this is already discussed somewhere, I'm new to forums and am not sure how to get around. If someone could just point me in the direction to the answer to my problem I would really appreciate it. Thanks.

Do you have the (32 bit) content server running? Did you Reboot?

[lar0chelle]

Originally Posted by theducks

Do you have the (32 bit) content server running? Did you Reboot?

Ok I rebooted and still had the same problem so I got to thinking about it - why would the program think I had the file open somewhere else?! and then it dawned on me. I backed up my library onto my external hard drive, which I don't usually keep plugged in but I had been using it earlier so there it was. I believe the program was seeing both copies of the library. Once I ejected the external hard drive and gave it another try - viola! tks for trying to help me.