Hello Everyone,

As a file is being downloaded, due to various causes (upload host crash, power failure) the last few KB downloaded will get corrupted. When this happens it assures this file will not be resumable. Gnucleus compares the last few bytes of your previously downloaded file with the first few bytes of the incoming file, making sure they match exactly, thus assuring it is the exact same file being downloaded and no corruption has occured during the disconnection. Obviously, if the last few KB of your file is corrupted it will not match the new uncorrupted incoming file and the transfer will be cancelled. If you have ever had the "Extended Info" window open and seen "Remote File Corrupted", chances are, it's your file that is corrupted and not the "remote file". This is not always the case however, it could be totally different file that fits your keywords, and happens to have the same byte size.

If you think you have one of these corrupted non-resumable files, I have found a freeware app. that allows you to "tear" the last few KB off the end of your file, leaving you with a file that is resumable again (but a bit smaller). I have tried it, it works. Make sure you tear off the end of your file and not tear a chunk out of the middle. Use Explorer on your file to right click=> properties and get the byte size of your file to determine where and how much to tear off.

Download "Japos Tear File" at http://www.japos.com/

Swabby, would it be possible to have Gnucleus show us an exact byte size in searches, instead of just KB. Is this info not available until a download is actually started? With this info wouldn't it be possible for us to create 0 byte resumable files using "File Name (size in bytes,keywords ext).ext"?