LimeWire 3.6.4 Beta

[afisk]

We've released LimeWire 3.6.4 beta, available from your pro download page as well as from the free page at:

http://www.limewire.com/english/content/beta.shtml

This version adds several fixes and improvements over LimeWire 3.6.3. These include:

- OS X users will now have the option to automatically run LimeWire on system startup, just as Windows users currently do. This feature is limited, however, to 10.2 users who have installed the Java 1.4 update. If you haven't installed the update, you should do so.

- LimeWire will now automatically sort search results by the size of the result group because you have a better chance of download success by downloading from larger groups.

- A fix for a bug when downloading a file with only differences in case from the name of an existing file on disk -- this would cause failures on operating systems that are case-sensitive, such as OS X.

- We've added a number of new default extensions of file types to share, including bz2.

- Changes on OS X startup to ask the user to enter their language preference. This allows us to use the standard OS X installer for international versions in addition to the english version.

So, that's all the changes. We're hoping to release this version quite soon, and thanks for everyone's help with testing!

-LimeWire Team

[stief]

Thanks for the info Adam, and appreciation once again to all the coders.

the beta finally showed--even though Safari requires the bookmarked page to be refreshed. Still don't understand the delay between the updating of the signed version in the cvs@gui.limewire.org and its appearance on the bookmarked beta Pro page.

The LW installer is still overwriting an active LW. I had dl'd and installed jum 221 earlier (it asked for the language and correctly refused to overwrite the LW 3.6.3 beta which was running. The 3.6.4 beta did not ask for the language, and went ahead and overwrote the running jum 221.

Magnets often require a number of clicks from the browser to get them working in LW. (I checked with the jum magnet and the Magnet mix ones). btw--Aubrey's cat porn is most popular

Could the Ethernet transfers be exempt from the upload slider? I've limited uploads to 90KB/s, but want that to apply to 'extranet' bandwidth (word?), not intranet transfers over ethernet. Instead of the 800KB/s I've seen in the past, the transfers were slowed to a ~50KB/s between my G3 and G4. Too, the server side showed a single upload, but the client side showed the file swarming from the 192.*.*.1 (gateway) and the local IP of LW on the G4.

Re the discussion of the need for PRO sales--sounds like it's needed if hiring business managers over coders is necessary, which also risks the opensource relationships which keeps at least some of us loyal. If open source is still the future of LW then a specialized GUI "sexy" coder who can overcome the problem of open source apps being primarily by coders for coders might make LW more attractive to end users (great introduction to opensource development in Wired . I can't get my kids to use LW or the jums--they 'like' Acquisition and Poison. I prefer LW for the education it provides on the way filesharing works, and the fact it is the most progressive and technically impressive networking p2p app and developer team I've seen.

Lastly--thanks for the attention given to OSX issues. LW has for me at least tapped into Apple loyalty.

[sberlin]

The delay between the update.ver file being updated and appearing on the website is because we test all the installers multiple times. We don't want to accidentally allow an improperly built version to be released.

I wasn't aware the Jens had added an installer to his disk image. When you say it refused to overwrite the running LimeWire, you're saying you had LimeWire running, and the copy of the 'LimeWire' folder from the disk image to the 'LimeWire' folder in /Applications was denied? Did anything particularly bad happen with the OSX-Installer LimeWire uses in the official release overwriting that directory?

Language will only be asked the very first time LimeWire 3.6.4 is installed, and only for OSX users. Subsequent LimeWire versions will have remembered your language from prior installations. You used a prerelease version provided by Jens, so were able to see the dialog earlier.

We've considered removing the bandwidth limit for ethernet transfers, and there may be an easy way to do just that...

[stief]

Hi Sam. You're right. I just did the usual drag to Application Folder from the jum .dmg. Since I was surprised by the dialog asking about language, I'm not certain exactly when I saw it. I think it was right after the drag.

Nothing bad happened with the official installer that I noticed, except the contents of the jum Limewire were modified.

Perhaps the officail installer shouldn't fire up the OSX installer immediately, but wait for the user to double-click the package. Safari mounts the .dmg (good) and immediately asks for the admin pw, which is a bit disconcerting when browsing through a bunch of other windows.

btw--the dl from the LW page is a fast 90KB/s, even though LW is running as an UP, downloading a few magnets and uploading an average of 50KB/s. The new LW's don't seem to hamper my internet browsing, etc at all now I've throttled it to 90KB/s

