LimeWire 2.5.0 beta is here!
 

The beta for LimeWire 2.5.0 is now available. The free version is available from: http://www.limewire.com/index.jsp/download_beta and a pro version is also available from your pro download page (for pro users only).<p>

The new beta includes several exciting new features and some "under-the-hood" improvements that will improve Gnutella significantly moving forward. The new additions include:

<ul>
<li> "Browse Host" is back by popular demand. If you're unfamiliar with this feature, it allows you to see all of the shared files on another user's machine, making sharing more convenient if you have similar interests. As more people upgrade, this version will work much better than the previous browse host implementation.</li>
<li> Parallel connect on downloads, meaning that you will connect to and start swarming from multiple hosts as soon as you start to download from a group, allowing you to get your download more quickly.</li>
<li> Full support for the "Hash/Urn Gnutella Extension (HUGE)", which assigns each file a unique "hash" and intelligently stores alternate locations for files on the network. If someone uploads a file from you, for example, you will store that computer as an "alternate location" for the file, and send that location to others when they download from you. This all makes downloading more robust and could reduce message traffic over time. It's also a first step towards a "Content Addressable Network (CAN)", one of the ephemeral goals of the Internet for some time.</li>
<li> Bitzi metadata lookup allows you to get more information about files -- right click in the search and library tabs to try it!.</li>
<li> German and French versions available -- thanks to Phillipe Verdy for all of his hard work on this.</li>
<li> The downloader now checks for corrupt files by looking at overlapping regions. </li>
<li> Loads shared files much faster on startup (though the first time may be a little slow).</li>
<li> Connects to the network more robustly.</li>
<li> Installer improvements to save your setting across installs, to correctly pick up the latest Java 1.4 and use it when it's available, fewer 1608 errors, etc.</li>
<li> Full support for HTTP HEAD requests. </li>
<li> Throttles outgoing bandwidth for ultrapeers.</li>
<li> Finally, LimeWire Basic will share the installer by default, even to web browsers (currently Windows-only).</li>
</ul>

So, as you can see, there's a lot of new additions. In fact, the code has changed so much that we really need users to help test it as thoroughly as possible. We've run it through our usual onslaught of tests here, but some always slip through. If you have the time to hammer away at it, we'll be forever grateful.

We hope you enjoy LimeWire 2.5.0.

Best,

The LimeWire Team

LANUCH ERROR ON MAC OS X
 

WON'T LAUNCH.....Aww man..this stinks


heres the error I get:



LimeWire version 2.5.0
Java version 1.3.1 from Apple Computer, Inc.
Mac OS X v. 10.1.5 on ppc
Free/total memory: 451576/2879488

