Nope. Reinstalled Limewire, set the connections to 2, gave it 40 megs of memory. Did a download just fine. Moment I tried to switch to the finder it came crashing down just as it has every other time I tried.

And I made a mistake on my previous post. It was, in fact, a type 2 error message, NOT a type -2. It's a repeatable error. Same act produces the same results, whether I click on the applications menu or click onto the desktop.

-m

Same here with the new iBook. Running OS 9.1 with 256mg ram. Doesn't quit all the time, but fairly often when switching to other apps. Have not updated MRJ. Frustrating....

I am running an G3 iMac 500 - have allocated 50Meg and also get the type 2 error. I solved it simply by not touching the applications tab when using limewire. To change applications I just click on the application windows behind limewire and there are no crashes.

For people getting the Type 2 error, there should be a file in your LimeWire installation directory called "limewire.lax." If you open that file in a text editor, there should be a line that reads:

lax.nl.macos.apple.menu.quit=false

Try changing this to read:

lax.nl.macos.apple.menu.quit=true

and see if you still get the error.

>Try changing this to read:

>lax.nl.macos.apple.menu.quit=true

>and see if you still get the error.

Didn't work. Still get the error. I am finding, as someone suggested, that I can switch windows, so long as I click on the window itself. If I try using the applications menu, same crash type 2 results. Though this was the case before I edited the text file. No changes either way since.

-m

response to rcq 1017
 

download MacZilla from download.cnet.com, and it automatically recognizes the file type, configures it to a Maczilla file, and you can play it. AVI's will freeze the computer though, better to use mpegs only with maczilla

Changes didn't help...
 

Unfortunately this didn't help matters. I also read through the thread, and attempted your other suggested fix, but the following line does not even appear in my LimeWire.lax file:

lax.nl.macos.apple.menu.quit=false

Thanks to everyone for trying these solutions, and our apologies for the continuing frustrations.

As I've mentioned before, the underlying problem here is that Java is really not very well supported on Mac OS 9.1 and below, although it is very well supported on OSX. We will continue to try to fix these problems, but I am not optimistic due to the weak underlying support for the programming language.

With all due respect, LimeWire is the ONLY Java app that causes problems like this consistently. I suggest the problem is not the Java support in OS 9.1, but more realistically with LimeWire's poor technical implementation.

This seems to be a regular problem when engineers try port a Windows application to the Mac... there is a basic lack of understanding of how to correctly write the language using Apple's OS. Maybe OSX will help, but many of us refuse to switch over until this platform is fully supported across the board... and it's a convenient excuse for developers who write shabby products for Mac OS 9.1 and below.

From the functionality design standpoint, LimeWire is a sleek, sexy Corvette. Unfortunately, under the hood, the engine is more like a Yugo. I strongly recommend that everyone avoid this junker.

The JVM implementation for the Mac has serious technical issues for any sophisticated program. Its use of cooperative threads, for example, means that a program using many threads (like LimeWire) can exhibit serious performance limitations. Multithreading is, however, a cornerstone of modern programming, and should be supported in a robust manner.

LimeWire is an extremely well architected and robust program. We program to the API, as any good program should do, and Apple's Java API is Sun's API. They do not maintain an API of their own for, they simply use Sun's.

With all due respect to Gary, LimeWire is not a Windows program that was ported to the Mac. LimeWire is a Java program written to the Java API.

While we admittedly have not had the resources to devote as much effort to the Mac version of LimeWire as we would like, please be aware that we have not had similar problems with JVMs on any other platform. LimeWire performs well on Linux, Solaris, other Unix varieties, and even OS2. It also performs quite well on OSX. Mac OS 9.1 and below is the only platform exhibiting these problems, and this is all with the exact same code base, as it should be with a Java application.

This strongly points to a well architected program experiencing the limitations of the underlying Java implementation.