Size limit in content server downloads? - Page 2

PepeM · 07-25-2011, 11:48 AM

Chaley,

Quote:

Originally Posted by chaley

Have you messed with the network settings, in particular the MTU or TCP window size?

Wow, that's a very nice try. I hadn't even thought of something like that.

Well, last time I messed with MTU and the like must have been in W95 or W31 time to enhance TCP over the modem performance. Boy, am I *that* old? :-)

Just in case I did it and didn't remember, I took a look at the registry and found no obvious reference to a TCP MTU value other that the default. The TCP setting shows a value which looks like some kind of MTU detect is enabled.

Quote:

Originally Posted by chaley

You might want to look at windows event logging to see if some kind of network error is being reported.

Nothing obvious there either.

I'm at a loss at what can the problem be. I just hope we won't find, in the end, that the technical problem sits between the back of my chair and my keyboard. :-)

BTW, I also updated Caliber to the 0.8.11 version and no joy.

Pepe

chaley · 07-25-2011, 12:11 PM

The difficulty here is that calibre thinks it successfully delivered the entire file to the network subsystem -- it was not given an error. The client (firefox) receives only a part. That says that *something* between calibre and the client is eating the data. (BTW: I think that the server log eliminates the brain-to-keyboard-error possibility.)

We are left with the question "what lives between the two level 7 apps when using localhost?" (I remember from some post above that you are testing with localhost.) These kinds of problems are extremely difficult to debug. The network card should be out of the picture (but I don't know that), leaving the IP layer and the TCP layer, both of which live in Microsoft's winsock stuff. In addition, there might be other things playing in the sandbox such as loopback connectors, netbios, netware drivers, VPNs, and who-knows-what. My suspicion is that something you installed has 'optimized' networking for you without asking your permission.

If you have another machine, and if you have time and energy, you might consider installing calibre on it to see if it behaves in the same way. Even better would be to test on a new install, perhaps in a virtual machine. The goal here is to either a) have a reproducible scenario (reproducible by us) that establishes the problem is in calibre, or b) show that the problem is in the guts of your machine. The problem with a) is that if the problem were easy to trigger, we would have heard about it. The problem with b) is "OK, so I know. Now what?"

Good luck!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Calibre Content Server and Windows Home Server 2011	HughMcC	Calibre	8	10-01-2014 07:26 AM
Is there a size limit for TOC.ncx?	osnova	Kindle Formats	10	10-21-2011 01:41 AM
Practical size limit on epubs	bobcdy	ePub	4	11-13-2010 04:13 AM
Size limit on PDFs?	tench	Sony Reader	4	06-24-2009 06:48 PM
PDF size limit	sic	Sony Reader	14	07-15-2007 04:50 AM

07-25-2011, 12:11 PM	#17
chaley Grand Sorcerer Posts: 12,449 Karma: 8012886 Join Date: Jan 2010 Location: Notts, England Device: Kobo Libra 2	The difficulty here is that calibre thinks it successfully delivered the entire file to the network subsystem -- it was not given an error. The client (firefox) receives only a part. That says that something between calibre and the client is eating the data. (BTW: I think that the server log eliminates the brain-to-keyboard-error possibility.) We are left with the question "what lives between the two level 7 apps when using localhost?" (I remember from some post above that you are testing with localhost.) These kinds of problems are extremely difficult to debug. The network card should be out of the picture (but I don't know that), leaving the IP layer and the TCP layer, both of which live in Microsoft's winsock stuff. In addition, there might be other things playing in the sandbox such as loopback connectors, netbios, netware drivers, VPNs, and who-knows-what. My suspicion is that something you installed has 'optimized' networking for you without asking your permission. If you have another machine, and if you have time and energy, you might consider installing calibre on it to see if it behaves in the same way. Even better would be to test on a new install, perhaps in a virtual machine. The goal here is to either a) have a reproducible scenario (reproducible by us) that establishes the problem is in calibre, or b) show that the problem is in the guts of your machine. The problem with a) is that if the problem were easy to trigger, we would have heard about it. The problem with b) is "OK, so I know. Now what?" Good luck!

Advert