just wondering if there's a way to link the "/foo/LimeWire/sh runlime.sh" command to a desktop shortcut in KDE. i've tried all the stuff i could think of (granted i'm a newbie) but i can' t seem to get it to work. I must say that the install of 1.6 went very smoothly and very easily by the way and the program loads nicely on my k6-3-450 machine.
Thanks

Desktop shortcut means an 'Icon' or a 'keyboard combination' like CRTL_ALT_Backspace ?

Adding an application is quite simple (out of my head): From the KDE-Menu, click configure panel -> add application -> old program
In case you start LW via the jre, choose the jre in /usr/java/where_it_is
on the next tab, add the command line entries (something like -cp /opt/LW RunLimeWire)
...select a nice icon...thats it

I've been trying to do this forever. A link to the application does not work. Whenever I click on the link, it just times out and Limewire does not appear. Limewire however, runs great from the terminal. And yes, I'm sure I made the link correctly (i think) :P

i'v e got several icons here and there that look pretty cool 'cause i chose a cool graphic, but none of them will start limewire (they don't seem to do a [inapropriate language deleted] thing as far as i can tell)

sorry about the language - i didn't think what i wrote was terribly vulgar but i'm not in charge around here. i'll try not to use similar language in future posts.

http://www.gnutellaforums.com/showth...=3328#section2

more precisely: A 2-8

Use the solution in the FAQ (section 2-8) or you can try the shell script I wrote for my own use. My script does two things. It lets you run LimeWire from anywhere (desktop icon, menu icon, any directory in a terminal, whatever) and, to make LimeWire behave like other unix programs, it creates a .limewire directory in your home directory for LimeWire to write it's configuration files to.

My script is attached. It works brilliantly for me but I've only tested it on my system (RedHat 7.1, KDE2.2, LimeWire1.7, JDK1.3.1). It should work on most systems out there. Give it a try anyway. :-)

To install:

1. Go to the LimeWire directory and backup the old runlime.sh with: mv runlime.sh runlime.old

2. Copy runlime.sh.txt to the LimeWire directory.

3. Rename runlime.sh.txt to runlime.sh with: mv runlime.sh.txt runlime.sh

4. Make it executable with whatever permissions you choose. e.g. chmod 755 runlime.sh


That's it! You can now link to the new runlime.sh script however you like. Note however that because the configuration will now be stored in the ~/.limewire dir, LimeWire will ask you to configure everything as if you had just installed it. By default everything (Shared dir, Incomplete dir, gnutella.net, etc) will be under .limewire in your home directory. If you don't want your Shared directory to be under ~/.limewire make sure you change this when LimeWire prompts you to.

[Update: Feh, I found a bug. Script didn't work when you ran it from the limewire directory with ./runlime.sh. See next post for the fixed version. :-) ]

A replacement runlime.sh. See previous post for install instructions.

Attached Files

runlime.sh.txt (424 Bytes, 350 views)

oh, even more simple : you have to be in the limewire directory for Limewire to work. Your shortcut doesn't put you there. Well then, I edited runtime.sh and added a

cd /home/(whatever path to your limewire dir)

just after the text and before

J2SE_PREEMPTCLOSE=1; export J2SE_PREEMPTCLOSE

hard to make more simple ?

Yes, it does. The script is generic. It'll work no matter where LimeWire is installed. The line:

cd `dirname $0`

Changes to the LimeWire directory. The $0 variable returns the command used to execute the script. Then the script changes to ~/.limewire so limewire will write it's config files there. The idea is that you can install the LimeWire .tgz under /usr/local as root and then allow multiple users to run LimeWire with multiple configs.

If you run the script with, say:

sh runlime.sh

Then $0 won't refer to the limewire directory. Run it like ./runlime.sh or /usr/local/LimeWire/runlime.sh. Or, as you suggested, write in the directory names manually. :-)