I've changed that because i thought that a upload speed of 30-39 kb/s is more usefull.
Yes it would be possible to add a FakeUp Version with the value 1 in the front.
Printable View
I've changed that because i thought that a upload speed of 30-39 kb/s is more usefull.
Yes it would be possible to add a FakeUp Version with the value 1 in the front.
Because, it's real stable... has optimal and checked prefences.
And uTorrent, especially 2, is polygon for testing new technologies and insane tunings.
For example,
net.max_halfopen 100
net.utp_receive_target_delay 100
net.utp_target_delay 100
Now I'm using BT 6.4.
Good, but very need DHT-Patch
...
plz
thnx
uTorrent 2.0 18488 ~ 400 kb (UPX Compressed)
BitTorrent 6.4 ~ 640 kb (UPX Compressed)
...
Some people say that newest versions of uT takes more memory and % CPU (against bT).
Also there are knowing problem with the "wavy" speed of seeding in 1.8.3+.
And BitTorrent is stability of old versions with some useful features (such as magnet-urls) of new muTorrent versions ...when uTP becomes more useful, it appears in BT in full (now 6.4 has bt.transp_disposition 13)
oops.. I must be miss something. :) I guess 2.0 has been changedQuote:
By the way, uT's default value for net.max_halfopen is 8, not 100...
Fair enough, I'll do a BT pack based on the latest version, then. But uTorrent also "has" bt.transp_disposition 13... it's 8+4+1, meaning incoming and outgoing TCP connections, as well as incoming uTP ones only, are allowed. This is how old 1.8.x versions act, I think.
It's been like that since I started using uTorrent back in 2006 :happy:Quote:
oops.. I must be miss something. :) I guess 2.0 has been changed