OS/X notes

We just posted a slightly modified version of the OS/X installer in www.limewire.com/beta/ The only difference is that the background on the spinning lime image is transparent.

Here are the bugs people have reported on OS/X, and our diagnosis:



* Configuration windows appears after every startup. We can't reproduce this. Is LW in a directory without write permissions? It needs to write limewire.props to record configuration settings. (Ideally we'd write this to the resource bundle, but we haven't firgured out how.)

Reply:

I can reporduce this by exiting Limwire using Quit from within OSX itself (using the pull down menu next to the blue Apple and quitting there) vs using File->Exit that is within the Limwire menus. If I use File->Exit, I dont see the config window again.

David

I tryed to download the 1.6 beta and when i install it it takes to long to set up the java thing

We unfortunately can't make that any faster; it's Sun's code. However, I bet you one beer that it will work if you give it a few minutes.

Christopher Rohrs

I noticed that there is no LimeWireOther.zip in the beta 1.6 location. Will there be a LimeWireOther.zip beta 1.6? Or perhaps there were no changes made to the portion of the code that makes up LimeWireOther? I presume that all of the OS specific packages contain whats in LimeWireOther along with an OS specific JVM?

LimeWireOther 1.4b works pretty well on OS/2 Warp Server for e-business, but it has a few problems and I'd like to try 1.6 before passing any judgements.

The LimeWireLinux.tgz should work for all platforms if you have java. The only change actually is that you have to convert the ";" in the limewire.props classpath to ":" for it to work properly. We should probably be able to fix that.

-greg

Actually, I think I mean that the other way around. Convert the ":" to ";" in limewire.props for the classpath.

-greg

--
I have a question. When will the "real" 1.6 come out, not the beta? Also, for Win 9x users, when will we get the systray feature?

Kirby
___________


<div align="center">
<img src="http://home.swbell.net/mattwtx/confetti.gif" length="200" width="75">
<b>THIS IS KIRBY'S 100TH POST!!!!!!!!!!!!</b>
[IMG]http://**************.com/ms/kirbykore/images/kirbywave.gif[/IMG] [IMG]http://**************.com/ms/kirbykore/images/kirbywave.gif[/IMG]
View Kirby's very first post!!!!!!!!!!!!</div>
I am very glad that all of you can be here today to see my 100th post. 100 posts makes you a senior member in the community, and there is only one other member who isn't an admin who has reached this mile stone. His name is lightstone. I have reached this point by helping other people, and I encourage you to do the same. Once again, thank you.

Congratulations on an excellent and very stable program.

I thought you would find it useful to know that both Mac Beta versions 1.5 and 1.6 are missing the last 2 "Options" tabs (Filters, Advanced) on one of my machines (iMac 233), but present on my other machine (PowerBase with G3 accelerator). On the latter machine everything works perfectly and completely.

In addition to the missing Options tabs, Limewire on the iMac does not preserve changes to any options involving typing in a value (that is, the cancel, apply, and OK buttons don't work; they just turn dark colored with a click and nothing else).

Both machines run OS 8.6 with _all_ latest Apple software updates, and they are connected to a LinkSys Cable Router with latest firmware. I use the most minimal extension set (that is, to get online) for both machines, using latest version of Conflict Catcher. Limewire folders on each machine have an identical installation of files and file sizes.

I have rebuilt desktop and ran latest Norton Utilities and DiskWarrior, with no effect.

I have made many installation attempts, always with no extensions loaded (shift-key down). I always give application at least 20mb memory.

With the exception of the Options problems, Limewire works fine on iMac.

Thanks


P.S. Increased application memory and minimal extension set has reduced freezes and other problems down to 1 error per 20 hours of usage.