TCP Optimizer version 2.0.2 RC2 (10/06/2005)

[Philip]

We've released an updated version of the TCP Optimizer 2, including a couple of non-essential bug fixes as described below. Note this is still a "release candidate" version of the program intended for testing purposes. The latest stable release can be downloaded here: TCP Optimizer v 2.0.1

The latest Release Candidate version can be downloaded here:

TCP Optimizer v 2.0.2 Release Candidate 2

The online documentation is available here: TCP Optimizer Documentation



List of updates and fixes in the 2.0.2 RC2 version (from version 2.0.2 RC1):

1. Changed the "custom" mode to show the "current" values by default (rather than "optimal").
2. Removed the LAN Brosing speedup and LAN Request Buffer Size from the Windows 9x version.
3. For Windows 9x, fixed the Advanced Settings "optimal" mode to show the correct Host Resolution Priority numbers
4. Fixed the optimal RWIN calculation to take into account custom latency preferences after program restart.
5. Changed "PPPoE" checkmark in custom mode to show when MTU=1492.

List of updates and fixes in the 2.0.2 RC1 version (from version 2.0.2 beta):

1. Fixed the optimal RWIN calculation for Windows 95 to use the same algorithm as newer Windows versions.
2. Fixed the advanced settings "Host Resolution Priority" to display the correct numbers in Windows 9x.
3. Increased the limit of RWIN for Windows 95 to allow for large TCP Windows in "custom" mode.
4. Removed ToS/QoS control box frame from Windows 95 version.

List of updates and fixes in the v. 2.0.2 beta version (from version 2.0.1):

1. Added all virtual NICs to the Network Adapters pull-down menu to account for nVidia and other on-board network cards with non-standard drivers. Sorted the pull-down menu by IP class for easier identification of the correct NIC (external IPs and the most likely NIC should be towards the top of the pull-down menu).
2. Replaced the "NegativeCacheTtl" advanced setting with "MaxNegativeCacheTtl" for Windows XP and 2003 Server (retained "NegativeCacheTtl" for Windows 2000). Note the "NegativeCacheTtl" setting is not removed by the program currently, that might change still in the final 2.0.2 version.
3. Added back the Tcp1323 options for Windows 95, although it is up to the user to update Windows and determine support for scaled RWIN values.
4. Fixed the version numbers to display correctly in the program properties.

You can view previous updates and past issues in the following threads:
version 2.0.2 RC1
version 2.0.2 beta
version 2.0.1 final
version 2.0.0 final
version 2 beta

[rafi_d]

Thanks. Great job! Almost all our comments were fixed. I'll put it also on my Networking forum for testing.

At first glance here are some (very minor) notes:
1. Alphabetic order in Registry tab
2. After selecting "PPPoE DSL" then moving over to "current" - this check-mark is being cleared. You have to re-check it again every time you cycle through the modes (unlike "modify all NIC" check-mark). I would leave it as the user last changed it regardless of mode changes.
3. I'm not sure about this one. When you "apply" a custom/optimal settings and do not reboot, the custom and current settings are from now on - being displayed differently. It might be a good "feature" - so that the user can still see what was before if he wants to go and change it back ...

Edit:
Here is an idea for enhancement -
I encountered many users having speed problems (mostly in P2P applications) that have to do with the maximum allowed TCP connections (in both 98 [default is 100] and XP-SP2 [default is 10] ). XP has a patch for it, and Win98-a simple registry setting.
How about displaying this parameter (in advanced tab) with some notes that explain it ? and maybe - also enhance the optimizer to be able to change it ?

I think it might help many users as well as boost the distribution of the TCPOptimizer !

[Philip]

Rafi, thanks for the comments and the constructive feedback.

For 1. --> The top keys only are ordered by importance as we saw it at the time. I am not sure what alphabetical order for those would be, since they're in different Registry branches.

For 2. --> one can choose a MTU that is 1492 even without being on a PPPoE connection... That's a bit confusing, but the PPPoE checkmark simply changes the MTU to 1492. Might fix the checkmark to show every time 1492 MTU is chosen in the final version I suppose.

For 3. --> will test, but it is very minor issue, that may be also perceived as a feature as you mentioned. Please note that if you make any changes in "custom" mode at all, until you restart the Optimizer it is not going to display the "current" values in "custom" mode anymore either.

[rafi_d]

Rafi, thanks for the comments and the constructive feedback.

For 1. --> The top keys only are ordered by importance as we saw it at the time. I am not sure what alphabetical order for those would be, since they're in different Registry branches.

The real problem is to find the important "MSTCP" within VxD ...

For 2. --> one can choose a MTU that is 1492 even without being on a PPPoE connection... That's a bit confusing, but the PPPoE checkmark simply changes the MTU to 1492. Might fix the checkmark to show every time 1492 MTU is chosen in the final version I suppose.

Right. A small thing - a "big" dilema... maybe automatically uncheck it not when "current" is selected (only gray it then), but when the user changes the value manually to != 1492

For 3. --> will test, but it is very minor issue, that may be also perceived as a feature as you mentioned. Please note that if you make any changes in "custom" mode at all, until you restart the Optimizer it is not going to display the "current" values in "custom" mode anymore either.

A good feature... leave it so...

See [edit] in previous post...

Thanks again for a job well done!

[Philip]

The problem with editing the number of concurrent connections being opened per second for Windows XP is that it requires editing of tcpip.sys, which goes a bit beyond the scope of this software. Note that the "10" limit is for 10 new connections per second in SP2, not 10 total open connections: http://www.speedguide.net/read_articles.php?id=1497

As for the limit on all open connections, it is huge by default in Windows XP, I'm not sure what the registry entry in Windows 9x was.

[Philip]

Fixed release to check "PPPoE" when MTU is 1492 and uncheck it otherwise.... Although this might not be entirely accurate for Windows XP where the default PPPoE MTU is 1480...

[rafi_d]

The problem with editing the number of concurrent connections being opened per second for Windows XP is that it requires editing of tcpip.sys, which goes a bit beyond the scope of this software. Note that the "10" limit is for 10 new connections per second in SP2, not 10 total open connections: http://www.speedguide.net/read_articles.php?id=1497

Right, so - maybe include the patch with the program and just execute it...

As for the limit on all open connections, it is huge by default in Windows XP, I'm not sure what the registry entry in Windows 9x was.

Here it is:
KEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\MSTCP\MaxConnections
http://www.dslnuts.com/9xme.shtml

Edit:

Fixed release to check "PPPoE" when MTU is 1492 and uncheck it otherwise.... Although this might not be entirely accurate for Windows XP where the default PPPoE MTU is 1480...

If 1480 is a max value embedded in XP PPPOE driver - maybe it is possible to detect if the user is using it, and 'recommend' this value for XP OS instead of 1492 ? Or 1492 is good for them too ?

[5MpstweakR]

All changes look good Phil.

One minor thing I noticed was a check mark in TCP1323 options for scaling when latency of 100ms is selected for a 5Mps connection with RWIN optimal of 62780.

I do not remember seeing this issue before in RC1.

Of course it is grayed out since it is optimal so not an issue... for those who are fastidious enough to recognize the inconsistency it may be viewed askance.

[Philip]

Rafi, at this point we're only looking at bug fixes, any additional features can be discussed for another version of the program.

1492 is the maximum PPPoE MTU value, that's all. It can be smaller than that, depending on the implementation.

5Mpstweak: I'm aware the Tcp1323 Options are set to 1, it was the same way in the previous release.


Thank you for testing guys, please let me know if you find any other issues with this release.