java.lang.ExceptionInInitializerError: java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key SEARCH_PUBLIC_BITZI_LOOKUP_STRING
at java.util.ResourceBundle.getObject(ResourceBundle. java:382)
at java.util.ResourceBundle.getString(ResourceBundle. java:354)
at com.limegroup.gnutella.gui.ResourceManager.getStri ngResource(Unknown Source)
at com.limegroup.gnutella.gui.GUIMediator.getStringRe source(Unknown Source)
at com.limegroup.gnutella.gui.search.SearchMediator.< clinit>(Unknown Source)
at com.limegroup.gnutella.gui.MainFrame.<init>(Unknow n Source)
at com.limegroup.gnutella.gui.GUIMediator.<init>(Unkn own Source)
at com.limegroup.gnutella.gui.GUIMediator.instance(Un known Source)
at com.limegroup.gnutella.gui.Initializer.initialize( Unknown Source)
at com.limegroup.gnutella.gui.Main.main(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at RunLime.main(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.zerog.lax.LAX.launch(Unknown Source)
at com.zerog.lax.LAX.main(Unknown Source)
at java.lang.reflect.Method.invoke(Native Method)
at com.apple.buckyball.app.LaunchRunner.run(LaunchRun ner.java:82)
at com.apple.buckyball.app.LaunchRunner.callMain(Laun chRunner.java:44)
at com.apple.buckyball.app.CarbonLibApp.main(CarbonLi bApp.java:76)

I don't know if this applies.... I had to completely uninstall 2.4.4 (Pro) before 2.5 (Pro) would install correctly - I realize we are on different platforms (Windoze 2k here) but this might be a plan of attack if you haven't tried it yet. I had tried the public beta with the same results.

Re: LANUCH ERROR ON MAC OS X
 

Your MessagesBundle.properties file located somewhere in your LimeWire directory is missing a line. I guess it was some problem during installation of LimeWire beta. Try removing LimeWire and reinstall it.

Looks good. Keep up the good work.

upload bug
 

1.
it happens often that a downloader is taking 2 uploads slots for the same file, one is active, the other sit at 0k/s, could Limewire be wise enough to not allow two uploads of the same file to the same downloader at the same time by killing the first used, now inactive slot??? This would mean more slots available on the Gnet and more downloads. Also, for those that limit the upload bandwidth like me the speed of the other uploads would be faster.

2.
another thig for uploads, when I specify the upload bandwidth to 15,31k/s, that bandwidth isn't used at capacity when there are more than 1 uploads. Would it be possible using something better than ie: two uploads, so the max speed of each is 7,8k/s even if one is taken by a modem user and is not reaching that 7,8k/s.

Hope you improve those things for the benefit of Gnet

Keep up coding!!!

I recieved the following error on launch twice during the first time I opened it, but it hasn't happened since. Clicking OK allowed the launch to continue
_________________________

LimeWire version 2.5.0
Java version 1.4.0 from Sun Microsystems Inc.
Windows XP v. 5.1 on x86
Free/total memory: 647552/6467584

java.lang.ArrayIndexOutOfBoundsException
at java.lang.System.arraycopy(Native Method)
at java.util.Vector.insertElementAt(Unknown Source)
at javax.swing.tree.DefaultMutableTreeNode.insert(Unk nown Source)
at javax.swing.tree.DefaultTreeModel.insertNodeInto(U nknown Source)
at com.limegroup.gnutella.gui.library.LibraryTree.add SharedDirectory(Unknown Source)
at com.limegroup.gnutella.gui.library.LibraryMediator .addSharedDirectory(Unknown Source)
at com.limegroup.gnutella.gui.VisualConnectionCallbac k$1.run(Unknown Source)
at java.awt.event.InvocationEvent.dispatch(Unknown Source)
at java.awt.EventQueue.dispatchEvent(Unknown Source)
at java.awt.EventDispatchThread.pumpOneEventForHierar chy(Unknown Source)
at java.awt.EventDispatchThread.pumpEventsForHierarch y(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
at java.awt.EventDispatchThread.run(Unknown Source)
-- listing properties --
MAX_UPLOADS=6
INSTALLED=true
DIRECTORIES_TO_SEARCH_FOR_FILES=C:\My Documents\Music Files
DIRECTORY_FOR_SAVING_FILES=C:\My Documents\Music Files
SAVE_DEFAULT=C:\My Documents\Music Files
JAR_NAME=LimeWire.jar
MAX_SIM_DOWNLOAD=8
CONNECTION_SPEED=350
_________________________

Other than that . .

1. Why is browse host always greyed out? This is when right clicking both single-host files and multi-host files.

2. I think that files should appear in the Library before they're hashed, it confused me as to why there was nothing in there until a file appeared (which was 50mb and took a while to show up).

3. The sorting bars still don't stay in their width/position in the downloads, uploads, connections and the library sections after the program restarts. Only the search's sorting bars get saved.
___________________________________________
| Name | Size | Status | Chat | Progress | Speed | <- These Bars

4. The stats box should contain a warning about its falseness.

5. Responsiveness seems a lot better overall, especially while recieving lots of results.

6. I hate to say it but a filter for the Morpheus 1.8.1 ultrapeers is becoming neccesary. Using the same search, it took six Morpheus 1.8.1 Ultrapeers to give the same results as one LimeWire 2.4.4 + one Bearshare 4.0.0 client. Six Morpheus 1.9.1 Ultrapeers yielded better results, but still below average, likely due to being connected to more 1.8.1 clients.

7. That parallel download thing is a huge help with the speed.

8. I'll think of more later . . . Great work! :)

Thanks to everyone for the feedback. I'm in the process of building a 2.5.1 beta based on this feedback, some other stack traces, and some catches by some of the LimeWire open source developers. The new version fixes the missing resource message that is likely disabling the current beta for almost all non-Windows users, unfortunately. It also fixes the problem with browse host always being greyed-out -- somehow the code to dynamically enable/disable it never made it in yesterday.

On the displaying files before they're hashed issue, we've gone back and forth on that a couple of times, even in the code itself. I think we'll keep it this way for now, as it's only an issue the first time LimeWire is started, although we may change it in future.

As far as preverving the position of tables, we actually have an open source developer working on a generalized way to accomplish this task, including turning columns on and off in all tables.

Morpheus UltraPeers -- we've done some statistical analysis of query results coming back from LimeWire UltraPeers in comparison with Morpheus UltraPeers, as we were concerned about precisely the same issue. To our surprise, the Morpheus UltraPeers actually returned more results on average than the LimeWires, although it's always possible that the tested nodes had an atypical network structure as far as the files available. We can run those tests again.

On the duplicate uploads, we'll look into that. It sounds like another client is being sneaky. We'll also look into the issue of maximizing bandwidth when throttling.

The Pro beta is up now, and I'm uploading the free version as we speak.

Thanks again. As always, any feedback on 2.5.1 beta is much appreciated.

That last post was from me -- I didn't realize that I wasn't logged in.

-- 2.5.1 --
 

I assume the 'browse host' feature will only work with other hosts running 2.5.x as I have yet to encounter a host I could browse. - If I am mistaken, can you clarify what conditions must exist that would enable this feature... and THANKS for 2.5.1 ... it is working quite well.... and for whatever reason I seem to be getting much greater numbers of results on my searches :D

Win 2k / 2.5.1 Pro Beta

german translation
 

Sorry to say, but the german translation has babblefish quality. Germans do speak english, and it is harder for them to understand this translation than the original english version.

You think so? I find the German translation (though it uses a couple of rather uncommon terms) quite okay. One of the problems is, that for some of the english words that are used e.g. for buttons there is not really a good German equivalent.

No problems so far but i haven't been able to download any files because i'm connected to morpheus ultrapeers and they aren't sending back any results even for common files :-(

is anything being done about this problem?

LimeWire 2.5.2 and Browse Host
 

I've just downloaded and installed LimeWire 2.5.2. I'm still unable to brows any hosts? Are there special requirements for brows host?

what is the difference with LW regular and the beta version?

I have been upgrading the 2.5.x betas since your first post. I moved from 2.4.4 to 2.5.0 etc.... upon upgrading to 2.5.2 from 2.5.1 all of my local settings and filters were apparently blown away

I am running JRE 1.41 on Windows 2K / PRO versions of the Beta

"Möchtest du das LimeWire dein hartes Laufwerk schnell auf andere Mediadateien durchsuchtt" ;)

I've been trying to download the latest beta from my LimeWire Pro page and every time it starts to install I get some error about a corrupted data.cab file and it won't install. I've redownloaded it several times and keep getting the same error.

Also, ich habe schon ein hartes Laufwerk...


okay, maybe the translation is not that good after all. (I have to admit that I don't look very closely at most of the screens anymore.)

2.5.2
 

2.5.2 doesn't remember prefs when installed over preceeding beta version and the audio search by metadata is absent. This is on osx and in French.

:D

browse host
 

Yes, you need to encounter another LimeWire 2.5 or later to use the "browse host" feature. For now, this is unlikely, but that will change soon.

upload suggestions
 

et voila: thanks for the upload suggestions. Those are all on our TODO list, actually, though they're not the highest priority now.

German version
 

Our German translation can be found at http://gui.limewire.org/source/brows..._de.properties
Any suggestions would be most welcome!

Instead of "dein hartes Laufwerk", should we say "deine Festplatte"? Just guessing--I didn't do the translation.

-Chris

PS: all those previous messages were from me. Forgot to log in.

German version
 

Darnit, NOW I'm logged in.

Re: German version
 

Yes,

a German never would say "dein hartes Laufwerk", this is the exact English translation but we say "deine Festplatte" (fixed disc)!

Morgwen

or you could say 'deine hartes scheibe' (hard disk) :D

let's sprachen Deunglish!

2.5.2 Beta
 

Found browse hosts feature (right click on search section name field) listed under Bitzi Web Lookup all grayed out though... Also Biti Web Lookup did not work :(
Glad that 2.5.2 now installs with 1.4.01 Java.. That's great
Loading up 3000 files takes a very long time. Not as fast as 2.4.4 Pro. Kaaza client; however, seems to have a better search engine I get more hits.

Thanks for your support.

2.5.2 Pro Beta User

An earlier response from someone stated the the 'browse host' feature would only work with 2.5.x Limewire hosts... so that will probably take a while to proliferate . . .

Yes but only if you want that the German people laugh. :)

Morgwen

slow file loading
 

The file loading (hashing) is intentionally throttled to avoid using all the CPU. Hashes are cached, however, so the second load should be really fast--much faster than previous versions of LimeWire.

2.5.3 beta now available
 

The LimeWire 2.5.3 beta is now available at http://www.limewire.com/index.jsp/download_beta. PRO users can download it from their personal download page. We now have French and German versions available online, so any feedback on translations is welcome.

2.5.3 is virtually identical to 2.5.2 except for a few minor bugfixes:

• Fixed installer to avoid PUBLIC_SEARCH_BITZI_LOOKUP problems if installing over previous versions.
• Fixed tgz and zip installers to include RunLime.jar
• Fixed NullPointerException and IndexOutOfBoundsException problems
• More robust behavior if can't write incomplete download files.
• Replaced "hartes Laufwerk" with "Festplatte" in German translation. :-)

As always, thanks for helping!

-Christopher Rohrs

Re: 2.5.3 beta now available
 

I would suggest to translate the license agreement. I couldn´t check the prog itself because I got a bug report and it switched to English...

I mailed the report to your mentioned address...

Morgwen

Is there any law that says that German people shouldn't be made to laugh? :p


Oops! I'm making off-topic posts in an already long thread. I deserve to be flamed! Any trolls out there who'd care to take a shot? ;)

Connections not remembered
 

Hey I know this is not a top priority thing but ever since you limited the number of connections i want to the network it will not remember how many each time I start up. I have a T1 line set up and I use 10 connections everytime but I have to type it in because the default is always 2 or 3. Even though it sais 10, I have to retype the 10 to get it to actually connect to 10.

Agian this is not big deal but can you guys maybe have it remember my prefrences as far as how many connections I want. Since your on a Beta run it would not be that much to add it in the next beta.

Thanks.

LW version 2.5.3 Beta Pro

I have to agree with Zerics, the number of connections should stay the same throughout every shutdown, otherwise its just annoying. ( Crosses fingers for having this in 2.5.4 (Final???))

Been running Limewire 2.5.3 on Mac OS 9.2.2 for the last few days. It looks pretty stable and resumes well. No resumed downloads have started over from 0 like they used to. I tried repeatedly killing and re-requesting files (sometimes with different names or from alternative hosts) with no problems. So it looks like the HUGE implementation has kicked in nicely.

People are downloading from me like mad, even though I'm on 56k, so my files are obviously visible on the net - perhaps more so than before.

Like others, I still haven't found any other 2.5ers to try Browse Host. But I'm sure they'll appear.

A minor bug: I've noticed up to four occurences of the same file being uploaded by the same IP (ie. four identical readings occupying four upload slots). I don't know whether this would be due to LW or the downloading client. I had never seen this before. I have since reduced the max-upload-slots-per-IP to one, so this no longer occurs.

Another small issue is that some downloads keep stopping:
They stop (requery), instantly restart when I re-request them (kill and double click on the search result) then stop again a few seconds later. You would expect downloads to stop because the host is no longer available or because it has used up all of its bandwidth - in which case it wouldn't restart immediately. Odd. If it's a small file then I might sit there re-requesting it each time this happens until the d/l is complete. I suppose the owners of the host could be killing the upload manually, which would be logical if I were hammering them for 10 files simultaneously. But usually, since I'm on a 56k modem, I only d/l one file at a time and rarely more than 5mb so I can't see why they would take such exception to me (other than for uploading so slowly). I don't know.... maybe the colour-scheme of some clients makes people bad-tempered. :)

Again, I have no idea whether this issue is LW related or not, but it's another new one.

Differences between beta and official versions
 

The beta versions include new features and protocol enhancements that are not currently in the release version.
Both Basic and Pro versions have their 2.5.x Beta version (the current release is 2.4.4).

About the 2.5.x beta versions:
The German translation was produced by a native German speaker. But there may still be some quirks in the beta translation. The French translation is tested since several months.
There will be also a Spanish translation from a native Spanish speaker. And may be a Dutch version if some Dutch translator helps us to revise the current translation.
Support for other non European languages is in progress.
Translations can be added and tested on 2.4.x versions of LimeWire, by extracting files from the 2.5.x message bundles in the LimeWire lib subdirectory, and editing your limewire.props file to set an alternate language such as "fr", "de", "es", "nl".
Portuguese (po) and Italian (it) translators are welcome to contribute a translated MessagesBundle from either the English or French messages which both are up to date !
Submit your translations by writing to this forum.

Comments
 

I've been running 2.5.3 for a few days on W2k, sharing about 215 files, cable modem through Linksys router.

1) When LimeWire is open, I notice that there are frequent, almost constant hard drive accesses (about one every 3 to 5 seconds). Looking at the process monitor, javaw.exe is eating up 20 to 35 megs of memory most times, and i can watch CPU usage jump from 0% to around 10% each time the drive is accessed. I'm not downloading, and no one is uploading, so I can't figure out why it's reading and writing so much. This has been a problem before, but it went away after I left the program running for a few hours. I left it overnight last night, and it's still making noise today.

