The old 1.48 installation that will not die

[Karen Myers]

I have 1.48 installed (OS is Windows 7 64-bit). I downloaded 2.0 in 64-bit, and installed it. It made a separate instance of Calibre (my bad), and both of them opened to a main screen which declared itself to be 1.48.

So, I uninstalled 1.48. When I ran the 64-bit 2.0, it still declared itself to be Calibre 1.48.

So I uninstalled the 64-bit 2.0. No installed Calibre instance. I reinstalled the 64-bit 2.0, and it still says it's Calibre 1.48.

How do I get the 64-bit 2.0 installation up (and so described), without murdering my database?

[JSWolf]

Go to program files and delete all the files in the Calibre directory. Then install 2.0 and see what you get.

[Karen Myers]

Before I saw your suggestion, I rebooted. That gave me a 64-bit 2.0 instance that so-identified (yay!) and my database seemed fine (double yay!).

Plugged in my new Kobo Aura. Not detected by Calibre. (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).

The two device plugins for Kobo are enabled.

I ran the Calibre Device Detection Debug and got this:

calibre 2.0 [64bit] isfrozen: True is64bit: True
Windows-7-6.1.7601-SP1 Windows ('64bit', 'WindowsPE')
('Windows', '7', '6.1.7601')
Python 2.7.8
Windows: ('7', '6.1.7601', 'SP1', 'Multiprocessor Free')
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
USB devices on system:
[u'usb\\root_hub20&vid8086&pid1e2d&rev0004',
u'usb\\root_hub20&vid8086&pid1e26&rev0004',
u'usb\\vid_03f0&pid_8404&rev_0100',
u'usb\\vid_03f0&pid_8404&rev_0100&mi_00',
u'usb\\vid_03f0&pid_8404&rev_0100&mi_01',
u'usb\\vid_0480&pid_a003&rev_010?',
u'usb\\vid_0480&pid_a006&rev_0001',
u'usb\\vid_04e8&pid_6860&rev_0400',
u'usb\\vid_051d&pid_0002&rev_0090',
u'usb\\vid_059f&pid_1053&rev_0006',
u'usb\\vid_0c45&pid_6449&rev_2808',
u'usb\\vid_0c45&pid_6449&rev_2808&mi_00',
u'usb\\vid_2109&pid_2812&rev_9080',
u'usb\\vid_2109&pid_2812&rev_9080',
u'usb\\vid_2109&pid_2812&rev_8570',
u'usb\\vid_2109&pid_2812&rev_9080',
u'usb\\vid_2109&pid_2812&rev_9080',
u'usb\\vid_2109&pid_2812&rev_9080',
u'usb\\vid_2109&pid_2812&rev_9080',
u'usb\\vid_2237&pid_4203&rev_0110',
u'usb\\vid_2687&pid_fb01&rev_0100',
u'usb\\vid_2687&pid_fb01&rev_0100&mi_00',
u'usb\\vid_2687&pid_fb01&rev_0100&mi_01',
u'usb\\vid_413c&pid_8197&rev_0112',
u'usb\\vid_8087&pid_0024&rev_0000',
u'usb\\vid_8087&pid_0024&rev_0000']
Unable to get free space for drive: D
(87, 'GetDiskFreeSpaceEx', 'The parameter is incorrect.')
Drives detected:

No disabled plugins
Looking for devices of type: MTP_DEVICE
List of WPD PNP ids:
[u'\\\\?\\usb#vid_04e8&pid_6860#0b349b4f#{6ac27878-a6fa-4155-ba85-f98f491d4f33}',
u'\\\\?\\wpdbusenumroot#umb#2&37c186b&0&storage#vo lume#_??_usbstor#disk&ven_kobo&prod_ereader-3.3.0&rev_0110#514b3a3055840&0##{6ac27878-a6fa-4155-ba85-f98f491d4f33}']
MTP device: \\?\usb#vid_04e8&pid_6860#0b349b4f#{6ac27878-a6fa-4155-ba85-f98f491d4f33}

--- then it looks for my cellphone which is the only entry in the list of Ignored Devices (Kobo eReader not listed) ---

