I was running LimeWire and 1 or 2 versions behind. I decided to upgrade to the current version. I downloaded LimeWireOther.zip, deleted the ./LimeWire directory and expanded LimeWireOther.zip into a new ./LimeWire directory.

I changed into the ./LimeWire directory and executed runLime.sh. It ran fine. I was surprised to see that it somehow kept my settings from the old release. I checked around for a conf file but didn't find one (I'll do some more research on this). I closed LimeWire.

Now every time I try to run LimeWire I get:
Starting LimeWire...
Java exec found in PATH. Verifying...
Suitable java version found [java = 1.4.2_01]
Configuring environment...
Loading LimeWire:

Then LimeWire freezes on "Loading Core Components..."

I've searched on this and in other cases it was an installation problem. In one case upgrading to a more-current version of LimeWire resolved the problem. In another case there was a problem with the ./Incomplete directory (which I deleted to prevent this from being a cause). It seems this is more of a problem on Mac than Intel/Linux.

I tried deleting ./LimeWire and reinstalling from scratch without success.

uname -a
Linux t30.powertool.com 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 i686 i686 i386 GNU/Linux

I'm running FVWM. I have plenty of memory and free HD.

Please help if you have any idea why LimeWire is now locking on me. Let me know if I can provide any additional data or logs.

Thanks!

And now it's running fine.

The only thing I did was close Mozilla (Mozilla 1.0.1).

Maybe it was a memory issue?

LimeWire freezes on "Loading Core Components..."

I started LimeWire recently to see this exact same message, again. I was running a slightly dated version so I downloaded the current version -- LimeWire Basic 4.10.9.

After installing I received the same error and lock. I cleaned the directories and installed again from scratch to receive the same error and lock-up.

While LimeWire Basic 4.10.9 clearly states support for JRE 1.4.2_01 I downloaded and installed JRE 1.5.0_06. This solved the problem for me.

I'm posting this in hopes of assisting anyone else that might have this same problem.

I'm also posting this to ask the question -- is there a problem with stated support for JRE 1.4.2 in 4.10.9 or could it be something else?