Kindle For Pc Windows 7 Free Download
Anna Pybus
I really want to get the Kindle PC program running on my computer so I can download, read, and manage my e-books. I realize that Calibre can be used to manage e-books and I do have that downloaded. However, Amazon won't let me download ebooks unless my PC is registered in their Kindle program and I'd like to just keep things streamlined.
I've viewed many tutorials and advice for setting it up. I have Wine, I have Kindle for PC, I set it to Win98, all of that. However, when I try to open KindlePC from the Wine menu or from the desktop icon, nothing happens. No error messages, nothing. I don't know what might be wrong. How can I make it work?
If the intent is to manage the book on your Kindle, what about using a native application like Calibre rather than the Kindle Windows software? Calibre is in the Ubuntu repositories so you can install it via the software centre or using the command line:
PlayOnLinux will use and if needed will install the appropriate Wine version for the program. Let PlayOnLinux download automatically and install the Kindle for PC software instead of downloading and selecting it yourself.
I just want to share a solution for those who are trying to install Kindle on Ubuntu 14.04 and Linux Mint. In my case, I noticed that the ttf-mscorefonts-installer package was not properly installed by the Software Center App because it didn't show the agreement that I had to acknowledge. I think that the fonts were not installed because of that. So I manually installed the fonts from the terminal using sudo apt-get install ttf-mscorefonts-installer, acknowledged the agreement shown in a colored text format display, and after that, my Kindle does not crash anymore when I open my e-books. My Kindle now works on Wine versions 1.6 and 1.7 under PlayOnLinux.
For Linux Mint users, they should install the ubuntu-restricted-extras package before installing the ttf-mscorefonts-installer for some reason. I think without the ubuntu-restricted-extras, not all fonts will be available even after installing the ttf-mscorefonts-installer package
I recently was having the same problem with Ubuntu 12.04, trying Kindle for PC. Following some clues I saw on forums, the best solution was to delete all files under .wine/drive_c/windows/winsxs/manifests. It works but may cause problems with other programs.
you will notice that only the file msvcr90.dll exists. So search for the other two dll files on Google and put them in this directory. For me, Kindle for PC is working just fine now after I've put these two dll files in this directory.
I was wondering if there was a way to send a note from Evernote to Kindle, via Amazon's Personal Document delivery service, where it would take a note from Evernote (maybe convert it to MOBI?) and send it as a document to my Kindle 3 (via your x...@free.kindle.com address).
I was hoping it would be similar to Instapaper's setup, where you add Instapaper's given email address (x...@instapaper.com) to the approved email's list under your Amazon account. I tried adding Evernote's unique email address (under Tools>Account Info) under the approved emails, however when trying to send a note via email (through Evernote's Share button), the document was not delivered to my Kindle under Wi-Fi.
I am using This application creates a folder in your dropbox sync which upload to gmail account every file that you save there. If you create a automatic filter in gmail to send to kindle.free, you can send automatically files to kindle. Thus, you need only export your note (s) as html file in that folder and ready!!!.
I've downloaded and installed JDK 32 and 64 bit.I've installed the Android SDK as needed.I've modified android_winusb.inf inside of the google-usb-driver to include the Kindle Fire device IDs.I tried downloading the kindle fire windows 7 driver from amazon (as described in the answer here), and using that.
The only thing I'm unsure about is the modification of adb_usb.ini. Unfortunately, my .android folder doesn't exist in my %USERPROFILE%, but instead exists in another location on my computer. That folder doesn't have adb_usb.ini either. So I copied the contents of .android to my %USERPROFILE%, and created adb_usb.ini in each, and added 0x1949 to that empty file.
I had the same exact problem only after adding 0x1949 I could see the device listed. Either amazon is changing the id's or people are giving wrong id's in random forums. The first one is definitely not required.
That sounds like you've done all the right things. For me the adb_usb.ini file did the trick and it's in c:/users/dirk/.android/adb_usb.ini. Oddly, I also added the product id of 0x006 on another line, thought I don't think that matters (the 0x1949 is the vendor id).
So I had the exact same problem as you and I also had a problem with it looking for java.exe in my c drive instead of my d. I fixed this issue the same way I fixed that. Use the "mklink" command line tool to create a symbolic link in the C drive to your .android folder on your other drive. My exact command was:
In general, running "android update adb" from the /Tools folder should be enough to update the correct adb_usb.ini file. The location of this file is relevant as adb will only look for one of them. I had a CRC error in sdkuilib.jar, and it would not copy. This caused "android update adb" to fail, so my adb_usb.ini file did not get updated.
Also, when I went to update by hand, I was logged on as joe user, but I elevated to admin user to perform the update. I modified the joe user copy of adb_usb.ini (c:\users\JoeUser.android\adb_usb.ini), but the adb program looked instead at the admin copy of adb_usb.ini (c:\users\Admin.android\adb_usb.ini). So, adb did not see the 0x1949 that I added by hand.
Once I replaced my copy of sdkuilib.jar (by redownloading, installing in a separated folder, and copying over the bad file), I was able to run "android update adb" and 0x01949 showed up in my admin adb_usb.ini. [To find this, I changed echo off to echo on at the top of both the android.bat and find_java.bat files.]
After that, I did an adb kill-server and adb usb. But I still got the "error: device not found" message. Only then did I notice that my Kindle Fire had timed out. I turned it back on, unlocked it, and at that point, the kill-server "adb usb" sequence produced "restarting in USB mode".
If you don't currently have a C:\Users\[Username]\.android folder, add one manually. Copy adb_usb.ini into this folder. Windows may give you some trouble if you try to create this folder in Windows Explorer (beginning the folder with a period, probably). I had to open cmd and type move android .android to accomplish this.
If you are using Windows and you have the Android SDK installed (if ANDROID_SDK_HOME environment variable is set) then adb will use %ANDROID_SDK_HOME%\.android\adb_usb.ini instead of %USERPROFILE%\.android\adb_usb.ini
d3342ee215