If you start
Limewire for the first time with a new or extensively changed share of several hundred files it will take a long time, possibly over 15 mins to get properly up and running. It seems the time is required to load the file information onto the network.

Starting without major changes to the share, it has just taken a little under 4 minutes, although the "quality" is still sitting on excellent.... It l changed to Turbo charged after another 2 minutes or so, although I am not 100% sure what the difference is!

Mac G3 OSX 10.3.9 Limewire pro 4.8.1 ADSL connection of moderate quality

I 've searched the Java site and do not see where you can download previus versions

Check out the link below it has the link you are looking for in it.


http://www.gnutellaforums.com/showth...threadid=36420

__________________










A little common sense goes a long way

Later Grandpa

Tried all the remedies I can find on these Forums. Switched Java both ways, deleted preferences folder, change user , and on and on ..... and it still runs 100 % CPU and bogs my whole system down. I believe it's time to move on to another P to P .

Beakie a little information would be helpful here.


OS, Windows 98/2000/XP
CPU, P4 3.0 GHz/AMD 64 3200+Ghz
Memory, 256MB/512MB
Video card & platform Radion/Nvidia
Connection, Dial-up/DSL
LimeWire Version 4.8.1/4.9.11
Java Version 1.4.2/1.5.4
Are you using a router, Brand/Model#
What firewall you use if any
What Antivirus if any
Are you new to LimeWire or Experienced
An accurate description of your problem

__________________










A little common sense goes a long way

Later Grandpa

I've found it helpful to give Limewire a below normal task priority if it is slowing things down with cpu hogging. On Windows, you can do that with ctrl+alt+del, find the limewire process in the task manager's process tab (it will be named java, javaw, or limewire), and right click it and choose "set priority", then "below normal". Then answer yes when it prompts you are you sure.

My problem is as previously stated and the same as many have posted before. Limewire takes over my xp system demanding 100% CPU and majority of mem usage thereby dragging a XP3000 and 1 gig of ram to a crawl. I have been using Limewire for close to it's inception and never had a problem until a few months back when I upgraded to a newer version. Just exactly what version it was when it started I never took note of. I have uninstalled and reinstalled every version I can find. Pro versionS and beta included. Also cleaning my registry between installs. Like I said I have tried EVERY solution posted on this forum to this date. Even the hokum update.exe virus revelation. There is no need for me to supply anyone with my system config as I have run Limewire previously successfully on this system and currently run Java dependent (no matter 1.4 or 5) programs with NO PROBLEMS. It would be great if someone who has actually experienced this problem and has a solution that has not been posted previously. Hopefully I will return to using a Limewire version in the future that's code can compete with the glitch.

Hi there,

I am also watching the words appear on the screen in front of me at about 1/4 the rate I'm typing as LimeWire is running at the moment! I started using L/W about a month ago and it's been fine up until a couple of days ago.

Does anyone know if there's a summary of all the info on this thread? I've been through most of it and nothing has made any difference, though I haven't uninstalled any Java versions yet. Be great to know if there's a substantial fix created yet.

My system:

XP2400 1.8GHz 512Mb RAM nVidia

This aside, LimeWire is so great.

Thanks

Nick

Here's another option that may or may not make a difference in your case, go to LW's menu bar, Tools>Options>iTunes>Sharing & disable all options & press apply.

As suggested at the beginning of this thread, having a very large no. of incomplete files & shared files can slow LW down somewhat. For a start, it means it takes LW much longer to settle down after opening. And it's always best to leave LW until it's loaded completely & left alone to try to connect by itself to the individual files before user intervention. As you'll notice, all files are queued after opening, LW will attempt to connect to these one by one. Wait until it's finished before adding more files to downld or using the media player, etc. And try to resist from using the Resume/Find Sources function if possible. If to use it, just apply it to 1-3 files at one times. Dial up users should only apply it to one file at a time. Manual searches are better than this function anyway & better for the network by not sending out too many simultaneous requests & jamming it with traffic. So how else to recontinue files downlding, ... direct connecting & browing of search results can certainly help.
Set your uploads & downlds for auto-clear & closing off search tabs if they get into multiple rows & are hours old can also help to reduce strain on LW. Also closing windows you don't need open at that time such as connection window, library & monitor window. Not ticking the option to view incoming searches in the monitor window can also help. Also not using LW's media player.

Hi Lord OTR,

Many thanks for taking the time to reply. I tried the stuff with incomplete files etc. That didn't seem to help. I didn't get around to trying your suggested fix as it seems to be the case that removing J2SE Runtime Environment 5.0 Update 6 got rid of the problem completely. Guess I should have tried this before.

Thanks

Nick