TCPIP Connection patch ????

Chappy said:

No argument there..

I can get 500 kBps from 3 seeders and then 45kbps from 100 of them. I think the longest my client took to build a good swarm was 8 or 10 minutes, which I don't really mind the time. The speeds are so subjective to so many different factors, it's almost impossible to know just what kind of speeds you should see.
I can take a 500MB file and start it, let the swarm build, and watch the speeds change from 100's to under 10 kBps within seconds, and then jump to 500 again a few minutes later. The swarm size doesn't change (too much) so how do we know that any changes we make have made a difference (truly) with such fluctuations?
All I know for sure is this, that limit has no effect on how many established connections you can have, and therefore cannot adversely affect speeds. I guess as long as the patch you're using doesn't kill the stack like the 64bit edition does, then if you feel it helps..go 4 it. But DO stay away from the 64bit patches as they fail the system file signature check run during bootup and causes a dead system.

if your talking about the 64 bit patch i posted it does not kill the system i know because i installed it on friends 64bit vista and 7 and it has never broke any os, you must not of followed the directions... or else your talking about some other patch.

i encourage anyone who wants to get the most out of their connection for p2p/torrents to install tcp-z and yes configure your torrent client for the patch aswell. read the readme before installation theres a reason its included.

x86/x64
http://soft3.wmzhe.com/download/deep...Z_20090108.zip

if you think your isp is throttling your torrent speeds.. test it here
http://broadband.mpi-sws.org/transpa...ttest-mlab.php

Chappy said:

No argument there..

I can get 500 kBps from 3 seeders and then 45kbps from 100 of them. I think the longest my client took to build a good swarm was 8 or 10 minutes, which I don't really mind the time. The speeds are so subjective to so many different factors, it's almost impossible to know just what kind of speeds you should see.
I can take a 500MB file and start it, let the swarm build, and watch the speeds change from 100's to under 10 kBps within seconds, and then jump to 500 again a few minutes later. The swarm size doesn't change (too much) so how do we know that any changes we make have made a difference (truly) with such fluctuations?
All I know for sure is this, that limit has no effect on how many established connections you can have, and therefore cannot adversely affect speeds. I guess as long as the patch you're using doesn't kill the stack like the 64bit edition does, then if you feel it helps..go 4 it. But DO stay away from the 64bit patches as they fail the system file signature check run during bootup and causes a dead system.

That is my point though, a fast connection and a relatively moderate sized file can be done in a matter of minutes with the patch. I completely understand it changes nothing regarding how many established connections you can have, this patch just lets you get there quicker and I think that is what I notice initially.

Just for the record, I have 64bit and the patch broke nothing for me.

It is kind of reminiscent of of my old WIN 98 days, some tweaks work well for some, but do nothing good for others. I remember the settings I used to modify would often just break other people connections LOL

Chappy said:

That is where you will notice any diff LT. I can't say I've really seen a big difference (I did try it with Vista 32bit) but when I went 64bit it was a system killer, and for a great many folks. They must have fixed it so that it passes the system check. Once I dug deeper into what the limit was and did, I just dropped it altogether and have never seen any horrendous slowdowns by leaving it.

i take it you didnt read the readme because you disable system checks before your install.
most problems can be avoided by actually reading the read me and installing things properly

This one worked for me on 7000: http://soft3.wmzhe.com/download/deep...h_20090205.zip

This is a Utorrent issue... many ppl around are complaining about the 1.82 build..... its a beta, which is installed on a beta OS, using alot of beta ipv6/toredo support...

This is software related, not internet/network related IMO.... and also not a TCP/IP max connections issue internally with windows, as most routers have a limit on them as well, and hold on to "dead" connections for way too long, some over 48 hours.... google it all, its on there somewheres... and have a look on the utorrent forum troubleshooting the 1.82 bug build... most have went back to 1.81.... you can still enable utorrent protocol in that program in the advance settings... all this on their forum... not also to mention what other settings you could be using with the program, DHT local discovery etc

dunno if this has been posted so i figured id go way back and post it in this old school thread

was just reading vista sp2 and windows 7 newer builds have removed the half open connection limit

How to enable the half-open TCP connections limit in Windows Vista with Service Pack 2 and in Windows Server 2008 with Service Pack 2

so no more need for tcp-z n all the others