LimeWire 4.0.2
 

LimeWire 4.0 is now available for download. LimeWire 4.0 contains NO BUNDLED SOFTWARE and has the following major changes/additions:

1) Better search results. Each search shows at least five times as many results as previously.
2) “What’s New?” feature. Users can browse the network for the most recent content additions.
3) Search drill down results. Searches in LimeWire now immediately display the artists, albums and
other information that fully describes files.
4) Faster connections on start up.
5) Proxy support. Users can now use web proxies to route their downloads to protect their identity.
6) A new search progress bar in each search tab that indicates the percentage of completion of a search.
7) Detection. When the Internet connection is down or a firewall is blocking access to the Internet,
Lime Wire will inform the user.
8) Support for International searches and International groups. Users can now search in any language,
and LimeWire ensures that a user will be connected to other users with their own language to aide
international users to receive search results in their native language and to find content from sources
that are close to home.
9) Improved downloads. By excluding the bad file sources, we rapidly make use of all the good sources
for faster and more reliable downloads.
10) Many additional changes and improvements offer users the most powerful, enjoyable file sharing
experience available.

In addition to the above major features, there's an assortment of other features, such as:
- OOB Proxying. Ultrapeers will now send an OOB query for their leaves' queries, allowing firewalled users to take advantage of superfast out of band queries.
- TigerTree EXchange (THEX) support, for automatic recovery of corrupted files.
- Brand new search interface and incredibly optimized display of search results.
- Faster startup times.
- ID3v2 support.
- Power Management, allowing LimeWire to use less resources when it is in the background.

For those keeping track of detailed changes in each of the releases, the following has changed since LimeWire 3.9.12:
- Try 10 more random ports to set up a listening port when LimeWire starts.
- Fixed some conditions where launching a file from the download table could fail.
- Fixed possible selection matching on search result filters.
- Various internal fixes for rare problematic cases.

For a full list of changes in each version of LimeWire, visit the LimeWire changelog.

We owe a very special thanks to open source contributers, such as Philippe Verdy, Roger Kapsi, Gregorio Roper, and Jens-Uwe Mager. We also owe a huge thanks to everyone on the forums who has helped to debug problems and suggest additions to LimeWire.

Thanks,
The LimeWire Team

Félicitations!!! For those who want to dl 4.0.2 it can be found there: http://www3.limewire.com/download/

Ciao:)

. . . or here http://www9.limewire.com:82/download

I wondered why the mailing list showed updates, but not the beta Pro page. For interest, just installed the Free and it looks fine. Any chance there's an easy way to get a Pro Installer of 4.0.1 and 4.0.2 to add to my collection? :p

Thanks again Sam for the credits, changelogs, and of course--all the work you and the team have accomplished. Time to break out the Lime daquiris!

[edit]--I'd forgotten to turn off the firewall when I got home from work, but LW 4.0.2 didn't remind me, and connected as an Ultrapeer.

:) hmm I like the new Limewire.com design, but the fonts are hard to read on safari which isn't the case in camino and mozilla, just FYI.

LW is now available to everybody from the basic downloads links.

Congradulations again!!!

Salut et voilà. Is this what you see? (When the mouse hovers, as in the 'Features' link, the links do highlight clearly). Aubrey, I assume, must be really busy for tomorrow, and cursing Apple's Safari ;)
[screenshot removed]

Oui Stief that's what happens. Mozilla shows that correctly so I assume something is missing in the khtml safari core. Why isn't Aubrey working on a mac? ;)

Force the page to refresh (generally using control-refresh).

LOL! She sure does nice work anyway. :p

Pro installed--and a 4.0.2 leaf already shows in Connections.
btw--Safari just kicked to an Amazon page while I was typing this and LW had just finished sending a file to iTunes. Gremlins!

Yep--the refresh worked (thought I had. Hmmm)

Ha, nice one Sam! Now it works great, what did you change if anything?

I downloaded today Limewire from download.com, and although it said 4.0.2, it was still 3.8.10.

Ivan
In the dark we make a brighter light

Hi guys,

I have a problem with my skins, when i select a skin it says that the skin is obsolete, so i download the new version of the skin, but when it comes to restart limewire for a new search, it comes again with the default theme!

