In some cases when trying to start LimeWire 1.6d after install & first launch one can get the error:

java.lang.ClassNotFoundException: a.a.a.b.Main

This is because the LimeWire Starter - "RunLime.class" - is looking for its Main class (!) in the "limewire.props" - File, which is plain text with varios settings. Here the first two lines:

#
#Fri Aug 24 15:33:06 CEST 2001
MAIN_CLASS=a.a.a.b.Main

Strangely enough, you get this line anew every time you exit the program (thus making the next start impossible). More on, if you unpack both .jar archives, there still isn't any "a.a.a.b.Main.class" ! Should ask the developers why the hell this is put there...

Attention!: Assuming the Java class naming convention "a.a.a.b.Main.class" must be in the file "./a/a/a/b/Main.class" (linux - alike)

One Solution could be to delete (or better comment - '#') this statement, then LimeWire starts, but needs more time to launch.

There is still a better Solution:

If you unpack both:
collections.jar and LimeWire.jar (WinRar doess it too)
and search the resulting folders for "Main" - in the presumption that a java proggy should start in some "Main" class - there are following "Main" classes:

./com/limegroup/gnutella/gui/Main.class
./com/limegroup/gnutella/gui/MainFrame.class

To put any of those in the "limewire.props" file, you should change the folder structure (see above) to:

com.limegroup.gnutella.gui.Main
com.limegroup.gnutella.gui.MainFrame

And see, the first one does it well!

However, I kindly suggest the responsible Developer to take a closer look at the sources, in order to avoid this problem.

Your UncleVan.