Hi!
I think I just found a bug: I use amule and emule witht the same temp/incoming folders, so they can continue each other's work. Whn I switch from amule to emule, or viceversa, the files will always appear as "possibly corrupted" and either amule or emule will perform a rehash. Problem is, when emule completes a file, and I start amule, it will notify about the new file (on the incoming folder) and will rehash it, but it will not perform a rehash of the .part files (even though it states that the files are possibly corrupted). Hope this information was enough.
Regards.
Edit: Sorry, I think I overlooked. It seems the fiels are indeed rehashed, but just the files that are rehashed are all zero size (been paused all the time) so the rehash took almost no time. Now the next question would be: why it didn't detect any of the big files (i.e. have downloaded something) as corrupted? I have never understood the mechanism amule uses to know if a file is "possibly corrupted" or not.
