The LimeWire 2.4.0 beta has just been made available at:

http://www.limewire.com/index.jsp/download_beta

This version includes dramatic performance enhancements, particularly for users who are sharing a lot of file. It also includes the following features:

<ul>
<li> new "add to wishlist" feature for searches that do not return results
<li> fixed bug where download would stall at 99% complete, automatically switching to faster uploaders when this situation occurs
<li> detects corrupt files when downloading from multiple host (by checking overlapping regions)
<li> connects to the network faster (using socket timeouts and increased parallelism)
<li> increased ultrapeer connectivity
<li> reduced bandwidth from requeries
<li> incomplete files are no longer deleted with certain expiry times
<li> new "about" menu lists contributors, including contributors from the open source project
<li> sends "Remote-IP" header when handshaking
<li> turns of uploads when in "shutdown after transfers" state
<li> vendor column in connection tab
<li> fixed issue on the Mac where using custom fonts could make the options window unusable
</ul>

Again, the performance improvements are really vital, and it will improve network performance significantly overall as more people migrate to 2.4.0.

We hope everyone likes it, and thank you all for your helpful feedback and comments. The performance bug that we fixed in 2.4.0 was identified by users on this forum as well as by one of our open source contributors -- we would not have noticed it without your help.

You are doing a wonderful job, but you MUST add checksum detection.

Connection are better, but I get "File Corrupted" on almost every MP3 I try to download (At about 5%).

That doesn't sound good and is very odd. We're working on changes that will add full-file hashing for all shared files on the network, making this operation much more robust and hopefully eliminating corrupt file messages.

The addition of the corrupt file messages is a good thing in some ways, however, because with the previous implementation the files would have been corrupted without you knowing about it.

Is anyone else seeing this? You are getting the message very consistently?

I've get a couple of 'File Corrupt' messages (Been using 2.4 for an hour or so).

It is nice to know how clean the copy is - but for movie files a couple of corrupt bits here and there usually aren't too important. I'd like the notification but would prefer to be asked what to do about it (Since this is just an interim solution before hashing, I won't ask for some guide as to /how/ corrupt the file is).

Alternatively, a nice easy way to resume the download (or even start over) would be useful.

Mark

Question for people who are getting the corrupted file bug: what OS are you using?

Thanks,
Christopher Rohrs

WinMe.

Is it a bug?

Win2000.

Mark

What percentage of downloads would you say are corrupted? How many did you try?

I don't know, I'd say 25%, and that ALL the "corrupted" files, are not really corrupted (I downloaded them with 2.3.0).
Maybe they do have some corrupted bytes, but that doesn't mean I can't listen to those mp3's, or watch those videos.