This was needed in Beta times (or even pre-Beta?). MS eliminated connections' limit in Win7 RTM, thus no need to patch tcpip.sys anymore.
I realise what has been going on. The TCP-Z reads the tcpip.sys file and gets the current hard coded half open connection setting. So one could be forgiven in thinking that this is the current setting the system is using, however if the EnableConnectionRateLimiting setting is a value if 0 or non-existent (Disabled), the operating sysstem will set the TcpCreateAndConnectTcbRateLimitDepth value 0 in the kernel memory, and the half-open outgoing TCP connections limit is removed immediate, without having to restart. The system will treat the new half-open TCP connections as always 0, and thus bypass the limit comparison altogether. Thus, you will notice that event ID 4226 will no longer been logged in Event Viewer. Likewise, when the EnableConnectionRateLimiting is set to 1 (Enabled), TcpCreateAndConnectTcbRateLimitDepth will also be set from 0 to 1 in the kernel memory, the OS will calculate the rated speed of ‘create and connect’ TCP connections been established, and limit the maximum attempts to 10. Which explains why we do not need the TCP/IP patch in windows 7. So frwil I stand corrected and thanks for giving me the insight to research the subject....