limewire 1.7 ClassNotFound error

I just installed JRE1.3.1 and LimeWire 1.7 on an NT4 box.

Both appeared to install correctly.

When running the shortcut to LImeWire1.7, I get the error:

java.lang.ClassNotFoundException:com.limegroup.gnu tella.gui.Main

The LimeWire shortcut points to:

E:\soft\JavaSoft\JRE\1.3.1\bin\javaw.exe -cp . RunLime

javaw.exe lives in the path stated, and RunLime.class is in the LimeWire directory containing the shortcut.

I don't know enough about windows (or java) to debug this problem. Any suggestions?

Many thanks, Chris
chris dot wallace at lshtm dot ac dot uk

[afisk]

Do you see the file called "LimeWire.jar" in your install directory? Also, can you attach the "limewire.props" file that should be in your install directory? Thanks.

LimeWire.jar exists (592K) in the install directory (e:\musicsoft\LimeWire)
limewire.props is:

#
#Tue May 15 13:36:55 EDT 2001
DIRECTORY_FOR_SAVING_FILES=e:\\musicsoft\\LimeWire \\Shared
DIRECTORIES_TO_SEARCH_FOR_FILES=e:\\musicsoft\\Lim eWire\\Shared
SAVE_DEFAULT=e:\\musicsoft\\LimeWire\\Shared
CONNECTION_SPEED=1000
MAX_UPLOADS=8
MAX_SIM_DOWNLOAD=12
INSTALLED=true
CLASSPATH=LimeWire.jar;collections.jar
MAIN_CLASS=com.limegroup.gnutella.gui.Main

Many thanks, Chris.

[afisk]

That is very strange that you would be getting that error. Does the "Start in" value of the properties of your shortcut correspond to the directory where you installed LimeWire?

It definitely sounds like a classpath issue.

You could try changing the shortcut target from:

E:\soft\JavaSoft\JRE\1.3.1\bin\javaw.exe -cp . RunLime

to:

E:\soft\JavaSoft\JRE\1.3.1\bin\javaw.exe -cp .;collections.jar;LimeWire.jar com.limegroup.gnutella.gui.Main

(that should all be on the same line, the window may have wrapped it, however).

That should probably work. Also make sure that the "start in" directory for your shortcut corresponds to your LimeWire installation directory. If it does not, try only making that change before making the change above. If that does not work, include both changes.

Many thanks. This worked. Though I'm unclear why, because the 'start in' directory did indeed point to the installation directory. Odd.

Thnx, Chris.

[afisk]

Chris-

Glad to hear that worked. I am not entirely sure what was causing this problem. The only word of caution that I have is that, with this configuration, you should not use the automatic updator, as it will not work. So, if you get a message in the future saying that there is an update available, you should simply uninstall your current version and download the new one from the web site, as the automatic update simply will not work.

I'll give this one a little thought for solving it in future versions. Thanks.