![]() ![]() *Then ticked some more files within this torrent to download and let it run, *I ran a torrent that downloads 70GB of data,ĭownloaded only part of the torrent because the torrent contains lots of files, You explain things very clearly.īy the way I might be having trouble here, to sum it all up here's what happened so far: TY for your answer in the other sub-forum. No, downloaded data is always hash-checked as each piece is completed. TIA Edited Octoby LovesTheSun (see edit history) Never experienced this with other torrents within this same version of BitComet I'm currently using. But I was just wondering why this happened. Chances are this will not occur again, I hope. It is still running and I'll report back when it does this again. But then the above mentioned thing happened. I ticked some more files within this torrent to be downloaded and let it run. I must include I've selectively downloaded part of this torrent at first. Why did BC do that? I use 1.22 stable release When it stopped the torrent reverted back to 96.8% and started downloading again. I assume BC was hash-checking all the files in the torrent. Last night when this torrent hit 100% my harddrive began rattling. I have a big torrent that has 70GB of data. It really shows there's been a great deal of work on both the client and the guide. It has very extensive features and detailed information regarding torrents. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |