i found one in windows 7 x64. When trying to enable the ctcp the set global command failed in ipv4 the paremeter is incorrect
TCP Optimizer version 3.0 released ! (Windows 7/Vista support)
I'd like to announce we've released TCP Optimizer version 3.0 (Release Candidate 1) today, including Windows 7/Vista/Server 2008 support, as well as continued support for older Windows versions (9x/XP/2000/2k3 Server) and many minor improvements.
This version 3.0.1 is now the latest stable release.
It can be downloaded from the same location as previous releases:
TCP Optimizer v 3.0 (last build 3.0.1, 07/08/2010)
Please post bug reports, comments and feedback about the release in this thread.
The online documentation is not yet updated with all new settings, but available here: TCP Optimizer Documentation
The documentation includes a changelog as well.
You can view previous updates and past issues with the program in the following threads:
version 2.0.3
version 2.0.2 final version 2.0.2 RC2 version 2.0.2 RC1 version 2.0.2 beta
version 2.0.1 final
version 2.0.0 final version 2 beta
i found one in windows 7 x64. When trying to enable the ctcp the set global command failed in ipv4 the paremeter is incorrect
Comptia a+ n+
Disregaurd above make sure you right click the optimizer and select run as administrator
Edit I was wrong when you try to enable ctcp it errors out
Last edited by mccoffee; 07-07-10 at 04:56 PM.
Comptia a+ n+
Confirmed, will need to fix that.Originally Posted by mccoffee
The correct changes are actually applied (you can verify by restarting the Optimizer and checking the "current" settings), just that the error is displayed incorrectly.
Great work Philip, thanks for your hard work.
aGreat work Philip, thanks for your hard work.
Tottaly agreed
another glitch though like above with the ctcp it gives the same error when reverting back to default but the settings do apply.
Comptia a+ n+
Tested in vista x64 the optimal setting took off wihtout a hitch no errors just ok for every setting
Comptia a+ n+
Tested @ winxp.
@ 1st run, doesn't read my last TCPO 2.0.3 settings
TCP Optimizer Current Settings:
(3.0 / 2.0.3)
MTU - blank / 1500
TTL - blank / 64
TCP Receive Window - blank / 64240
MTU Discovery - Yes / Yes
Black Hole Detect - No / No
Selective Acks - Yes / Yes
Max Duplicate ACKs - blank / 2
TCP 1323 Options:
Windows Scaling - check / check
Timestamps - uncheck / uncheck
Advanced Settings tab:
Max Connections per Server - 10 / 10
Max Connections per 1.0 Server - 10 / 10
LocalPriority - blank / 5
Host Priority - blank / 6
DNSPriority - blank / 7
NetbtPriority - blank / 8
Lan Browsing speedup - blank / optimized
QoS: NonBestEffortLimit - blank / 0
ToS: DisableUserTOSSetting - blank / 0
ToS: DefaultTOSValue - blank / 0
MaxNegativeCacheTtl - blank / 0
NetFailureCacheTime - blank / 0
NegativeSOACache Time - blank / 0
LAN Request Buffer Size - blank / 16384
# OS: Windows, Linux # Browser: Blink, Gecko, Presto, Webkit + Squid + Bind
works fine for me and reads all the past values i have set. Another great job, "keep walking......" Philip
edit:i was wrong. it can't read my hamachi vpn adapter, where from you "sniff" the adapters"? u have to, from currentcontrolset/class..... i think is the right path
tested under win 7/vista 32bit
Last edited by 100 010 00; 07-08-10 at 03:45 AM.
There is no patch for stupidity
Thanks for that report! Are you running XP in a Virtual Machine by any chance ?
The Hamachi VPN adapter seems to be using a non-standard IP address location, that's why the Optimizer doesn't pick it up... ( VirtualDHCP.ClientAddr ). Will look into it when I get a chance, but it should be an isolated case.
its ok for me, but the previous one, was always able to resolve all of my vpn adapters (hamachi, remombo, etc,) in all os's
There is no patch for stupidity
I just ran optimized settings on Windows XP, and looking at the Analyzer it doesn't set the TCP Window correctly.
« SpeedGuide.net TCP Analyzer Results »
Tested on: 07.08.2010 12:29
IP address: 67.235.xxx.xx
Client OS: Windows XP
TCP options string: 020405b401010402
MSS: 1460
MTU: 1500
TCP Window: 65535 (NOT multiple of MSS)
RWIN Scaling: 0 bits
Unscaled RWIN : 65535
Recommended RWINs: 64240, 128480, 256960, 513920, 1027840
BDP limit (200ms): 2621kbps (328KBytes/s)
BDP limit (500ms): 1049kbps (131KBytes/s)
MTU Discovery: ON
TTL: 120
Timestamps: OFF
SACKs: ON
IP ToS: 00000000 (0)
Updated to version 3.0.1
Fixes:
- correctly reads current settings under XP
- temporarily disabled incorrect error message under Windows 7 x64 after applying changes.
- minor cosmetic/message updates
What version of the Optimizer (Help > About). Should be 3.0.1 ....
When you apply the settings and reboot, does the Optimizer (not Analyzer) display the correct "Current settings" ?
If the Optimizer displays the correct settings, but the Analyzer does not, that means there must be a router on the path, or your ISP that changes those settings.
Another possibility is that there is a transparent web proxy between your machine and the Analyzer, so it can't read your settings and is displaying the ones of the machine connecting to it (check the IP address in the Analyzer and make sure it's yours).
Tried the new one in 7 x64 works great
Comptia a+ n+
I started TCP Optimizer under Vista and XP.
On Vista I see many new settings but under XP its the old 2.0.3 look.
Do you can enable these settings under xp too ?
eg. gaming settings
if you have xp 64 you should be able to enable ctcp or compound tcp
Comptia a+ n+
i dont run XP in a VM, i'll report any bug or etc of TCPO v3 under XP SP3 + full hotfix (up2date)
# OS: Windows, Linux # Browser: Blink, Gecko, Presto, Webkit + Squid + Bind
Make sure to re-download and try with the 3.0.1 version, there was an issue with 3.0 reading some XP current settings. Thanks.
Posting Permissions
Bookmarks