Hi Folks,

The LimeWire 4.3.2 Beta is now available. PRO users can download it from their personal download page. Free users can download it from the LimeWire Beta Page.

Changes in LimeWire 4.3.2 include:
- Fixed a problem with international characters. Previously, some search results would contain 'block' characters and saving these files on some operating systems would fail. This is now fixed. Thanks goes to "heavy_baby" for pointing out the problem and proposing a fix.
- Added expanded server-side support for an upcoming new feature that will allow LimeWire to learn about more sources faster and more intelligently pick which sources to to use when downloading.
- Added a fix for some degenerate FW-FW transfers that would cause the transfer to fail. Thanks goes to Julian from BearShare for pointing out the problem and proposing a fix.
- Re-added the ability to rename files in the library. Thanks goes to FishEye for maintaining our CVS history.
- Updated the Windows installer to better handle a few situations, and LimeWire.exe to ignore a "jre" subdirectory and instead always pick the most recent Java version from the registry.

Thanks for your help in testing the betas! We're hoping to stabilize this installer & version very soon, and release it as a the production version. Then we'll continue work and release a more feature-filled version shortly afterwards.

Thanks,
The LimeWire Team

That was 3 hours before this post of yours so you weren't kidding were you! lol

re cc Licenses

A quick check showed all working here as expected.

Is it possible to use LW to search for only licensed material? i.e, something like the What's new? search, or a filter . . .

Yup. It won't work well right now, since not many clients understand the licensing, and it only works for Audio when it does work, but it's possible. Just do an 'Audio' search, choose 'More Options', and choose 'Creative Commons' from the 'License Type' dropdown box. You can also specify further criteria, if you want.

When will the FULL version of Limewire 4.3.2 be out?
As Im using Limewire 4.2.5 out now and dont wanna risk using a BETA.

From my experience: Neither beta never got me no problems (this is true, even though the style is a parody on some I already read (and used myself) in english :-) )

__________________

-> put this banner into your own signature! <-
--
Erst im Spiel lebt der Mensch.
Nur ludantaj homoj vivas.
GnuFU.net - Gnutella For Users
Draketo.de - Shortstories, Poems, Music and strange Ideas.

I can't recall having problems with betas except for memory issues on os x. Now, using CVS builds is an other matter, but beta builds are pretty safe. You can alway do a backup of your inomplete files folder if you fear loosing downloads.

Ciao

__________________
Liens d'intérêt /Links of interest:
Gnutellaforums en français /The House's rules you have to respect / First search the forum, then create a thread / Free software alternatives! - Logiciels alternatifs gratuits!/

I think I started using LW betas from 4.1.4/5 but only struck an issue when I jumped back from 4.1.7 to 4.0.4 where the incompletes refused to load. Before that I had no problem interchanging b/w the 2 versions. Since then I haven't had any issues jumping between betas, most recent official release versions, & jum cvs. Thus LW is one program I have confidence with their betas (unlike betas of other softwares.)

LW betas have been really quite safe for me, but that's not the point.

Betas are betas BECAUSE they haven't been tested as much, so we SHOULD be careful.

Easy solution though: I just install betas on another admin account. If the beta wipes out the home directory, no problem: I only have files in that account that I know I might lose, and I don't worry about a beta messing the 'valuable' files I didn't get arouund to backing up

btw Lime-UK: what OS are you using? Someone here has probably tested the beta on a similar one.

btw, the OS X VM problem is still here. I had to quit yesterday after it rose to 1.3 GB and the system warned that the HD was almost full.

Any more news on tracking this down? I noticed Apple updated the CHUD tools, and hoped that might have helped.