Quote:
Originally posted by Unregistered
Greetings, OP again.
I did exactly what you suggested: added an environment variable JAVA_HOME for my jre directory (I don't have the sdk) and made sure it was in my path. LimeWire still doesn't work.
I don't see why the change you suggested would have worked anyway, since I can still run LimeWire 2.4 manually with the java command; it just produces a million error messages about missing files and fonts (which were presumably supposed to be bundled in the tarball). If LimeWire really couldn't find Java or the standard libraries, it probably wouldn't have started up at all.
Have you or anyone else actually gotten the 2.4 tarball to work? |
I asked myself the same questions. That is why I downloaded the cvs to investigate it for myself. I will run a "diff" between cvs and version 2.3. Surprisingly, the suggestions that I gave, short of the experimental tcsh suggestions worked for me and others with their default user accounts using bash. Isn't there a way for you to try bash and then implement my suggestions from my link? I have just finished reconfiguring all of my distributions on my computers with the exception that I have gentoo and Linux From Scratch left to change. I had them all pretty much optimized as multimedia systems but because of my intensive involvement with developmental software, I had to make some drastic changes from repartitioning my drives to reconfiguring scripts. Under bash, all my distros rock. Red Hat 7.3, Mandrake 8.2, Mandrake Cooker, Linux From Scratch, and gentoo. I will have answers for you within a day (I hope) of why my suggestions work at all, let alone why they are necessary. One thing I do know for certain, they work 100% under bash as I have not been told different.
digging deep,
altoine