2) Maybe it has something to do with all the shoddy Morpheus UPs, but I'd estimate that 95% of my downloads attempted from 2-4 star results immediately end up in Requery mode. The only reliable success I have is with one-star hosts that happen to be busy at the time. Perhaps 2.5 final could have a vendor filter...

Haven't had much trouble other than that (but I also haven't had any incredible 8 host downloads either :()

Brandan L.

Oops.

3) "Exit after Transfers" doesn't seem to work either, but I don't think it's worked in previous versions. Very minor detail.

Brandan L.

LimeWire 2.5.1 (pro), Java 1.4, W2K...

A couple of recoverable error bug reports have been sent to Bugs@limewire.com
...

Minor detail - probably more to do with Java than LimeWire... The dialogue boxes for selecting download and share locations do not support Windows network locations - i.e. I cannot browse to a network location (e.g. \\Mark\D\LimeWire).

I /can/ enter the location manually and it all seems to work (albeit - hashing of a few Gig across a 100Mb network connection is not very practical).
...

I haven't yet been able to shut down LimeWire and restart it without LimeWire getting locked into a state where it uses 100% CPU (Athlon XP 1500). It might eventually recover from this state - but not within the half hour to an hour that I've allowed it so far.

I have a suspicion that the problem relates to an inconsistency between the download.dat file and the actual files in the incomplete folder. If I delete the entire contents of the incomplete folder then LimeWire will start up without a problem (obviously with no files in the download queue).

