LimeWire 2.0 beta is finally here. This version includes all of the important important features of the earlier betas such as:

<ul>
<li>The introduction of UltraPeers to the network, a feature that will save everyone's bandwidth for downloading files and that makes the Gnutella network far more scalable than ever before.
<li>Swarm downloads, or the downloading of a single file from multiple hosts to speed up your download and maximize your bandwidth.
<li>The option to leave LimeWire running until all of your current uploads and downloads are complete, at which point it will automatically close.
<li>Dynamic allocation of upload slots to make as many files available to the network as possible.
<li>Much more accessible chat functionality, allowing you to communicate with other users on the network (which you can also disable).
<li>Many minor user interface changes to make LimeWire easier than ever to use.
</ul>

The new beta includes several additional improvements, such as:

<ul>
<li>More robust communication of UltraPeers so that you can immediately reconnect to another UltraPeer if you lose your UltraPeer connection.
<li>The search button is now disabled when you are not connected to the network, so all searches should return rich results.
</ul>

Let us know if anyone experiences problems or has suggestions. As always, thanks to everyone for their support and for their helpful criticisms.


---------------

Best,

The LimeWire Team

uhh damn, that was quick. I've been running LimeWire 1.9c since it came out, so thats been a day of uptime and I havnt had any problems yet. But anyways Adam were is the tgz for the ol' FreeBSD user you got here? :]

Yeah, we're getting a little crazy with the betas over here =). This one's getting close to the final release, though. You can get the tgz at:

http://www9.limewire.com/beta/2.0/li...eWireLinux.tgz

As usual, just ignore the references to "linux" in the path.

Thanks.

the ads-banner are now even clickable .

Its not dramatic but my connectivity to supernodes has gone up..I m now maxing up to 25-30 hosts through one superpeer. This is a good sign of things to come...Im assuming things will really start to take off in the next few months as it gets more distributed...Cant wait to see the whole network connected...I wonder how long that may take .....

Gnutella is getting a serious makeover!

Good Job Limewire team!

Oh BTW...the ads are nice...It makes the client more interesting to look at

Glad you guys like the new version so far -- I'm especially glad that you're seeing some nice, high connectivity with the UltraPeers, sweeppicker. Yeah, hopefully this will only increase when this is officially released. It looks like it's going to be spotlighted on download.com for all platforms, so that should give it a nice boost.

Let us know if anyone has any problems with it.

Yes this new version is really good...

And the features i don´t want to see...

you know them I don´t want to repeat them!

Morgwen

P.S.:

Missing an official statement about the new buy option!

can u resume downloads with this?

I have just tried to install 2.0.2 but am unable to complete the installation. I have JRE 1.3.1-02 installed on my computer. I get an error message as follows:

Error 1610. The configuration for this product is corrupt. Contact your support personnel.

I have a feeling that I will have to delete some entries from my registry. I was previously running version 1.7 but could not get it to respond. In "Add/Remove Programs", there was no reference to LimeWire. The uninstall application would not work. Then, through Explorer I removed the Limewire files. Also, I removed all references to Limewire in the registry. Probably, there are other entries in the registry that cannot be located by running Limewire under "Find".

Thanks for assistance.

Can anyone tell me or help me out as to why Limewire 2.0 flickers so badly and seems to stutter when switching back and forth between windows and even tabs on the interface. Running OS X 10.1.2 loads of Ram....Is there anything I can do to prevent this, did not have this issue while using 1.8.

Thanks.