ps--forgot to say thanks for adding those other extensions to the default list, and to ask that the quit button become a close window button like Safari and other OSX apps.

pps what is a "WebMedia Spider Arachnid 3.3 (GnucDNA 0.9.2.6)" Ultrapeer I see connected? I can't browse it to find out if it's a leech.

[sberlin]

>ps--forgot to say thanks for adding those other extensions to the default list, and to ask that the quit button become a close window button like Safari and other OSX ap

We talked a little about this, and decided that it'll change when we're confident that LimeWire will not be a performance problem. We have a few things in the works that'll help to ensure this is the case.

The OSX Installer immediately asking for the admin PW is a 'feature' of Safari -- it automatically runs a package if it's the sole contents of the DMG.

Not sure what the WebMedia thing is -- most likely just a random client built ontop of GnucDNA.

[stief]

Thanks for all the info and interesting hints--I've unchecked the Safari->Preferences->General-> "Open 'safe' files after downloading"

The new autostart feature worked, but now I've unchecked that too in the LW prefs. I'd expected it to be removed from System Preferences->Login Items when the LW pref was applied, but had to quit and reopen System Preferences to see it removed.

Glad to see the iTunes/LW player prefs now save correctly. I thought Roger also submitted more iTunes options (like sharing playlists so songs properly show in the Library).

I dl'ed your popout.zip Sam (will you port it to OSX to properly test your PBook? ) to my unshared dl folder, moved it to a shared Magnetmix folder, but how can I share it without interrupting uploads? I don't want to use the refresh button (>10k files being shared), so I usually wait for the next session. There was some talk of how to keep the Library updated: might something like the way the downloads.dat and .bak work be used to avoid interrupting uploads if the library needs updating? Perhaps the unshared dl folder could show in the Library, and files could be dragged and added to the appropriate shared folder from there?

Incomplete T-* files still show in LW searches. My son uses the same Shared folder whether using LW or Acq, but because Acq's Incomplete folder is a sub-folder, its contents show up when I search or browse his machine. I thought any folder named "Incomplete" wouldn't be shared, even when the parent (no pun) was shared.

A search for "limewire" returned 903 non-ethernet results in less than 5 seconds, most of them interesting but irrelevant.

A search for my reference file returned 273 results in two minutes, including 17 hits for the each of the contents of the bundled reader application package (probably being read as a folder by OS 9 servents?), and a bunch more seemingly unrelated .mp3's.

I guess the hope for being able to easily email my files to friends via a "Send Magnet Link" is unlikely soon. This would be an attractive Pro Option.

Well, once again this is too long. Hope some of the comments will be useful.

Cheers.

[sberlin]

System Preferences does not handle preference-changed notification events. While it is open, the preferences are cached in memory. You must restart System Preferences in order for it to recognize the changes -- in practice, this isn't a problem since most people will not have it open to try and 'see' what LimeWire is doing.

Heh. PopOut (which I actually originally called breakout, but didn't think that name'd fly for a public release) is written in x86 assembly -- wouldn't be too easy to port to a PowerPC architecture I don't think. Fun project, though.

Incomplete folders should not be shared. Does Acquisition allow you to call it something other than 'Incomplete'? I'm fairly positive that LimeWire correctly handles this, but I'm not sure how Dave has mucked with the code.

Thanks.

[jum]

Originally posted by sberlin

I wasn't aware the Jens had added an installer to his disk image. When you say it refused to overwrite the running LimeWire, you're saying you had LimeWire running, and the copy of the 'LimeWire' folder from the disk image to the 'LimeWire' folder in /Applications was denied? Did anything particularly bad happen with the OSX-Installer LimeWire uses in the official release overwriting that directory?

I did not add an installler, and I will not add an installer in the future. I might not have expressed it clearly enough in the past, but the whole reason why I build my versions is to get rid of the installer besides getting to play with the cvs changes earlier. Simple drag and drop of the LimeWire.app should be enough in my humble opinion.

The reason why the overwrite happens with the installer version you did and not with my build is the way it is copied. The OS X installer does not check if the files are busy it is overwriting. The Finder does check this fact and refuses to overwrite a running application.

As far as I understand the guidelines for the OS X installer an installer script is supposed to quit the application if it is about to be overwritten. But then the company I did do OS X installer packages for did switch to their own installer as the OS X one was found to be lacking.