This is a known problem. BitComet is in deed downloading good data, the problem is that these data fail the hash-check and will be excluded.
The problem is due to the feature called: “Long-time seeding”. It’s BitComet’s internal network, improving the downloadspeeds dramatically, however, this feature is very new and needs further development. It’s still in BETA stadium.

Simply disable the “Long-time seeding” network when experiencing this problem. It only happens rarely – you can be unlucky though.

There are no problems on Private Trackers, due to the Long-time seeding network only is active when the torrent doesn’t have private flags enabled.

The bug is reported to the developers.

Best regards,
Unofficial BitComet Ambassador.

One thing I find quite amazing is that when I use both client to download a same torrent from the same tracker, I always find that BitComet has a higher download status. Was using that BTCMT 0.66 till few days ago I have upgraded to their new 1.03. With this new program, it’s the same, it could download much faster compared with UTorrent, till guess what?

For the fun of it, I just put on the summary section and look at the actual figure displayed. UTorrent could only download about 10 to 15 kbs but with BRTCMT I could download from 55 – 70 kbs. What I saw was a bit scary. Even though the download status keep on changing every second, the current downloaded data on the torrent doesn’t increased. In few minutes, only few mb loaded. This means that the status of 55 to 70 kbs is not true? So, what the hell is BTCMT downloading? Even if the Downloaded data increase, you could see that it increases by 10 to 15 kbs only. Then why showing 50 – 60 kbs? At times, with this high status going on and on but teh downloaded data don’t even move for few minutes, lol!

example:
if downloading at 50 kbs, I should get 3 mb in 1 min which will come to 180 mb in an hour and within 10 hrs, I should get 1.8 gb. Plus minus a bit, perhaps, lower it to 1.4 to 1.5 gb only, ok, acceptable.But guess what, after leaving it there for about 15 hrs with 50 to 65 kbs in the status, it only downloaded 800 mb. The uploading status was at 10 kbs and it logged it has uploaded for 500 mb. Crab!!! Always shown that the downloading is about 5 times more then uploading but the result is not.

Anyone has experience the report been false compared to the actual data downloaded? Or what other things have they downloaded? Thought I read somewhere that in the new version, this false report don’t happened anymore but it seems that it’s still there.

.

Regarding the HTTP-support seeding and long-time seeding, check this out. A picture says more than thousand words, right?

(Persistent seeds = HTTP-seeds and Long-time seeders.)

http://img209.imageshack.us/img209/8383/persistentseedsba3.jpg

This system works – also considering that torrent, I was downloading was pretty low on peers.

-XS.

1. It shows a torrent as completed (switches you to a seeder) even if you only have 1% of the total torrent. So if you choose to download just one 1kb file out of a 10gb pack, you will still be seen as a seeder, which is incorrect. Until this is changed, it will never be allowed on any private trackers (and should not be allowed on public ones either imho).

2. It does not send a correct user-agent. It shows itself as “Mozilla .xxx). Another reason for private trackers not to allow it. Most block user-agents with “mozilla” in them, to stop cheating.

So, even though it does not have the bugs, its still a bad client, especially for private trackers. It shall remain banned until these things are fixed.

That was fixed a long, long time ago. BitComet is perfectly safe for private trackers.

And just to let you know, Vuze does track your downloads and phone home about them.

If azureus made a kickass lite version it would be awesome. Like one without all the guiy bs. One that could still work with the kickass plugins but not take 2 mins to load with a shitty media player. Azureus team take a fucking hint please.

rTorrent and kTorrent are also good options for and nix machines.

With bitcomet/utorrent its whatever they want to throw you, be it back doors, bombs, cripleware, unwanted tracking, etc.

Want to make bitcomet succeed? Release it. Otherwise, goodbye.

and others tweaks. It can be found easy by just searching for “seba14″ on google.

In no other way was this a 1.0 release as that is generally understood.

The entire community knew about it, and endlessly bitched about it, and is STILL bitching about it. BitComet didn’t and doesn’t need to explain a thing about it. You should know, and if you don’t know then you don’t know much about bittorrent and should learn more before speaking.

The problem is that bittorrent piece boundaries have nothing to do with the file boundaries of the contents. Piece #27 contains the end of file #3 and the beginning of file #4, so if you just want file #4, this causes problems. The community has been griping about that for years.

This was an attempt to solve the problem by including a padding file that filled out the rest of piece #27, so that file #4 starts with piece #28 instead of in the middle of #27.

But the poor guys are damned if they do and damned if they don’t. SOMEbody will complain about it no matter what they do.

People who block all versions of a client will suffer on their end and hurt the swarm far more than a few hit & runners. How many fools use the Safe Peer plug-in that blocks µTorrent?

Azureus users like to cut themselves off. After Vuze was found to actually report the user’s activity I say let them cut us off.

I use both BitComet & µTorrent.