Dealing with Kindle for PC/Mac 1.19 and KFX in calibre

[jhowell]

Originally Posted by olivier74

That didn't work for me. The book was imported as a KFX-ZIP file. What could have gone wrong? I am using the latest version of everything (all updated today).

First make sure that you are importing the .kfx or .azw file from its original location, not a copy. The import process needs to locate additional files in order to be successful.

Other than that, the most likely reason for that is a failure of the DRM removal process. We are not allowed to provide help with that here on MobileRead. You should ask for help at either Apprentice Alf's Blog or Apprentice Harper's GitHub.

[Inukami]

When I recently updated my mac computer to MacOS Mojave 10.14, I got the below message when I first opened Kindle for Mac 1.17 again.

"App" is not optimized for your Mac and needs to be updated.

This app will not work with future version of MacOS and needs to be updated to improve compatibility. Contact the developer for more information.

It also referred me to link 32-bit app compatibility with macOS High Sierra 10.13.4 and later.

I'm assuming that Kindle for Mac 1.17 is a 32-bit app, which means that it will not update with future versions, as Mac is transitioning to 64-bit apps.

At the Apple Worldwide Developers Conference in 2018, Apple informed developers that macOS Mojave is the last version of macOS to run 32-bit apps.

When will the 64-bit transition be complete?

The 64-bit transition for macOS and macOS apps is still underway, so final transition dates have not yet been established. But now is a good time to check with the software developer to see if 64-bit versions of your favorite titles are available.

Anyone know when you wont be able to use Kindle for Mac 1.17 on the most recent MacOS software? Is it not likely to be until the next major release?

Inukami

[DNSB]

Originally Posted by Inukami

I'm assuming that Kindle for Mac 1.17 is a 32-bit app, which means that it will not update with future versions, as Mac is transitioning to 64-bit apps.

Anyone know when you wont be able to use Kindle for Mac 1.17 on the most recent MacOS software? Is it not likely to be until the next major release.

The quote you posted says it all. Mojave is the last version to run 32-bit apps. The current plan is that when Mac OS 10.15 (Mac OS Death Valley?) is released, it will not support 32-bit apps. Until then, you are okay.

[jhowell]

Originally Posted by DNSB

The quote you posted says it all. Mojave is the last version to run 32-bit apps. The current plan is that when Mac OS 10.15 (Mac OS Death Valley?) is released, it will not support 32-bit apps. Until then, you are okay.

If Apple continues their current pace the next major version will not be out until fall of 2019. No need to worry just yet.

As far as I know even the most recent version of Kindle for Mac is 32-bit. Although the most recent version is 1.24, the Mac App Store still has 1.23, probably because Apple will no longer accept updates to 32-bit apps in the store.

I suspect that the next version (1.25?) will be a 64-bit app. Hopefully the workaround to disable KFX will still be possible with that release and it will be a painless upgrade.

[wiggy97]

I was unable to add an ebook to Calibre despite upgrading to version 3.33.1, using your KFX tool and using the latest Alf tools 6.6.1.
I am using win 7 pro OS
I am getting this error message in Calibre, and cannot get any response from Alf's Blog or GitHub.
E-books downloaded directly from amazon website to PC and then aded (or not) to Calibre.
Any ideas please?

----------------------------------------------------------------------
Failed to read metadata from the file:
C:\Users\xxxxx\Downloads\Impaired Sensitivity to Thyroid Hormone (Thyroid Hormone Resistance)_ A Cause of Heart Disease, Cancer, Autoimmune Conditions, Women’s Health Issues, Strokes, ... Fibromyalgia, Depression and Other Issues(1).azw3
With error:
Traceback (most recent call last):
File "site-packages\calibre\utils\ipc\pool.py", line 371, in worker_main
File "site-packages\calibre\ebooks\metadata\worker.py", line 88, in read_metadata
File "site-packages\calibre\ebooks\metadata\worker.py", line 78, in run_import_plugins
File "shutil.py", line 83, in copyfile
IOError: [Errno 2] No such file or directory: u'C:\\Users\\DOUGLA~1\\AppData\\Local\\Temp\\calib re_9xh_b0\\cdllis_add_books\\0\\Impaired Sensitivity to Thyroid Hormone (Thyroid Hormone Resistance)_ A Cause of Heart Disease, Cancer, Autoimmune Conditions, Women\u2019s Health Issues, Strokes, ... Fibromyalgia, Depression and Other Issues(1).azw3'

