We are having a bad time with a glitch in LimeWire. When a download completes and the ‘Verifying file content’ routine starts, should the connection fall out - the file verification stops and the percentage at which it ended the process is then the point at which LimeWire restarts the download. For example if the connection drops out at 97% LimeWire restarts the download at 97%. In actuality the complete download is there and only file verification needs to be restarted!

The problem is that this has been happening over and over, so some files do not ever complete!

Into the mix, my significant other found some individuals in a chat room post that they were f*****g with scabs on LimeWire, by waiting until the downloads were at 99%, then closing the program twice. They stated this would cause an error and the scab would have the file download reset causing an irritating delay! (When asked why they did this this, the response was they liked Kazaa and didn’t like that LimeWire users didn’t have to put up with ads and spyware that they have to continually deal with!)

I wish file sharer’s on LimeWire could be made less of a target as a result of this...

LimeWire will redownload files after verifying if it detects that a part of the file was corrupt. Verification will only begin after LimeWire has downloaded 100% of the file. After verification, LimeWire will either proceed to save the file or redownload the parts that were corrupt. LimeWire will attempt to recover from corruption up to 6 times before giving up and just leaving the file as corrupt.

A future version will change this so that verification takes place as the download is happening.

Those folks in the chatroom are just trying to annoy people -- dropping off the download when it's 99% or so does nothing other than annoy people who can't get that last 1%.

Ah, makes sence the juviniles were probobly responding to my girl's earlier LimeWire post.

Thanks for explaining about the restarts caused by file corruption!