Additional Note
 

I yet don't know the difference RunLime.jar and LimeWire.jar but they both run the same and well without errors on my system. I can only run the commandline runLime.sh and not LimeWire the executeable. I have a hunch. Can you post all your compilers (rpm -qa|grep gc)? I think a library called libgcj and gcc-java maybe the true culprits. I had a brain fart in the previous post but now I am remember while java path was added into the .bashrc or .bash_profiles. It is added to allow you to have your downloaded java package to be chosen over any other first. Kaffe has residence in /usr/bin. When I had given you the suggestion for your tcsh shell environment, I should have explicitly stated that JAVA_HOME had to be first in your set path. Or simply instead of using the variable JAVA_PATH, just simply place the full path to your java executables like so:

set path = ( . /usr/java/j2jre1.4.0/bin, /usr/bin, /usr/sbin )

That way, no matter how many java jre and sdk packages you have installed the one you want used with LimeWire 2.4 will be chosen by default.

Re: Additional Note
 

perl-Msgcat-1.03-7mdk
libsigc++1.0-1.0.3-2mdk
gcc-cpp-2.96-0.62mdk
gcc-2.96-0.62mdk
gcc3.0-cpp-3.0.1-1mdk
gcc-c++-2.96-0.62mdk
gcombust-0.1.46-1mdk

Nope, no gccjava. Anyway, when you said to add JAVA_HOME to my path, I did add it to the beginning, not the end, and it still didn't work. <sigh>

If my perfectly normal out-of-the-box Mandrake installation (plus the Sun JRE) worked fine with LimeWire 2.3 and not LimeWire 2.4, then I think there is a bug in LimeWire 2.4. :(

Maybe I'll try the installer version... The only reason I didn't use it to begin with was spyware fears...

Re: Re: Additional Note
 

we can simply put /usr/java/j2re1.4.0/bin at the beginning. It really needs the path pointing to the bin of the java installation. Creating JAVA_HOME is created only to make it easier to change java versions on the fly at the commandline for purposes such as mine. You can simply set that into your path stateeent pointing to the "bin" and then log out and then back in. That is the best sure fire way to activate and use the changes as they are not always going to be used by simply opening up a new terminal or different terminal window when you are in a window manager. As it may not take effect simply because you may have already used an instance of that window prior to the changes. I had similiar effects until I did that. It is guaranteed to work.

altoine

This is weird. I download the tgz version of Lime since the bin version gave me java error when I try to run it. When i run the tgz version sh ./LimeWire.sh it gave me this post's java error but then I use java -jar LimeWire.jar then the whole program comes up and run. Oh well, I just have to remember to use this command line from now on.

Something Else to Try
 

Try to run runLime.sh instead of LimeWire.sh.

sh runLime.sh

HTH

altoine