for BC u need to forward both as DHT network will need udp port, if u r not using DHT, then just tcp is enough

by default the torrent file is saved at Torrents folder inside ur Bitcomet folder, try look it out (e.g.: C:\Program Files\BitComet\Torrents)


depends on the file u r downloading, if the tracker is based on the affected area then no connection is just reasonable (didn't u read the news about underwater cables got "snapped" at South of Tw???)


can't blame much on TM for this time (except for the fact tat they don't hav fund to support backup routing plan... )

As u can see, u are connected to peers at DHT network... tat's the good thing for BC, we are not limited to the connection via trackers (but for some private trackers, they don't allow such function)...

a simple tip: change back to ver 0.70 if u think it's not "right"

for my case, I can always connect to remote ports without prob, may b bcos of the torrents I'm dling...


tat's for sure it will affect the connections, furthermore with the current "cable-under-repair" situation...


80% is just a reference given by "foreign countries" users... for our streamyx case, it's better u adjust and try, so far for 512k (as I'm using) I found out tat around 15~18k is the best... (more u get ur connections choked; less u get fewer connections)

I used to get tat kind of "false" info shown on the toolbar... my guess is there is some bug or just delay in passing the info...

there is nothing can b done, unless may b u can restart it as to "reset" and hope it back to normal


tat can't b true at all, since TW earthquake I can still dl with bitcomet, just not tat good speed at daytime, but at night still getting full speed with very "healthy" torrents

This post has been edited by yelsew: Jan 12 2007, 08:57 AM

I'm not sure tho.... I nvr on tat auto resume function

probably something conflict with tat function and bcome "unabled"?

*edited: btw... which ver u r using? may b tat ver got bug for tat function?

This post has been edited by yelsew: Jan 12 2007, 01:06 PM

I guess it's bcoming a normal case where dev improve or upgrade some parts, possibly affected other existing part of the program

I think some private trackers are blocking the connection of BitComet as they don't encourage the DHT network provided by BitComet... (it's just my guess)

it's your choice then if u like it

for me I'm using both as different sites/forums will recommend different clients... in tat case I won't b missing any "interesting" files

This post has been edited by yelsew: Jan 13 2007, 09:07 AM

programs structures and concepts different?

I just notice tat BitComet most of the time (for 0.70 tat I'm using) need to "make full" to the min disk cache size then only it starts to get faster... I wonder if other ppl also having this...

uTorrent didn't hav tat issue tho... so it starts faster?

uTorrent got its own file-rename, check whether it's on, if it is then just do the rename for the file u r dling... after the files added to uTorrent, it/they will b hash checked b4 resume (the torrent(s) file u can always get from BitComet\Torrents folder)


with current situation it's hard to decide whether u got throttled or not (I mean TW earthquake issue...)

just hope it's not really throttled...

u should pull it wider to show the initian... there will state whether it's remote or local...

oic... so the concept has changed... if tat's the case then I get mostly from "local peers" too... tat appear as "Remote Initiation"

mostly ppl use it for blocking the connections which they suspect no flow of data occuring...

since u can log on here, I suppose the pc/laptop u r using already hav a static IP???

or u r connecting thru a dhcp network?

u can try with the small program I attached. It's the original tcp/ip patch

almost full (most time 50K+ for 512k), if the torrent is in good health (above 500%)
but not everyday...

may b it's bcos when u start dl other torrents the bandwidth been taken and ur existing connections were dropped to allow new connections to go thru. So, when u "resume" back, u need to "reconnect" back...


not tat "complicated" to do portforwarding... u can refer here:
http://www.portforward.com/
check ur modem/router model then look it up there, should hav some guide for u to do it