Feh, sh runlime.sh does actually work! dirname cleverly translates it to '.' the current directory. :-)

Just to clarify something. You don't *have* to be in the LimeWire directory for LimeWire to work. The only reason you start LimeWire from the LimeWire directory when you use the provided runlime.sh is because it only uses the current directory as the class path:

java -classpath . RunLime

If you add the correct classpaths when you're starting up limewire, you can start it from anywhere.

Hang on a second guys, you lost me completely: After installing LW 1.7 i did the following (KDE 2.2.1): Right mouse on the desktop -> create new -> Program
-> Enter program name, choose application (which is /home/your_user_dir/LimeWire17/LimeWire17), select an icon.....(where is the nice LW-icon?)...and thats it!

yeah, great, it works!

I have installed the naked linux program (1.7c without installer). To me it seems that this version requires a script. A simple link to LimeWire17 doesn't work (mostly because this file doesn't exist in the non-installer version ;-) )

And how do you start the 'naked linux program' ?

something like 'jre -cp .....'?

The 'naked linux program' is just a gzipped tar file. It comes with the .jar files and a runlime.sh shell script. You have to run this script in the same directory as the jar files hence the replacement runlime.sh script business. I installed LimeWire this way too and wrote an alternative script for my own use. You can see it at:

http://www.cyberspace.org/~kohl/limewirelinuxhowto.html

The howto was written for 1.7 and probably could use updating now (re where to download). I'll get around to that in the next couple of weeks.

I tried both the FAQ method ("cd [my limedir] && sh runlime.sh") and twist's runlime.sh, but neither work from the GNOME menu. It still starts fine from a terminal though...

When ran from the menu it seems as if Limewire actually starts, connects and scans the shared dirs, but no UI appears! There are about two million jre processes hanging around...

BTW, this is with 1.7c. 1.7b started OK from the menu.

I've just installed 1.7c and it works fine for me from the KDE menu when I use my script. It might be something that the GNOME menu does. But it seems strange that 1.7 works for you and 1.7c doesn't. They start up the same way.

Did you change anything else in your system between installing 1.7 and 1.7c?

Yes, I swiped my entire Redhat 7.1 + Ximian GNOME installation and installed Redhat 7.2 with RH's GNOME.

I discovered that both the FAQ and the edited runlime.sh methods actually work from the menu if I check the "Run in terminal" option in the GNOME menu editor.

In the terminal I always get many instances of this warning

Font specified in font.properties not found [--symbol-medium-r-normal--*-%d-*-*-p-*-adobe-fontspecific]

but that doesn't stop Limewire from running OK, as long as it's started from the terminal or from the menu with "run in terminal" selected.

I still don't want to have an unnecessary terminal window hanging around, so the problem isn't solved.