The 2.8.0 factory installation has an empty "user" table. I understand about updating the "user" table of the Kobo/KoboReader.sqlite and should be able to fumble my way thru that, but I don't have an example to use for 3.3.0. Yay - this is progress.ģ) I'm now at the stage of bypassing the registration, since that step is the kiss of death for Windows recognizing the device. When I plug it back in, Windows (and Calibre) can see the device properly. I unplugged the device, and it took the update. ![]() I've copied that installation to a backup.Ģ) I've downloaded the 3.3.0 firmware from MobileRead (thank you) and copied it onto the device directly. OK, I've been educating myself about sideloads of the firmware and can phrase some more intelligent questions (thanks for your patience).ġ) With the factory installed 2.8.0 (Aura) firmware, Windows can see the device properly. This device has been blacklisted by the user (87, 'GetDiskFreeSpaceEx', 'The parameter is incorrect.') Successfully initialized third party plugins: DeDRM & K4PC, K4Mac, Kindle Mobi and Topaz DeDRM & Inept Epub DeDRM & Inept PDF DeDRM & Count Pages & eReader PDB 2 PML & Quality Check & Ignoble Epub DeDRM & Find Duplicates & Extract ISBN & Barnes & Noble & Kobo Utilities & User Category & Goodreads Windows-7-SP1 Windows ('64bit', 'WindowsPE') I ran the Calibre Device Detection Debug and got this:Ĭalibre 2.0 isfrozen: True is64bit: True The two device plugins for Kobo are enabled. ![]() (Windows also complains - wants to format it as drive D: - but the OS list of connected devices for ejection includes "eReader 3.3.0", so I assume the drivers are alright (but the Kobo PC utility doesn't see it either, so maybe not). ![]() That gave me a 64-bit 2.0 instance that so-identified (yay!) and my database seemed fine (double yay!). Before I saw your suggestion, I rebooted.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |