quanzaboy

So why did it appear when I launched BitComet if I'm using the english version? I think I might have stumbled on a bug here, so you might wanna pass that along to the developers...

I added a torrent to my BitComet today, and when it opened I saw this weird Chinese menu to the right of the "Help" menu that I've never seen before... What the h*** is that thing!? When I restarted BitComet, it disappeared just as strangely as it appeared... Anyone??

Thank you bitdave, I reverted back to version 0.70, and it seems to be working normally now...

Does anyone else have an explanation??

Have you tried the download with any other clients? That may clear up whether it's a file issue or a client issue...

Well yeah, that's what I thought too, but then why doesn't BitComet register it as "rubbish data"!? Because usually it does..

I've been using BitComet for a while now, and I've never experienced this strange problem... I'm downloading a file, and the download speed is around 170-180 Kb/s. However, the file itself is progressing at a significantly slower rate, since the remaining time indicator is around 30 minutes for over 2 hours now. The strange thing is that in the file info, the total amount of downloaded data is 930Mb (without "rubbish data"), even though the file itself is just 350Mb (see image below)! The download is continuing to progress at a high rate, constantly increasing the total amount of data downloaded, but the file progress itself is barely moving. Here's the info as it appears on BitComet: Any ideas? :mellow:

You probably have a partial download, as seems to be the issue with BitComet and AVI files... I had the same problem too, check out my post here: http://forums.bitcomet.com/index.php?showtopic=2824

chainsore, I'm guessing you're slightly retarded, so just to explain: If you don't wanna use winrar that's nobody's problem but yours. In megaupload.com, on the top right corner you should see a validation field with some letters you need to enter into it, and a "downlaod" button.. enter the letters, press the button. Not too complicated is it? Edit: by moderator although I know you are trying to help, I will not allow being rude to members, so this stops here

I do all the above on a regular basis anyway, so that has nothing to do with it, especially considering that I never had any problems other than with BitComet... thanks for the suggestions anyway! The final hash check does seem to be necessary, since it makes sure the finished downlaod is the same as the original's supposed to be.. fact of the matter is that when i did a manual hash then it discovered there were missing pieces, so if it does that automatically it will prevent such problems in the future. As for the data loss i'm sure it's something to do with the program.

Ok fine, I figured it out.. Re-Added the torrents, closed bit commet. Swapped the partially finished AVI's with the .bc! files, re-opened the client, did a manual hash check, resumed, and allowed the remaining 2-3% to complete. Also checked the option "Hash-check again when downlaod task is finished".. But surely this was all unnecessary.. I mean surely the hash check at the end should be on by default, saving users time figuring out this problem in the first place... Anyway, works now.. will keep using it!

I've just noticed a significant problem with BitComet, one that I have never experienced with any other P2P client!! I successfully downloaded a couple of AVI files using BitComet (or so I thought...) BUT!!! When I proceeded to open the downloaded files I discovered that whole segments were missing.. i.e One of the files kept skipping throughout the entire playback, while the other just ended half way through (no doubt the gap was too big to play).. I mean, I don't want to slagg anyone off, but with all due respect what the h*** kind of client did you guys build that doesn't check the integrity of video files after download?!?!?! I mean now I have to download these files all over again via DC++ or something.. which I could have done in the first place and gotten them right! Is there a workaround around this problem, or should I just stop using BitComet altogether?