Limewire Pro 4.8 won't work with OS 10.3.8

[Patriot787]

I have Limewire Pro and I updated to 4.8 Pro. Evidently it doesn't work with Max OS 10.3.8. I took the suggestion to download the Java Update 1.4.2 Update 2, but when I tried to install it, a dialog box comes up that says that the current version of Java on my hard drive does NOT need to be updated!! So now I have a non-functional Limewire Pro, which I paid for. I would go back to the version that I had before, which worked perfectly, but I'm not sure if this is possible! Please help!!!

[Lord of the Rings]

Did you download the Standalone installer or try to install Java over the net? The point is, yes your system already has it but it may not have installed correctly! Try it!

If that doesn't fix it then delete your LW preferences folder whilst LW is closed. It can be found here: /Users/your_username/Library/Preferences/LimeWire

I had similar problems with Limewire not working, and just blinking.

I solved my problem by doing the following:

1. Deleted all references to Limewire as described in previous threads.

2. Downloaded and installed the following version of Java for Panther:

http://www.apple.com/downloads/macosx/apple/java.html

Like you, I tried Java 1.4.2 and was told that I had the most current version of Java. You will be able to install the Java for Panther.

3. Reinstalled Limewire.


Hope that helps,

Ralph

[Shadownature]

What I'd like to know is if this version has solved the virtual memory consumption issue. Want to know before I wipe my hard drive to fix my everlasting "ZeroKB available" problem. Don't want to do it repeatedly you understand.

*Cups a hand to his ear hoping to hear good news from the community*

[Sonica]

ok so i downloaded the update for java from the link above ^^^, but limewire still does the bouncy thing. no only does this happen with just limewire, but also a couple other apps i have, including firefox and cyberduck. help?

[stief]

Originally posted by Shadownature
What I'd like to know is if this version has solved the virtual memory consumption issue. Want to know before I wipe my hard drive to fix my everlasting "ZeroKB available" problem. Don't want to do it repeatedly you understand.

*Cups a hand to his ear hoping to hear good news from the community*

Sorry--not yet. I suspect we'll have to wait for the Java 1.5 release for OS X

(Sonica, have you tried deleting the Dock prefs? ~/Library/Preferences/com.apple.dock.plist )

[Shadownature]

Originally posted by stief
Sorry--not yet. I suspect we'll have to wait for the Java 1.5 release for OS X

Booooooo!

Oh well. You wouldn't happen to have a good guess when that is, would you? As much as this screwed up my Mac, I still want to continue to use Limewire. It's a good program.

[stief]

no idea--perhaps when Apple releases Tiger?

I agree that LW is still worth supporting--the project has really come a long way, and the developers are quite supportive of the Mac and open source standards (unlike some greedy individuals who leech off LW's development).

btw--I stopped the rising VM in this graph by clearing all incompletes and then clicking LW's close box. I haven't had the hard drive thrash for long periods of time either, probably because I started with 5 GB free space. Maybe that will work for you?

[Shadownature]

Originally posted by stief
btw--I stopped the rising VM in this graph by clearing all incompletes and then clicking LW's close box. I haven't had the hard drive thrash for long periods of time either, probably because I started with 5 GB free space. Maybe that will work for you?

I doubt that would work as my problem is it seems the VM is on, but Limewire is not. Or some file has taken up space and not being registered as a file. This doesn't seem to be the case of others as I've read.

I had found a 5 GIG console log file and deleted it after trying to read it to see what it was (freezing and forcing reboot). I had made a topic on with what little information I had. X.3.8 + LW 4.4.5 = "Data Flooding" I'm pretty sure I'm screwed and will need to back-up and reinstall.