Usually LimeWire does not immediately use 100% of CPU, but starts to do so at some point as it goes through the download queue.
...

I still have a problem whereby uploads drop off to 0KB/s and effectively block my upload queue (I have my upload bandwidth throttled).
...

When upgrading from 2.4.4 to 2.5.0 and then to 2.5.1, LimeWire did *not* keep my previous settings.

Mark

LW 2.5.3 / Mac OS 9.2.2

I previously said I was getting a lot of uploads, but I was only glancing occasionally at occupied slots and not paying attention to speed. I have now noticed that they all seem to sit at 0k and if I give them more bandwidth, they disappear.

Still LW 2.5.1...

I've been reminded (since it has just happened again) that occasionally LimeWire gets its names in a twist.

I've just downloaded a file from a series (avi) - LimeWire says the download is complete and the size was around 330MB.

The actual file that was downloaded is from the same series but has a different name and is around 20MB. (size is irrelevant - I mention it only to illustrate that the files do not match - the previous occassion that I caught, the downloaded file was larger than the file LimeWire thought it had downloade).

The actual downloaded file is correctly named - but was never in my download queue.

Mark

I think the weakest link in LimeWire is the upload part, as duplicate uploads are allowed and bandwidth utilisation is far from optimal, especially when throttled.
Also the settings aren't remembered when installing a new version, something new because prior versions took precedent preferences on osX.
I hope to see 2.6 in near future to correct those issues

