Thread: KINDLE FORCED UPGRADE
View Single Post
Old 10-28-2020, 04:28 PM   #46
John F
Grand Sorcerer
John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.John F ought to be getting tired of karma fortunes by now.
 
Posts: 8,099
Karma: 71356237
Join Date: Feb 2009
Device: Kobo Clara 2E
Quote:
Originally Posted by haertig View Post
Running KindleForPC on Linux under WINE (wrapped by PlayOnLinux) I did the following:

Code:
$ cd ~/.PlayOnLinux/wineprefix/kindle_1.17/drive_c/Program Files/Amazon/Kindle

$ chmod 000 renderer-test.exe  (was previously mode 755)

$ cd ..

$ chmod 555 Kindle  (was previously mode 755)
Note: The "kindle_1.17" you see in the pathname right after "wineprefix" above is what I chose to call my PlayOnLinux installation. That part of your path may be different, depending on what you named your installation.

I then started KindleForPC a couple of times and verified that it always remained at the currently installed version 1.17. It did. And I never got any messages about "update available" either.

Next, I opened KindleForPC again, picked a random book from the display of titles (that was not currently downloaded), right-clicked on it and chose "download". Then I verified that the download successfully showed up in my "My Kindle Content" directory. It did. This is the only functionality I need from KindleForPC.

I actually don't use KindleForPC anymore. A few years ago I switched over to using the "Download for USB Transfer" method instead. But it was good for me to review usage of KindleForPC, and keep my installation "up to date" using the strategies described here to keep it from updating itself.

I run nightly backups on all of my family's computers, and keep each individual daily backup for 365 days. So if KindleForPC does manage to update on me, I have one year to notice, and restore from backup. After that, I guess I'd have to reinstall and re-register the program from scratch. Amazon may, and probably will at some point, make re-registering a no-go. So my preferred method of getting things back on track after an unexpected update would be to restore from backup. But Amazon could thwart that as well, if they tried hard enough.
I thought for version 1.17.x you didn't have a render check exe?
John F is offline   Reply With Quote