How can i remove these obsolete skins for the new ones begin to work properly?

thanks for your help.

it's okay guys, i found the problem!

thanks anyways!

merci et vive limewire!!!!

Clean your system of existing adwares. Limewire has no adware or spyware, but its installer will not attempt to patch your system. May be it's your installation of iTunes on your Mac that is polluted. Or may be you clicked on the Google Ad banner at the top of this forum page.

Refresh your browser page or clean your browser cache. May be you have used an outdated link on download.com. To get to the appropriate page on download.com, follow the "Get Basic" button links on the LimeWire website.

A massive dissipointment this is!
I downloaded the international version from download.com (because i cant install the normal version) and i got 3.8.11 wtf? i cleaned my computer with window washer and all that stuff before i downloaded 4.0.2 what is going on
It took my an hour to download it on my dial up connection :(

Definetly disappointing :( But I see on the download page it should be 4.0.2
There http://www3.limewire.com/download/ look in internationnal folder, the installer was modified yesterday 15:10 as the other installers... Maybe an error on your part, but I you want to take the time dl again, you should get it there just to be sure.

Bonne chance

Could it be a delayed update on download.com for its distributable copy of the downloadable file? May be that's a problem of download.com's own server cache.

One note however: if you are upgrading, you don't need the international version to get international support of its translated resources. What is in the "international" version is the internationalized installer, and the Java JRE bundled.

So you are likely to already have Java installed, and the English installer would not be a problem (the English installer does not requests to you which language to setup, but if you are upgrading, you will keep your previous settings saved in %USER_HOME%\.limewire\limewire.props.

But even if it is not an upgrade, you can still change the language after installation of the "english-only" version. I think that this should be made clear in the download page: both installers support all international features of LimeWire.

Nope, tried it for the second time, and still got 3.8.11 after using Webroot window washer, uninstalling Limewire this is bad for me because i was looking forward to using Limewire 4.0.2 oh well... nevermind, maybe next time.

EDIT:

Maybe i'll just download it direct from LimeWire's website. I never downloaded LimeWire 3.8.10 or 3.8.11 so why do i get 3.8.11

Is there a magnet link for 4.0.2 international? because i have 2 other Gnutella clients on my computer, Bearshare 4.5 and Morpheus 4.0.4

I downloaded now Limewire from its website. Really amazing. Nothing to do with the poor experience I had in the past. This is very, very good.

Keep on the good work.

Ivan
In the dark we make a brighter light

Just a small problem i have been having with 4.0.2 (That i finally got to install instead of 3.8.11) things are cut off like where it says "Getting started" parts are cut off, and where it is circled in red, i have also been having this problem with the 3.9.X Beta's

I couldnt attach it cos it said 200K was to big so: www.geocities.com/imeshlite/LimeWire.jpg

Please create a HTML page referencing this image. Geocities does denies access to visitors for non HTML file if this file is not loaded from a Geocities hosted HTML page (where Geocities attachs its ads and JavaScript). This done, give the URL of your HTML page which just needs to contain the reference the image like this:

<HTML><BODY><IMG src="LimeWire.jpg"></BODY></HTML>

(store that HTML file in the same folder "/imeshlite/" as your image, for example with the name "/imeshlite/LimeWire.html".

Im not sure if this is what you wanted but: http://www.geocities.com/imeshlite/LimeWire.html

Apparently your Windows 95 or 98 fonts have been changed and do not display the appropriate metrics (the line height does not match with the normal definition expected by the default theme for Windows.)

As you seem to use the default theme for Windows, it uses the following fonts:

# tabs and window labels
CONTROL_TEXT_FONT_NAME=dialog
CONTROL_TEXT_FONT_STYLE=1
CONTROL_TEXT_FONT_SIZE=11

# nothing in 1.4, results list File Title and Library folder names in 1.3
SYSTEM_TEXT_FONT_NAME=verdana
SYSTEM_TEXT_FONT_STYLE=0
SYSTEM_TEXT_FONT_SIZE=10

# results list font in 1.4, results list details in 1.3
USER_TEXT_FONT_NAME=verdana
USER_TEXT_FONT_STYLE=0
USER_TEXT_FONT_SIZE=10

# nothing in 1.4 or 1.3
MENU_TEXT_FONT_NAME=verdana
MENU_TEXT_FONT_STYLE=1
MENU_TEXT_FONT_SIZE=11

# nothing in 1.4 or 1.3
WINDOW_TITLE_FONT_NAME=Georgia
WINDOW_TITLE_FONT_STYLE=1
WINDOW_TITLE_FONT_SIZE=11

# nothing in 1.4 or 1.3
SUB_TEXT_FONT_NAME=Georgia
SUB_TEXT_FONT_STYLE=1
SUB_TEXT_FONT_SIZE=11

Are you sure to have the correct versions of the following fonts:
Verdana, Georgia ?
Also when a font cannot be found, it reverts to a default "virtual font" given an alias name "dialog".
The definition of this font alias is part of the Java installation.
You may look at which version of Java you use, to make sure that the "dialog" virtual font is properly defined for your system.

---

Open the file "font.properties" present in the "lib" subfolder of the Java installation.

(1) If you use Java 1.3.1 or 1.4 You should see something like:

dialog.0=Arial,ANSI_CHARSET
dialog.1=WingDings,SYMBOL_CHARSET
dialog.2=Symbol,SYMBOL_CHARSET

which indicates that the actual font will be searched in this order:
Arial, Wingdings, Symbol.

(2) If you use Java 1.5.0 Beta 1, the "fonts.properties" file should contain something like:

dialog.plain.alphabetic=Arial
dialog.plain.chinese-ms950=MingLiU
dialog.plain.hebrew=David
dialog.plain.japanese=\uff2d\uff33 \u30b4\u30b7\u30c3\u30af
dialog.plain.korean=Gulim

(the format of this file was changed in Java 1.5.0, but users noramlly never need to modify the "font.properties" file which is installed with Java).

Here also, there's an explicit reference to the Arial font to display Latin, Greek and Cyrillic (grouped under the term "alphabetic")

---

So make sure that these 3 core fonts are properly installed in Windows. It's possible that you have incorrect versions of these fonts, or copies that were not built for Windows 98.

So you may need to reinstall the 3 standard Windows fonts from your Windows CDROM or from updates. Some softwares modify core fonts and replace them with fonts with identical names but different metrics:

Arial, Courier New, Time New Roman

Plus these 2 fonts from Internet Explorer, if you want to use the default theme on Windows:
Verdana, Georgia

Alternatively, you may want to try other themes:
- for example the "Windows" theme uses only the native fonts described in the Java installation in "font.properties". But the look and Feel is reset to use the default Windows coloring scheme of your Control panel, and buttons or menus corresponding to the standard Windows Look and Feel.

- or the "Amber" theme which was made to use the Java Metal Look and Feel but with only the default "dialog" virtual font. Without any forced bold character style (I created it for international users, so that they will be able to display the interface correctly with their language, notably for languages written with complex scripts like Chinese, Japanese, Korean, Thai and Arabic that are difficult to read when displayed with Bold characters).
A screenshot of this theme follows:
http://www.rodage.net/docshare/AmberTheme.png
(Note that, due to the 256 colors palette (needed because of the progressive background shading), the image is a bit darker than it is in reality with more colors and a more dominant bright yellow). I could have used a 16-bit palette, but I wanted that the image views here keeps at reasonable size.

Note also that this is a development/test version, that has some unreleased items. Also the interface shows the French translation...

LimeWire 4.0.3 is released. 4.0.3 is a service release for 4.0.2, fixing various internal bugs. 4.0.3 also fixes the "too many peer connections bug" and should fix problems first-time Mac Classic users were experiencing. Approximately 30 internal (and rare) bugs have been fixed for this release.

Here is a magnet-link to LimeWireWin 4.0.2 from the LimeWire page. You need to paste it into your browser, as the URL-Parameter adds "http:// ":

magnet:?xt=urn:sha1:RZ73ST6NRS45QIMGX2CIOVCWIJCBVJ JP&dn=LimeWireWin.exe&xs=http://edrikor.dyndns.org:6346/uri-res/N2R?urn:sha1:RZ73ST6NRS45QIMGX2CIOVCWIJCBVJJP&xs=h ttp://edrikor.dyndns.org:9845/uri-res/N2R?urn:sha1:RZ73ST6NRS45QIMGX2CIOVCWIJCBVJJP]LimeWireWin.exe

I've been wondering about something in the past days :confused:

Is there something different in the internationnal versus the english version on windows related in local connections? I'm asking that cause on os x, starting as a leave I easily get 3 fr connections, but on windows with the english version (but with the interface in french) I never get those fr connections (the prefs are on in options).

Merci

LW now tries to connect mainly to your region.
Did you set teh english LW to run in Frensh?

arne, I wanted to have the confirmation from LW devs that the language used for the interface is the one that receives preferencing (normally it is, but the english windows made me wonder, I'll try the internationnal later). Yes of course the GUI is in french. BTW it connects by language not by region AFAIK. ie even if I'm in Québec I connect to lots of nodes in Europe.

Ciao

Can files that get manually added to the shared folders after LW has started be uploaded, or is a Refresh first required?

btw--4.0.3 on 10.3.3 looks fine so far. Should we look for the changelog for the 30 fixes (whew! probably takes longer to document than fix ;) ) here or the CVS logs? FWIW, http://www.limewire.com/english/cont..._history.shtml only shows up to 3.9.12

Yup! I can confirm LW Pro v4.0.3 works perfectly with OS 9.1 whereas v4.0.2 didn't work at all. :D

local preferencing update
 

Well the internationnal version is much better and faster to find fr local connections than the english version (I tested many launches, well it's not a good test as LW remember IP of last connections but still...). Maybe you may want to look into it, if it is possible that there is a flaw in the current LW implementation.

Ciao

location of users in the world does not matter much here. What is used is the selected locale, that also conveys a user's cultural background, and contents that will more likely match the user's assumption.
So yes there will be a cluster between France and Québec, but this is not an exclusive preference: there are still lots of interaction with the rest of contents shared by English-speaking users, or users of other languages.
The default setting of 2 connection slots reserved with locale preferencing enabled leaves lots of place for other contents as well. But my opinion is that a country or continental region would probably work better. to get fast responses from users in the same area, if content is not a priority for a user.

Note however that the geographical location of users does not influence much the networking latency or bandwidth throughput or quality. there are many cases where users in the same country will have poor interconnections but excellent intercontinental connections. This depends mostly of the ISPs upstream bandwidth providers an their peering links. So for Western Europe, and North America, there's not a significant imporvement by restricting these users by zones. For users in Asia or Eastern Europe, language will not allow cood international or even national connections.

Care to share how you fixed it? Pretty please?

hey everyone is there anyway of downloading the limewire 4XX pro version obviously without paying for it?

>hey everyone is there anyway of downloading the limewire 4XX pro version obviously without paying for it?

No.

Your kinda on the wrong forum to ask this ;)

in 4.0.4, I'm not sure if this is a bug, but it can be turned into a feature ;)

Switching themes also clears the search history.

btw--I couldn't try Philippe's Amber theme: got the message to update, but couldn't find an updated Amber. Nice page though (especially the wry descriptions of each theme)--I hadn't seen it this year.

Isn't it in the list of installed themes? I did not check it.
But you can download it there:

http://gui.limewire.org/unbranded-source/browse/~checkout~/lib/themes/amber_theme.lwtp

pro
 

i'm curious,

what does the "PRO only" theme for limewire pro look like

Philippe--it's in the menu (and in the ~/Library/Preferences/LimeWire/Themes folder), but choosing it gives the "out-of-date" message and the link to update. I used your link, but for OSX I had to change the extension to zip, unzip it, and add the folder to /Themes. Looks like OSX needed the lwtp file and the unzipped folder to work. The lwtp file alone wasn't enough.

swimkid--the Pro theme uses a faint green and the LW plug rather than lime (I don't really notice much else different). You should donate to Pro anyway ;)
Mail me I'll send you the lwtp (if no one objects) or a magnet of a screenshot. Just curious--why wouldn't you get a Pro? You are interested in p2p, and LW development is the most active and interesting as you've seen.

LimeWire 4.0.5 is released, as a service release for 4.0.4. The following changes have been made:

- Fixed some cases where scanning for old files could cause errors if a file was deleted at the wrong time.
- Ignore even more UDP sending errors.
- Stronger validation of many string parsing routines to catch more faulty network data.
- Fixed issue where reloading shared files could cause uploading routines to temporarily fail.
- Fixed TigerTree retrieval to never download the tree twice from the same host during the same connection, and to allow all trees greater than or equal our preferred depth.
- Fixed downloading themes within LimeWire to correctly expand the downloaded theme.
- Fixed creating the TigerTree of a shared file to properly close the file when finished.
- Fixed corruption checking of downloading to use the smaller depth of our created TigerTree and the downloaded TigerTree.
- Ignore more errors caused by corrupted data when loading annotations.
- Ignore more internal errors related to Java on OSX.
- Fixed rare case of Tips of The Day going out of synch.
- Fixed resuming of downloaded files to not fail in some rare conditions where the list of downloading items changes unexpectedly.

Thanks,
The LimeWire Team

Thanks Sam.

In hindsight, where should I have looked to catch those bugs (at least the OSX ones)? I'm just wondering what clues I missed testing the last betas. Any tips?

Sorry about that. Will try harder ;)

There are no more common easy-to-find bugs to be fixed -- we've fixed them all. ;) These service releases are mainly to clean up rarer problems that can cause LimeWire to act less-than-perfect. None of the bugs are showstoppers, but a combination of them can lead to consuming too many resources, or not being to see XML, etc...

We have a 'console' tab planned that can list out problematic things that aren't necessarily errors, but are indicative of something going wrong. Until that's added, there's absolutely no way anyone could have found these bugs prior to them being reported as bugs.

Doubtful that it's a problem with Safari or khtml so much as one of the almost 300 errors in HTML on the limewire.com home page that are reported by the www.w3.com HTML validator.
Safari tries to do things correctly, and is (rightfully so) slightly intolerant of non-standard markup and scripting.

Uh, the problem with the links was because of caching stylesheets. Refreshing the browser forces it to retrieve the newest files. People's browsers still had a cached version of the older LimeWire.com style.

Also, as far as the 300 errors go, it is actually 237, and about 50 of them are because the "alt" tag on images wasn't included (so there's no text to use in place of an image while it loads), about 100 of them were an ampersand in a link was used instead of an &amp (which cause a ton of cascading parsing errors with the validator), and some minor nuances with whether or not the word 'STRICT' or 'TRANSITIONAL' is used as the document type.

Uh, Sam, can we have another beta to play with? Philippe's new optimizations sound really impressive (might this mean java will begin to lose its "slow" rep?), and I'm curious what zab and Roger have been doing with meta-editors (?).

Maybe we're getting bored here so we'll pick on the web site: 4.0.5 isn't generating enough problems to keep the forum busy. :p

Ah! The sweet sounds of silence in the forums!

Congrats--sure is sweet to watch the netsize grow (dang--just about hit 300,00 tonight before 'Safari' stopped showing the daily graph).

Hey--I keep hitting refresh, but http://www.limewire.org/ still won't update and show the new opensource credits. Will Mozilla help? ;)

A new beta is coming soon... we're making sure that everything is stable and deciding on what new features should be initially included.

The program that generates the crawler numbers & images sometimes fails -- it has nothing to do with Safari. On all browsers the # of hosts is sometimes not displayed, and the image graph sometimes fails to load.

limewire.org has not been updated yet. It will be.

sberlin, why has Limewire blocked Morpheus? Isn't that abit stupid? (he prob wont answer this anyway)

He probably won't answer (most probably heard your question far too often), but I will: Morpheus didn't give anything back and harmed the network by being to greedy (connecting to too many hosts, etc, which slowed down the whole network).

Read the past GDF-messages about that subject, and you'll see, why they decided to do it. A cooperative Network needs to shun out overly greedy "members", because else all would pay dearly for the greed of a few (or those few would manage to take down the network). That's how cooperation works: As long as all abide the rules, the network runs fine, but as soon as someone begins to exploit the network, others need to shut him (or her or it) out or have the whole system degrade (from which the cooperative ones would suffer first, the leeches only later, but they'd suffer still).