i really find it ridiculous, that you claim this (german) translation was made by a native speaker. never! when i look at the german messages in cvs i can't believe that this translation is from a german...

Interesting on the German issue. Our translator is actually a native German speaker. Are there specific words or phrases that should be changed? Feel free to go to join the translation project at:

http://www.limewire.org/project/www/translate.html

Phillipe Verdy, one of our open source programmers, would be delighted if you wanted to take up making changes to that document. It's really easy to do -- you just have to change a text file.

Hi Adam,
I'm curious, what you are going to implement next. Could you please give us a quick preview of LimeWire 2.6? I know that you are working on non-blocking IO for Java 1.4 users (which as far as I do understand, will not improve the network itself significantly) and out-of-band replies (IMHO a very good idea).

Do you plan on implementing upload queues soon? I think it would be a great addition since it could really reduce the amount of requeries sent through the network while dramatically increasing the download success rate.

What does LimeWire think about partial file sharing. It'd be certainly useful for larger files. Do you expect it to be implemented soon?

How about gnutella weblinks? There are already a few websites offering links directing to files on the gnutella network via magnet-uris. I suspect integrating different browsers with java to implement one-click gnutella links is probably a little complicated, but I'd be already content with the possibility to copy the weblink, paste it into LimeWire and hit the "Add To Wishlist" button.

Another great feature that I would really, really love to see, would be the ability to run the LimeWire core in daemon mode, accessing it through a graphical frontend (possibly even from a remote computer) or even accessing the core from a webbrowser (with some kind of middleware mediating between browser and limewire core, - possibly a browser plugin). I believe it would be a great addition, if you could just click on a gnutella weblink, a go!zilla-like window pops up, showing you the progress of your download and a few minutes (hours, days,...) later the file is on your disk.

Maybe the last one is nothing for the next point release, but how about the other features: partial filesharing, upload queues and weblinks?

--
greg

IMHO almost every phrase must be changed. many sentences just seem, as if they were translated by a machine. that's the reason i don't really believe in you claiming that the translation is by a native speaker. if it is so, then tell the native speaker, he should translate the whole messages more freely, as no german will ever understand what f.e. is meant bei a "hauptrechner". (in fact it isn't even right, if you tranlate it back it is something like a "main computer" and not a host.)