Hi Hervé
The TELNET TCP windowing operation is explained in chapter 6 in
http://www.utasker.com/docs/uTasker/uTaskerTELNET.PDFIt is possible (and normal) that debug outputs are sent in more that one frame but usually only the first frame will be of small content since the maximum amount of buffered data is sent in each frame.
Could you upload the Wireshark recoring since I can then also look in more detail at the frames - at the moment I don't see anything anormal based on TCP content, but I think the issue is more about the timing.
I would only expect delays when there are lost TCP transmissions or receptions an dthus repeats take place. I don't see any reception loss and also I don't think that there is any transmssion loss (a repetition when sending will generally result in large TCP frames being send becasue there is mnore waiting data in the meantime and this doesn't seem to be true). I note that windowing operation is taking place and also a final frame has a lot more content (all expected operation).
Regards
Mark
PS: Did you make the change from this post?
http://www.utasker.com/forum/index.php?topic=1001.0I have generally deactivated thsi since I was sometimes getting strange behavior (slow web pages). I think that it is because an Ethernet reception event was being lost (internal queue overflow - increasing Ethernet task queue would possibly solve it) and it caused the Ethernet reception to be always one frame behind (loss of synchronisation). I don't however think that it is your problem but best to at least mention it just in case...