However I think/proposing, that eMule add the ability to:
1. Force Check against a local file, when requested (much like "Force Recheck) (prompt for file to compare to.)
2. Force Check against current shares, to see if its currently sharing the file that it's trying to download from the network.
BUT:
A: The File Must be Complete.
My common use for the "force recheck" command on a torrent is when I get the file some other way for a torrent that's either slow, or not fully seeded. I Stop the Torrent, Replace the unfinished file, with my other_sourced file. Then do a "force recheck" to see if the other_source file is the correct one. (I can then also seed the complete file).
There is no Good equivalent in eMule. If you share the other_source file, you can then manual check the Hashes but that's very tedious. Also eMule will continue to download the file, not noticing that it is sharing the complete file, until you Download the entire file from the network which is wasteful. The only workable, solution I have is to use a Second PC, with the same edk links and have my normal eMule upload to it and download from it. But then I have all these copies, and It's not that simple to manage.
The File you are comparing against would have to be a complete file, because of the nature of edk links. The links only Store the complete file hash (most of the time) so there is not a way to see if you have good sub parts. This is why we don't see a torrent like "force recheck" command (As I understand it) (torrents do have hashes for each part). While it is possible to get sub-hashes, you must find at least one source on the network, and this was requested three years ago and has still not been implemented. This is a simpler will_always_work version, that I hopeful will get implemented in a much short time frame.
I would like to additional see an option to compete the download from the file, so that I get a file named the way the edk stipulates, and it go to the normal output directory. Just as if I had full downloaded the file off the network.
Checking against current shared files is another way to go. It at least saves from downloading a file you have. But as the collision is currently coded you lose the edk file name and its record in the transfers list, and the edk file name. I would rather have the check against file, or at least the current transfer record to not disappear.
Update:
For #1, yes you can share each file, read the hash, and then manually compare it to the the file your trying to get, but it very tedious to do for 50 files at a time
For #2, If your getting a file, and then you share out a complete version, eMule doesn't notice, you will still download the file, and Share it. Only when you complete the Download, does eMule notice.
::Neither of theses methods let you 'complete' the download. I.E. you don't get a file named as the edk link stipulates, in the directory you had setup for the download
This post has been edited by larek: 05 February 2013 - 08:28 PM