the pic show me u havnet do port foward coz "local"

but before stop seeding
it also help increase ur download speed...

i juz hope there no any ppl like my stupid friend
he juz limit his upload speed to 2kbps
when i ask him to increase it
he said:"you are silly ar? that upload file to other ppl!"
i think he really silly
think that upload file will make file lost....
upload file didnt mean you will lost the file!!!!!

hope no one in here will think like that
and let it be a reason for a selfish ppl

im used bit comet before and then switched to utorrent. i find u torrent is much better, faster and takes up less resource. i really recommend utorrent over any other clients.

but sumtime the seed will moved very slowly after a while, but after i shift the half dl to bitcomet, it just run 58kbps.

So hard to understand the portforward website...complicated!

Anyway...what's the U-torrent website neh?Does U-torrent need portforward too?

I'm using Bitorrent 0.58 ..wahaha..classic one.

it's �Torrent, not U-Torrent

the site is http://www.utorrent.com/

any client needs portforwarding if you're behind a router/firewall

nah, v0.71 is released, go and grab it lah

any new feature?

my average dl speed is 60k/bs , for rm66 tmnet streamyx

you are in heaven...

my fastest speed is only 50kbps
and i just got this speed when the seed is still fresh + many seed......

the file that you download is the lastest file?
(dun talk about the file that you dl...)

http://forum.lowyat.net/index.php?showtopi...view=getnewpost

but someone say 0.71 won't let u limit the upload spd

how to do port forwarding ??
any website guard introduce??

from soo

http://www.portforward.com/

thankx~~ sotong

but if you use the modem Riger DB102
the portforward website didnt hv any info about it......

so, dun get Riger DB102 as ur modem!!!!!!

my house is using a router connect to a 8 ports switch..
izzit can set the portforward as normal mention in that website??

from soo

your fresh degree is ? seed about passed one month also speed like that

u r fast, mine now is just 54kbps.

crap! version does not affact the DL speed.
all you need to do is look for "local seeder", as many as possible, this is the key in high spped DL.

So in BitComet 0.71, which the Option configure the TCP/IP is located..
Option > Preference > TCP/IP Limit.

[B]AND DO NOT USE IT TO MODIFY YOUR SYSTEM FILE!!
It would crash your TCP/IP System File and windows couldn't detect your connection in the Network Card.[/B]




I know this topic suppose to open in Technical or Software Section.
BUT most users are BT hardcore in here and most using BitComet though.

HERE the 0.71 version is about the new design.
Inside got an option which could modify the TCP/IP system file by setting the 'TCP Half-Open Limit'.

I know, some people are using that a FIXED TCP/IP patch which is hot spreading in the Website and run it just edit the System File in the Dos Mode thing.
But recently, that thing is not allow to run anymore for the UPDATED WinXP SP2 or those PC with newest WinXP installed.





So here is what my experienced.
Story... ... ... ...
Yesterday i was upgraded to 0.71, i found that the TCP/IP option!!
i felt "wow this is make much easy for me." I go and make changes... back problem appear.

I tried everything out, firstly i though it was Router F up!! and i checked NO! is not, i even had OPERATION to my PC!! but things is fine!...

Today i have formatted my PC, everything back to normal. After that the problem come back again~ i'm shocked!! tried everything and check, i'm thinking "it's virus?!"

After 6hrs checking, that i realize is this TCP/IP thingy!!
Because the most early program installed and configure is BitComet 0.71 and the TCP/IP Setting as well.
Problem occur will make log into the EVENT VIEWER and those Logs would keep saying the SSDP Service started and stop, TCP/IP is failed to Initialize.

here the Event ID code... 7000, 7001, 7036.
Story Finish, this is what happening to me. And share with you guys!!
So please dont risk to try it guys ~~"

Dont open fire to me hor... if i make mistake.
Sorry for Little boy's BAD English.