I'm using LimeWire Pro under Java 1.4.1 and I have a consistent problem where I connect and files start to download, then without warning, I get the message that I have no connection. I can turn my cable modem (RCN) off and on, but it doesn't reconnect. I can also reboot or turn the computer off and on and no go. It's only when I turn the computer and the modem off (turn off the UPS), that I can reconnect. Anyone experiencing anything similar? I'm running eCS 1.2 (OS/2).

Can you give us a total desciption of your set up:
1. What version of Limewire (LW)? (Go to LW's menu Help>About LW...)
2. What firewalls you have?
3. ram?
4. HDD space available?
5. Connection type? (eg: dialup, broadband, cable, etc.)
6. Modem & router brand name & model numbers?
7. Where are you trying to connect from (home, school, work, etc.)?
These details are vital if you want us to find out what your connection problem is.

1. LimeWire Pro 4.4.5
2. None (Except any cable ISP RCN may have)
3.. 640 Meg memory
4. 20 gig
5. Cable (RCN is ISP)
6. Motorola SurfBoard Model SB4100
7. Connecting from home

The key for me is that I have no problems (drops) with normal surfing using Netscape, Firefox, Thunderbird, Mozilla, etc. If I get dropped by LimeWire and I shut everything off and restart, I can get back on with Mozilla or LimeWire.

I am using Innotek's Java 1.4.2, but I'll be switching over to Golden Code Java 1.4.1 as soon as they mail me the disc, to see if that make any difference.

Thanks for any help.

I hope THIS (click on link) does not apply to you. Do you use USB connection? If you have a choice use the ethernet connection. It's much more reliable than usb. Go here & scroll down to 3.4 USB-based modems/routers

Do you use the Resume button on all your downlds to continue them after opening LW? Doing so will put great stress on LW & have side-FX of upsetting LW's connection quality & use up much of your comp's resources as well. And it can also drain your main connection.

No, I do not use a USB connection to my modem. It is ethernet.

No, I don't use the resume button. I will occasionally use the search for more connections. LW seems to spend a lot of time idle i.e. the files are in the list, but not downloading because it needs more nodes. Even when I have three or four available connections, the dl'd speed hovers around 1 or 2, although I have seen it go as high as 38 on rare occasion.

If a downld stops or slows to 0 or if I just want to try again with one that won't connect, I'll select it on the downld list, press the stop button. Then I'll re-select it from the search results & press the downld button. I'll try that several times backed up with a new search. That's worked for me since LW2 a few years back. Yes sometimes you need to slave over LW. Have a look at these: HERE & 'maybe' you might pick some useful points up.

For your main problem of losing connection, I'd suggest you drop back your upload bandwidth to about 70/80% or more if necessary so it doesn't play havoc with your connection & you can browse at the same time. With such a connection I'd also disable Ultrapeer (UP) capabilities. Tools>Options>Speed & tick Disable UP Cap. & press Apply.

Also set your downlds to auto-clear. Close any windows you're not using at that time (eg: Connection, Monitor, & LIbrary Windows.) Go to LW menu View>Show/Hide ...

After opening LW, leave it 10 to 20 mins before doing anything. Give it time to load the incompletes & shared files, & try on its own to connect one by one with each incomplete. For different people this can take different amounts of time (even to load the same no. of files.) I share almost 3k files & it takes 10 mins to load them & incompletes on Mac OSX but takes much, much longer on the same computer using OS 9 for half the amount of files. But I still don't use it for about another 10 mins after that. In fact often I'll just turn it on & leave it & check it an hour later to see what's happening. Some of my incompletes often start by themselves whether that takes 20 mins, 40 or 70 mins. The longer LW is on the more stable it is & easier to use.

Unfortunately, leaving LW alone did not cure the problem, however, changing the Java JRE did. I switched from the Innotek Java 1.4.2 to the Golden Code Java 1.4.1 and my problems with disconnecting have been solved. My LW installation under eCS (OS/2) are now resolved. LW Pro doesn't run as well as the native Napster/2 did, but it is definately up to the job.

Thanks to all (but esp. Lord of the Rings) for the help, advice and sleuthing.

Gilbert