It never fails. You have just managed to download some 100 Megs worth of incomplete files when for what reason ever (maybe an interrupted connection or whatever), Limewire freezes, destroys downloads.dat and thus sends your incomplete files to Nirvana. The next time you run Limewire, the downloads screen is as white as a polar bear in a blizzard.

As far as I am concerned, I do nor wish to spend my short life moving incomplete files to the trash and restart downloading them over and over again. Sorry, but after several weeks of this, i am more than a little bit pissed about LW and just because MAc users do not have access to Shareaza doesnt mean we have to deal with such inferior trash! (Ooops, but now I feel better)


There are four solutions to this problem:

(1) An automatic backup of downloads.dat every so-and-so minutes,

(2) Enable Limewire to work with "mutilated" downloads.dat files,

(3) Tag download information to the file itself and thus make it resumable on its own,

(4) look for a gnutella client that actually works.

75% of these solutions are up to the developers, 25% are at the user's choice.
We'll see what solution will surface.

Still pissed,

N:A:

I'm sure you will be ecstatic* to learn that the new LimeWire beta (2.7.0) includes the ability to force incomplete downloads (as shown in the library) to resume.

I've only just got this and I'm still playing...

I think the resume will resume from zero - if the downloads.dat file is corrupt then LimeWire has no way of knowing which bits of a file have been downloaded.

But this does save having to search for the files you were downloading and starting them manually.

Mark

*It certainly pleased me a great deal.

also fyi -- if you close and restart limewire, the downloads generally show as '0%'. unfortunately this is because the progress is currently only set when a file is downloading or corrupted. this does not mean that the file is actually 0% -- the best way to test is to try and launch the file -- if it launches, there's some hidden progress. this will be fixed in a future version (along with some other nifty features).