I keep running into the problem that if I quit Limewire with downloads in progress, the next time I open Limewire, they are no longer in my download window. Does anyone know how to avoid this, or some other way to redownload something in your incomplete folder?

the newest version fixes that bug.

Which version would you suggest????????????????????

You can't be suggesting LW 2.3.3 can you?
Because LW 2.3.3 Pro don't do dat for me!

I have the new version, and as the last person stated, it's not fixing it....any ideas for the second part of the question....is there a way to redownload from the library page from your incomplete folder?

The bug was fixed in LimeWire 2.3.

I know it's working on Linux and Windows now. The file, that is used to save the downloads, downloads.dat is saved when you close LimeWire and when you add / kill downloads.

If you are having trouble, check if LimeWire can save to your downloads.dat file (located in your Incomplete - directory). Check file permissions, etc.

Great for the PeeCee crowd...
What about the Mac? Does it work for me?

NOT

Hey, you can install Linux on your Mac!

Did you check if the downloads.dat was written?

yes,
been there,
done that,
"Downloads.Dats" is written.

And, either NO resumed downloads with LW 2.3.3 Pro,
or, if they do resume,
they begin at 0% regardless of the previous (incompleted) file size.

lots of fun when on a dial-up, trying a 10Mg file and reaching 95% complete
only to have LW 2.3.3 go back to 0%

Do the downloads to resume appear in your downloads-panel after you started LimeWire?

If that's the case a possible explanation could be, that you downloaded a grouped search result and LimeWire now resumes a similar file with a slightly different filename. If that's the case, the download will start from 0% again and it will create a new temporary file. This is a defect, indeed, and the LimeWire-team is trying to solve it by implementing another addition Gnutella protocol, the HUGE proposal, which will allow to identify similar files with different file names securely.

So far, I don't think it's an MacOS-specific bug, since the methods used to write and read the file are working with JRE 1.1.8.

I do tend to go after a "grouped" file
as the odds of finding one of them with an available download slot are much better,
However, the problem also occurrs with a single download host request (download all).

My recollections are, that (with ANY- LW 2.x.x)
when the incomplete (resuming) download appearrs in the LW download window after a restart,
the host address is the same as the original attempt, and,
although I do nothing,
the incomplete download appears in the download window
and resumes at 0% regardless of the % I reached in the previous session.

This problem does not happen in my LW 1.7,
LW 1.7 usually completes incomplete downloads as long as the original host is (still) available.