I just installed LW 2.0.2 under linux (using Sun jre 1.3.1) and i found that something strange is going on when resuming files. I had a bunch of incomplete download froom my previous installation of LW 1.8, when i find the file and click on it for downloading it again it can happen one of the following things
1) resumes the file (perfect behaviour)
2) starts downloading a new file cos of a a difference in the name (this should really be fixed! who cares about the name when the checksum is the same?)
3) overwrite the file restarting it from scratch (this just happened once but i lost 80MB of download )
4) start downloading from scratch the file *without* setting its length to zero... that means that he simmply re-writes the file and when u get to the end continue downloading the part that was missing before
I hope to have been clear.
Can anyone please explain to me what causes these (erratic imho) different behaviours?
thanks

I get the same thin on Mac OS 9.2. 90% of the time, it starts over from scratch, and does not update the "Incomplete" files in the Library

Same here, it used to resume fine until I downloaded 2.0.

Resume doesn't seem to work at all with anything above 1.8c. If I have an incomplete transfer with 2.0+ I have to load 1.8c so I can resume. 2.0+ will overwrite the file from the beginning even if the checksum is the same in the Incomplete folder.

with 2.1 i just keep pushing 'force resume' ,then i scratch my head,
then a 4 letter word comes outta my mouth,then i realize i've wasted
the last 2 hours........nothing at all happens.

Same problem here, running RedHat 7.2, slightly modified 2.4.7-10 kernel, ext3 fs, LimeWire 2.1.1.

The behaviour seems erratic here too; I've been trying, unsuccessfully, to find a pattern. The most common scenario is that an attempted resume will ignore the incomplete file and start over, this time storing the new download *nowhere at all*. When the new download is "done", it copies the *old* incomplete file over to the shared directory. So I'm left with an incomplete file even though I waited for the full download to complete the second time around.

Another common scenario seems to be that the resume fails and the download restarts from 0%, but when the new download reaches the size of the incomplete file, it starts adding to the end of it. Better than the scenario described above, because you actually get a complete file in the end, but still not good.

This isn't listed in the "known bugs" is there a work around for this.

Where the hell are you?

I am getting the same absolute aggravating behavior in
2.1.1. This happens even when I am downloading from
the SAME JERK that keeps interrupting the download.
It most often happens when the other end kills the download.
You then get a totally dead connection and have to kill it
yourself later. If you do the kill, it will not resume where it
left off. This has happened to me repeatedly in downloading
large mpegs. It is truly aggravating as heck.