We've released both the free and the pro versions of LimeWire 2.6.0 beta. It's available at:

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

This version includes the following:

- now connects to the network using GWebCache, a distributed connection system
- includes more statistics, such as showing the number of replies sent for files, the number of uploads for files, the number of alternate locations for files, and the user agent for uploads
- on Windows, we wrote a LimeWire exe launcher that dynamically searches for the most recent JVM available on your system each time you run it -- you will no longer have to re-install LimeWire when you install a new version of Java
- many important bug fixes, particularly to uploads and the installers
- LimeWire is now available in many new languages, including Italian, Catalan, Portuguese, Brazilian Portuguese, simplified Chinese, and Swedish


We're also working on several really important projects for future releases, such as upload queuing and a new searching system that will improve overall search performance by several orders of magnitude.

Hope you all enjoy it!

The requested URL /beta/2.6.0/LimeWireOSX.sit was not found on this server.

Same here

Thanks guys -- it's all set now. The new installer is called "LimeWireOSX.zip" instead of "LimeWireOSX.sit."

Works ok. When I opened it though, it tries to get me to DL 2.5.5 because it is the "newer" version. Odd.

Thanks for the news Adam...

I'm on my way to download & install 2.6.0 Pro now!

I just fixed the update servlet to not report an update available for 2.6.0.

Thanks.

LimeWire uses now 2-3 times more cpu cycles on mac osx 10.2 than 2.5.5- which is bad. I restarted it but same results... probably a bug somewhere...
Another thing, at first launch the mp3 player buttons were aqua like, after a restart those buttons are the same as 2.5.5, weird.

more if needed later...

Remember that the first time you run the program, it will hash all files in your shared directory that it does not already have a hash for. Did you choose a new save directory and move files to it??

My bad. I knew I should have mentionned that all files had been hashed before my experiments.... anyway there is a cpu cycles problem on my computer. Next time I'll try to be more clear.
Thanks