Quote Originally Posted by 'chazz',index.php?page=Thread&postID=74389#post743 89
Looks like you were right, once again, Freddie!
Holy smokes, I got lucky twice in one thread!

It was a nagle issue and a recurring 'CPU situation', appearantly you can't take manual steps to fix this in the registry, the change has no effect.
I found a patch to download and install though and also created a .reg file for TcpNoDelay thing, don't know if that really works then either but did it anyway.
Could you say where you got the patch? I'd like to know so I can tell other people.

Result? The following;
Woot. That's awesome. I'm glad this long thread worked out so well.

I was wondering about the registry advice in those links because I thought probably WoW was requesting Nagle in its client, and I thought it would be odd if Windows allows a system-wide registry setting to override an applications choice, especially since that part of the Windows API (net communications stuff) is incredibly technical and it's used by specialists who write incredibly sophisticated server software and I couldn't imagine that Microsoft would take away control over Nagle from them and put it in the registry. And based on what you've observed, I guess they didn't.