Quote:
Originally Posted by JimmXinu
Of course, now I can't duplicate the problem even sending the same file from Calibre. So that helps a lot. And now I can't find any other cases of it, just to insure I look crazy.
 |
Main screen turn on. "How are you, Gentlemen? All your base are belong to us. You have no chance to survive. Make your time.
Ha ha ha."
Quote:
|
I'm not able to find anything about manually testing the wireless device interface. Can I get a pointer or a phrase to google for that? Pointing my browser at ipaddr:9090 gets some basic library metadata in JSON after a lengthy (~5minute) wait.
|
You won't have joy. The wireless protocol is reasonably complicated. It is a "push" interface, requiring the client to respond in certain ways at certain times.
Koreader has an independently-written client. If it is reasonable for you to install it then the next time something breaks you could use koreader to see if it breaks in the same way. You could also look at the code of this client, given that it is open source. You can also look at the code for the wireless device driver.
Quote:
|
I am assuming (possibly wrongly) that the 'smart device' AKA wireless device interface is different than the Content Server.
|
Yes. The two have little to do with each other. The point of commonality is that calibre will prepare the file to be transferred in a similar way.
Quote:
|
I also noticed that the corrupted zip files were ~2x the size of the correct one.
|
Now that is interesting. A protocol error would result in byte-for-byte corruption. Doubling the number of bytes points strongly to a problem at the source.
Quote:
|
Thanks for your help, folks.
|
You are welcome. It is little enough payback for all you do for the calibre community.