Hi everyone. Many people are complaining about problems with resumed downloads. Indeed, there are a number of cases where 2.0-2.2 code can fail to resume properly. The new LimeWire 2.3.0 beta should fix these problems. Do try it out and let us know if it does the trick for you. Please be aware that this is still a beta. We know of two platform-specific bugs that still need fixing. Here is <a href="http://www.gnutellaforums.com/showthread.php?s=&threadid=9368">more information</a>.

Sincerely,
Christopher Rohrs
LimeWire

YAY!!!!!
THANK YOU, THANK YOU, THANK YOU!!!!!

Thanks a million...much better

The beta version does seem to work better for actually resuming the downloads but they start over from 0% rather than from where the file download left off when the connection was broken.

Any ideas?

I am using 2.3 - I have tons of 100 - 500 mg files in the incomplete folder with no apparrant way to resume download? They are not auto-resuming as is clearly states in the user guide.

Is something else required of me? I would pay the $8.50 and go PRO if there was some indication that a full featured product could be offered here.

However, it seems that as poor as other gnutella client interfaces are - at least many of them have much better RESUME features.

Somebody is going to figure this ALL out soon, put it all together and CONTROL this market.

LimeWire 2.3 may not be able to resume incomplete files created by older versions. The older versions sometimes failed to write enough information into your downloads.dat file.

BTW, there is an option to have LimeWire automatically delete old incomplete files: Tools->Options->Saving->Incomplete Files

Resumes seem to work better, but LimeWire still doesn't continue to download files with different names (even if that's the same file), and the requery doesn't work well, it can find a file, and download it from 0% (even if I had 99% of the original).

LimeWire can't resume a file with a different name. In other words, if you have 50% of "file one.txt" in your incomplete directory, LimeWire won't be able to tell that "file two.txt" is the same thing. In the future it may using SHA1 hashes, but for now it will start "file two.txt" from scratch.

And what if I'll rename file one.txt to file two.txt? Will it work?
And if LimeWire doensn't use HASH then why do I get different file names mixed in the same group when I search? And why doesn't the requery search for files with the same name?

Unfortunately renaming a file won't work because the state of the file is stored in downloads.dat. That file isn't easily edited.

The result grouping in the GUI is approximate; it tries to groups files that are similar but not necessarily the same, e.g., "File 1.txt" (100 KB) and "FILE 1.txt" (101 KB). LimeWire won't swarm from both files, but it will try them one after the other.

The autorequery feature "canonicalizes" the file name before requerying, i.e., it extracts the most relevant keywords. Any results matching exactly incomplete files will be resumed. Other results may be downloaded anyway.