Hi,
I’m sorry for not replying sooner to your post, it gets very busy here, and its easy to miss a question.
Regarding private trackers. It is the tracker that has to approve what clients can be used. Since some very old versions of bitcomet have an issue with allowing dht even if the torrent doesn’t allow it, many tracker have restricted bit comet to only allow newer versions. It is possible that this tracker has only allowed certain specific versions.
You would have to contact them to resolve this.
Regarding rubbish data, this could be cause by connection errors. If a piece of data is changed in any way when downloaded, it will be hash checked, and discarded as rubbish if it fails.
This is normal.
If you have a large amount of rubbish data, then it could be your internet connection has a problem. If it happens only in small amounts, from time to time, then it is likely other peers problem, not yours.
Regarding disabling files. If you disable a file before it is finished, you are likely to lose all current progress.
As for the status changing to not complete, even though the file is all there, this is because some of the torrent pieces are spanning more then one file, so when you enable downloading of an additional file, all pieces that file needs are scanned for level of completion, Because only part of some of the pieces are present, the status of these files changes.
I don’t know how to make this clearer.
I will attempt to simplify it…
Imagine a torrent with two files, This torrent is distributed in three pieces.
file one, file two
piece one, piece two, piece three
If you select only “file one”, then the client will download piece one, and piece two, then discard half of piece two.
You then select file two, but since you already discarded half of piece two, your client has to mark it as NOT downloaded, and then download piece two, and piece three.
This will result in file one reading about 66% complete, eventhough it is all there.
Basically, you are altering or “cheating” on the rules that bit torrent uses, which is far less efficient and wastes resources.
The only way to avoid this would be to design the torrent to be used that way,which would involve an EXTREMELY complex torrent creating program.
I do have one suggestion, if you want to divide a torrent into two halves, then you could download half, fully seed that half, then remove the torrent from your client, move the completed files to a different location, then restart the torrent, and download the other half.
This would still be inefficient, and require longer download time then doing it all at once, but would avoid completed files from being overwritten with incomplete data.
It is still the best option to download a torrent the way it is designed.
Suspect
)?