[pdurrant]

As it's an AZW3 file, not a KFX file, it's nothing to do with importing KFX files.

Detailed help with removing DRM isn't available here. You'll have to want for an answer elsewhere.

[jhowell]

Originally Posted by wiggy97

IOError: [Errno 2] No such file or directory: u'C:\\Users\\DOUGLA~1\\AppData\\Local\\Temp\\calib re_9xh_b0\\cdllis_add_books\\0\\Impaired Sensitivity to Thyroid Hormone (Thyroid Hormone Resistance)_ A Cause of Heart Disease, Cancer, Autoimmune Conditions, Women\u2019s Health Issues, Strokes, ... Fibromyalgia, Depression and Other Issues(1).azw3'

Originally Posted by pdurrant

Detailed help with removing DRM isn't available here. You'll have to want for an answer elsewhere.

The error being reported does not appear to be related to DRM removal. It seems that calibre is failing to read metadata from the book because the file pathname is too long for Windows to handle. Shortening the name of the file before import should be all that is needed.

If after correcting that a DRM-related error occurs then help should be requested elsewhere.

[lkmiller]

Haven't seen your post on the blog or at GitHub. The blog comment might have gotten stuck in moderation/spam -- the filters at Wordpress can be a little overzealous sometimes.

[jhowell]

I have updated the first post in this thread to show that methods 2 and 4 will no longer work starting with Kindle for PC/Mac version 1.25, which should be available soon.

Kindle for Mac 1.25 is supposed to be a 64-bit app.

[MickiTee]

Thanks for the update.

I'm still using v1.17 and will carry on doing so as long as possible, but as a precaution I've just downloaded v1.24.

[Purple Lady]

Originally Posted by MickiTee

Thanks for the update.

I'm still using v1.17 and will carry on doing so as long as possible, but as a precaution I've just downloaded v1.24.

I just did the same thing. I downloaded from the Amazon website, so I was surprised that it was still 1.24.

[odamizu]

Originally Posted by jhowell

I have updated the first post in this thread to show that methods 2 and 4 will no longer work starting with Kindle for PC/Mac version 1.25, which should be available soon.

Kindle for Mac 1.25 is supposed to be a 64-bit app.

Thank you, jhowell, for your careful attention to this!

[ilovejedd]

Originally Posted by jhowell

I have updated the first post in this thread to show that methods 2 and 4 will no longer work starting with Kindle for PC/Mac version 1.25, which should be available soon.

Kindle for Mac 1.25 is supposed to be a 64-bit app.

Thanks for the heads up.

Just to clarify, does this mean the method still works for now with the current FW versions (5.10.x)?

Originally Posted by jhowell

Method 4 - Convert from KFX to other formats

It now possible to convert books from KFX to other formats in calibre by installing the optional KFX Input plugin. Due to a change in DRM this will no longer work with Kindle for PC/Mac version 1.25 or newer and will likely not work with Kindle firmware after version 5.10.X.

[jhowell]

Originally Posted by ilovejedd

Just to clarify, does this mean the method still works for now with the current FW versions (5.10.x)?

Yes, method 4 still works with the recently released 5.10.x Kindle firmware.

[Terisa de morgan]

Originally Posted by MickiTee

Thanks for the update.

I'm still using v1.17 and will carry on doing so as long as possible, but as a precaution I've just downloaded v1.24.

I only find the link to the app. Where do you find the program for Windows?

Edit: Forget it, I've found it just after sending the message ;(