[chaley]

Originally Posted by kdsksg

Yes, this is the verbatim log that popped up after I closed the debug version of calibre. All I did was save as and send it to you.

In that case we know the problem. The wireless device driver did not start. You should see lines like the following near the top of the log

Starting up...
Started up in 4.32 seconds with 77 books
SMART_DEV (   0.00:  0.003) _attach_to_port try ip address "" on port 9090
SMART_DEV (   0.94:  0.802) startup_on_demand listening on port 9090
SMART_DEV (   0.95:  0.001) _attach_to_port try ip address "" on port 54982
SMART_DEV (   0.96:  0.000) startup_on_demand broadcast socket listening on port 54982
SMART_DEV (   1.98:  1.019) run All IP addresses {'{4AFD7AF6-F037-4FA9-B866-8B2334C445C9}': [{'broadcast': '192.168.120.255', 'netmask':'255.255.255.0', 'addr': '192.168.120.6'}], '{B237AF4A-8A56-4AF7-B64F-C236001A871E}': [{'addr': '169.254.156.167'}], '{4278D57E-9ADF-11E6-9A9E-806E6F6E6963}': [{'broadcast': '127.255.255.255', 'netmask': '255.0.0.0', 'addr': '127.0.0.1'}], '{97D48348-3352-41E0-8698-71FA9D292B0A}': [{'addr': '169.254.194.204'}], '{1F6BE112-2686-491E-AA9E-98FE9F816D3E}': [{'addr': '169.254.212.152'}], '{9B0F7C9C-D29B-4518-B8CF-3C16072273F9}': [{'addr': '169.254.101.42'}], '{B9045235-697D-4857-AF18-EBB356CBBD47}': [{'addr': '169.254.175.222'}]}

What I don't know is whether the WD driver isn't set to start, is attempting to start but failing, or is very very slow to start.

I think the middle one is not likely because something would be in the log.

You can check the first one in calibre by pressing the Connect/Share button. If the WD driver is running then you will see something like the following image. The important bit is the green dot and the existence of IP addresses.



As for the last one, you can sort-of check this by waiting after you start calibre to see if the SMART_DEV log lines eventually show up in the log.

And yes, I'm running a much older version of calibre because I'm resistant to upgrading because it seems that every time I do update anything as I usually loose something vital or run into major glitches. However, if the solution is to upgrade, then that's what needs to be done.

I don't know if upgrading will fix it. It lust might. There have been many intervening changes to the wireless device driver, including to device detection.

If the upgrade doesn't fix it but does break something else then you can downgrade back to where you are. This isn't the optimal outcome so I hope you don't end up there.

Yes, I previously used Marvin on my iOS device before the Marvin/Apple iOS 8.3 incompatibility. I haven't revisited using Marvin on my iOS with my Calibre but that is an option on the table if I can't get the Samsung to cooperate.

If you aren't using the plugins then try uninstalling them. It is very possible that they interfere with the WD driver, especially on that older calibre version. Do this before trying an upgrade.

Do I need to create another debug log, or is the fact that it's missing those bits of information symptomatic of a problem? I followed the instructions detailed in the FAQ that you linked me to. I opened calibre in debug mode, attempted to connect CC and calibre a total of twice (with my IP and port specified), which both failed, and then I closed calibre (debug), saved the log it generated, and emailed it to you.

Yes, I need to see a calibre debug log that contains the lines shown above. If those lines aren't there then CC will not work.

Am I just a jinx (my hubby says so!)?

My wife has a similar problem. Computers don't like her. Frequently she does something and it doesn't work for inexplicable reasons. She asks to come up and mansplain things to her computer (not her), then she tries again with me standing there. It works. Neither of us knows why. She has given up trying to understand, as have I.