If this problem won't be fixed soon, I'll stop using LimeWire forever, and will tell everybody I know that LimeWire is the worst Gnutella client ever made!!!!!!!!!

How is it possible:

I downloaded a song, Killed it, found the EXACT same file, with the EXACT same name and the SAME size, and I know it for sure because when I clicked "Download Any", I checked the incomplete folder and there was no file added, it just started rewriting it from the beginning! I had 3500/4000 KB already downloaded, but this damn program just started rewriting it!!! I noticed this problem a LONG time ago and I hoped that the developers would actually do something about it soon, but me (and all the other users. for more info go to "Download\Upload problems" forum, and select "Resuming downloads") still have the problem!!!

I like LimeWire, I like it's design, it's feautures (especially Ultrapeers), I like the search results, I like the download speed, but I have a dial-up connection, and if I download something big (I once download 100+ MB file, and my connection droped at 50MB completed, and LimeWire just started rewriting it!!).!!!!!!!!

you really should fix this problem. i remember it existed in v1.2 already, and smart downloading hasn't improved since then (i can't tell if it has improved by swarming because modem users cannot swarm). i hope that along with HUGE in the coming releases you would make the whole researching / resuming / swarming mechanism more robust and reliable. lime is *by far* outperformed on this matter by phex and gnucleus.

post script: could you add an option to hide the internal player ?

I'm not really sure on this in the terms of gnutella but as much as I know about resuming files in anyway the counterpart (the node you're downloading from) must also support that feature!
because it has to start transmission somewhere in the middle of the file. if it does not support this it will start at the begining.

as far as i know i had my first 2 source download today and it was pretty cool. unfortunately did one source quit the transfer and i was therefor stuck at 10% with the slower source. i just looked at my search results found the only possible 2nd source on it again. then i killed the slow download and started from the other source. it resumed back at 50%. i know it does not always work but as i said it has to be the exact same file and the other node has to support it to.

regards.

OK, but it rarely happens with other clients, did you read the thread at "Download\Upload Problems"?