{'device_version': u'G870AUCU1ANG3',
'friendly_name': u'SAMSUNG-SM-G870A',
'has_bulk_properties': True,
'has_storage': True,
'manufacturer_name': u'Samsung Electronics Co., Ltd.',
'model_name': u'SAMSUNG-SM-G870A',
'protocol': u'MTP: 1.00',
'serial_number': u'R38F608ZJTV',
'storage': [{'capacity': 12316528640L,
'capacity_objects': 0L,
'description': u'Phone',
'filesystem': u'Generic hierarchical',
'free_objects': 0L,
'free_space': 10205106176L,
'id': u's10001',
'name': u'Phone',
'rw': True,
'type': u'fixed_ram'},
{'capacity': 62695079936L,
'capacity_objects': 0L,
'description': u'Card',
'filesystem': u'Generic hierarchical',
'free_objects': 0L,
'free_space': 62688395264L,
'id': u's20002',
'name': u'Card',
'rw': True,
'type': u'removable_ram'}],
'type': 'media player'}

Trying to open: \\?\usb#vid_04e8&pid_6860#0b349b4f#{6ac27878-a6fa-4155-ba85-f98f491d4f33}
This device has been blacklisted by the user
No suitable MTP devices found

Looking for devices...
u'usb\\vid_04e8&pid_6860&rev_0400'
u'usb\\vid_2237&pid_4203&rev_0110'

Devices possibly connected: None

[kovidgoyal]

If windows cannot see it, neither can calibre.

[Karen Myers]

"If Windows can't see it..."

Yes, very true, but...

1) It saw it once, initially, and I managed to load my 400+ to-be-reads on it

2) Windows' "eject device" describes it correctly, and Calibre's "detect device" shows it (see above) but decides it isn't eligible for some reason, so it seems like it's not just a Windows issue... More like I screwed up a Calibre setting.

Any suggestions for experiments?

BTW, I also fill up my husband's Sony reader from Calibre, and Windows gives me the same "Device on D: -- want to format it?" message without impeding Calibre's ability to manage the device. Haven't tried it yet with the 64-bit 2.0 Calibre -- I suppose that's next.

Thanks.

[kovidgoyal]

It has to show up as a drive in windows explorer, without that calibre cannot connect to it. As for suggestions on what to do with misbehaving Kobo devices, see: http://manual.calibre-ebook.com/faq....-touch-glo-etc

[Karen Myers]

OK, I've been educating myself about sideloads of the firmware and can phrase some more intelligent questions (thanks for your patience)...

1) With the factory installed 2.8.0 (Aura) firmware, Windows can see the device properly. I've copied that installation to a backup.

2) I've downloaded the 3.3.0 firmware from MobileRead (thank you) and copied it onto the device directly. I unplugged the device, and it took the update. When I plug it back in, Windows (and Calibre) can see the device properly. Yay - this is progress.

3) I'm now at the stage of bypassing the registration, since that step is the kiss of death for Windows recognizing the device. 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. The 2.8.0 factory installation has an empty "user" table. I thought I might go thru an aborted registration for my new 3.3.0 device to get an example and then throw that away to repeat (1) and (2) manually, but of course, doing that destroyed my ability to look at the device in Windows to see the table. (Dumb).

So, where can I find an example of a dummy "user" record for 3.3.0 (Aura)?

[kovidgoyal]

I'm afraid I dont have much personal experience with Kobo devices (I only owned one, briefly, a few years ago), so you'll have to wait for someone with more knowledge of one to show up.

[Karen Myers]

I do have a single "user" record in the clean (unregistered) 3.3.0 install, but I don't know enough to alter it correctly:

Field Value

UserID dec75cef-493f-4da1-af8d-d7a7183fa3e5
UserKey 0a0e4b93-68fd-455a-b716-039e7c973dce
UserDisplayName demobundle06_13@kobo.com
UserEmail demobundle06_13@kobo.com
__DeviceID
FacebookAuthToken
HasMadePurchase false
IsOneStoreAccount FALSE
IsChildAccount FALSE

[Karen Myers]

Thanks, Kovid. I figured it out.

To complete the thread, here's a record which works for the User table for the Kobo Aura 3.3.0:

INSERT INTO "user" VALUES('aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa','aaaaaaaa-aaaa-aaaa-aaaa-aaaaaaaaaaaa','xxxx@xxxx.xxx','xxxx@xxxx.xxx','a', 'a','FALSE','FALSE','FALSE');

[davidfor]

Karen: That should work. What you can do now depends on what was happening before. If the database corruption was caused by the Kobo desktop app, then you should be able to login using WiFi. You would need to logout of the dummy account and then login with the real Kobo account. Of course, if you don't buy books from Kobo, this is not needed