I have been using Limewire 1.4 for months and have had no problems at all.
A few weeks ago I took the bait and installed OSX, then Limewire 1.6d.
Since then, I have been having trouble maintaining connections. With OS9 and 1.4, I would have 4TB to 30 TB of files within 60 seconds.
Now, it takes up to 15 minutes to get 4TB-8TB, and as soon as I download (the downloads work fine) a file or two, the connection(s) drop to 150 megs or so. I set the connections for 4, and my TTL to no more than 5.
I'm running it on a 350 G4 with 700 megs of memory, and an ISDN 128 connection. If I maintain 2 connections for an hour I'm lucky. Any suggestions? Thanks!

First let me say that I am Limewire fan. Back in my stupid-days I used Bearshare which worked fine, but I am furious that about what Bearshare does to your operating system without permission. (When you install Bearshare, it permanently alters your Windows registry, throwing out everything that should be there except for about 3 or 4 items. When my volume control disappeared on the fourth computer I installed it on, I finally traced the common thread back to Bearshare, but it was way too late) DON'T INSTALL BEARSHARE!

To get back on track... I upgraded my Limewire to 1.6 as soon as it became available. It works well and I am quite happy with the latest version. Most notably I like sending it to the tray so I can forget about it and let others share from me all they like.

I do however want to report a small bug. (It's good to report small bugs because that means that there are no major bugs to worry about). On the Monitor tab, I click once to highlight an item that has somebody either downloaded, is downloading, or attempted to download. But before I even have the time to move my mouse to choose what action I want (Kill Selected, Clear Inactive, or Options...), the item always UN-highlights! This makes it impossible to actually use the "Kill Selected" feature since you don't have enough time to click that button after you highlight an item (and don't even try highlighting multiple items).

Now one multi-part request for version 1.7 or 2.0 (whichever is next). First, you should have a "launch limewire when Windows (or other OS) starts". This should only be recommended for those with "always on" connections to the internet. Second, that feature should have an additional option to start minimized in the system tray. This will greatly increase the number of hosts sharing files.

Thank you Limewire

The new version does not seem to work at all.
After installation, the desktop icon points to:
-cp . RunLime
double clicking produces no response. There does not appear to be an exe file in the installed directory.

I posted a reply earlier about what I thought was a difference in LimeWire involving kde and Gnome. I think I've actually found it's a difference between Mandrake and Redhat, while LimeWire runs normal on RedHat it does not on Mandrake.

I would like to see LimeWire ported to FreeBSD.

and kde, etc.....

Seems that alot of people are haveing problems with this Java error myself included! Do we have a patch to fix this problem???or can limewire post a link so those of us that didnt have a problem with the last version can get that copy back????thanks for the time... Jerry

anyone know where I can get a linux verison of LimeWire 1.4x?

FreeBSD only has linux's j2sdk-1.3.02 ported at the moment.

I'll try to respond to as many people as I can here.

To the original user posting about sharing the entire hard drive, I cannot think of any reason why LimeWire would be listing 16 files as shared when you only have on file in that directory unless you are also sharing a second directory.

To the OSX user seeing reduced horizon statistics -- these numbers are only there to give you a rough estimate of the files available, and they do not accurately reflect the true state of the network. I would not use them to determine the quality of your connection.

For the user who posted the suggestions and bug reports, we will likely do all of these things at some point. The bug in the Monitor tab will definitely be fixed with the next release, and we will add the option to run LimeWire at startup at some point. The only thing that is tricky here is to detect that LimeWire is already running when the user starts another one. Should that start a second LimeWire, or should it detect the original one running and simply make it visible?

Ed- is the target of the shortcut only:

-cp . RunLime

or does it also include something like:

C:\System32\javaw.exe -cp . RunLime

(Does it include something like the first part with javaw.exe in it?)


As far as LimeWire for FreeBSD, LimeWire 1.6d should work fine with Java 1.2 and higher, so there should not be any problems with the current version of Java available for FreeBSD.

__________________
Adam Fisk
LimeWire Developer

I got LimeWire 1.6d working with FreeBSD!!! :]
I just had to install the linux-jdk13 port and switch java to javavm in runlime.sh

I'm running Java 2 RE, SE 1.3.0_02

I downloaded 1.6 and saved it to the folder where 1.4 was. Version 1.4 was over written and 1.6 doesn't work. Clicking on the desktop icon does nothing. Shortcut target is

C:\WINDOWS\SYSTEM\javaw.exe -cp . RunLime

Maybe the RIAA created a non-working Limewire prgram, secretly set up this site, and is merrily watching the installed base of users steadily drop.

Guess it's back to Morpheus