Proxomitron reduces RWIN to 32768

[laighleas]

JJoe Wrote:Good news, if only that somebody with XP/Home/SP2 is seeing the correct number for RWIN.

But just to be clear:
Did you have the problem *before* you patched tcp.ip.sys?

No. However, the patch wasn't in response to the problem - it was in anticipation of it, and almost immediately following my recent upgrade to sp2 from sp1. I was doing a clean install, and had left it a bit late so that all the various problems and hiccups were well known. :-) I was aware of the restrictions on tcpip.sys under sp2; I was also aware, from earlier experiments/observations with Proxomitron, that these new settings might well have a direct impact on Proxomitron's performance. I therefore patched it as a matter of course, almost immediately after the upgrade so that I didn't have a future problem. Of course, I can't rule out cocking a snoot at MS as a motive as well. :-) But mostly it was seeing an anticipated problem and dealing with it ahead of time. :-)

JJoe Wrote:RWIN is the number you set, after you patched tcp.ip.sys?

With the patched tcpip.sys the system, without any tweaks - other than having hardened the stack - gave me 65535, whether Proxo was used or not. This was the value set by Windows in the registry when it installed sp2. After spotting this thread I decided to do a few speed tweaks, after which I checked the RWIN again, and got a value of 257004 with or without Proxomitron, which is what the registry gives as the value.

JJoe Wrote:Do you have the problem now, if you use an unpatched tcp.ip.sys?

Haven't unpatched it since. :-) No point, except maybe for experimental purposes. But if I get some time, I may run the experiment. :-)

Kevin