Regarding the TCPAck change - not the QoS hack
Quote Originally Posted by Los',index.php?page=Thread&postID=198654#post19865 4]But does just the latency number go down, or is the general 'feel' of lag and gameplay actually improving?[/quote]I did this manually over the weekend, my dad did too. There was a noticeable difference in game play. Any of you that software box I am sure have noticed that if your dudes are just standing there and you jump, the dude jumps on his own client then the other dudes jump. That is a direct effect of your latency. If it was zero all would jump at the same time. With my my latency went from ~280ms to about 80. And there was a noticeable difference in "jump coordination". The biggest place I saw this difference was in the Arget Tournament Mounted combat. If I PvP'd I suspect I would see a difference there as well. If you read the what the TCPackfrequency does, dropping ~200ms is exactly what should have happened. By default it queues ACKs up to 200ms trying to send 2 at once. Making the change causes it to immediately ACK every packet. so you should see a drop in 200ms if you do it.

These are the references I used to make the change (from the email I sent to my dad). Make sure to reboot after. I would never run an unsolicited VB script. I probably wouldn't run a solicited one either. Registry editing can be very dicey (I hate the registry, worst thing every invented for computers) but this is a pretty simple change and the instructions can be had straight from Microsoft.

I also strongly recommend following the procedure to back up your registry (see below) and even printing out the procedure to restore your registry if you do not have a second computer to look it up in the event of a disaster.




[quote][url]http://support.microsoft.com/kb/328890/[/url]
[url]http://forums.worldofwarcraft.com/thread.html?sid=1&topicId=4665621068[/url]



Important This section, method, or task contains steps that tell
you how to modify the registry. However, serious problems might occur
if you modify the registry incorrectly. Therefore, make sure that you
follow these steps carefully. For added protection, back up the
registry before you modify it. Then, you can restore the registry if a
problem occurs. For more information about how to back up and restore
the registry, click the following article number to view the article in
the Microsoft Knowledge Base: 322756

([url]http://support.microsoft.com/kb/322756/[/url] )
How to back up and restore the registry in WindowsSubkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interfaces\<Interface GUID>

Entry: TcpAckFrequency

Value Type:
REG_DWORD, number

Valid Range:
0-255

Default:
2

Description:
Specifies the number of ACKs that will be outstanding before the
delayed ACK timer is ignored. Microsoft does not recommend changing the
default value without careful study of the environment. For more
information, visit the following Microsoft Web page: [url='http://technet2.microsoft.com/WindowsServer/en/library/823ca085-8b46-4870-a83e-8032637a87c81033.mspx?mfr=true%20%28http://technet2.microsoft.com/WindowsServer/en/library/823ca085-8b46-4870-a83e-8032637a87c81033.mspx?mfr=true
http://technet2.microsoft.com/WindowsServer/en/library/823ca085-8b46-4870-a83e-8032637a87c81033.mspx?mfr=true
(http://technet2.microsoft.com/WindowsServer/en/library/823ca085-8b46-4870-a83e-8032637a87c81033.mspx?mfr=true[/url] )
If you set the value to 1, every packet is acknowledged
immediately because there is only one outstanding TCP ACK as a segment is just
received. The value of 0 (zero) is not valid and is treated as the default, 2.
The only time the ACK number is 0 is when a segment is not received and the
host is not going to acknowledge the data.
Formatting - looks better now that is basically quoting myself.