I wanted to follow up on the ultrapeer thing. I turned off the ultrapeer in the speed section of the preferences. I am running the latest version of the OS, 10.1.5. I am now at almost 24 hours running LimeWire with no crashes. Upload activity seems just as active as before, so that is the end of the ultrapeer experiment for me. I'm still not sure what useful purpose it serves.

At this point I would find a "browse host" option much more of a worthwhile option than one that causes the program to crash.

Maybe "ultrapeer" should be OFF by default, and then explain to people what it does and allow them to turn it on at their own risk.

Since I began to use OS 10.1.5 with Limewire 2.4.4 I cannot maintain a modem connection for more than a few minutes. I've been using OSX and LimeWire together for several months with out much trouble untill now. I'm going to try turning of ultrapeer .

I want to follow up, it has been 10 days since I turned off the ultrapeer capability. My LimeWire has not crashed since then. The LimeWire folks sort of pooh-poohed the idea when I presented it to them, but for me the proof is in the check mark: Disable ultrapeer capability!
Mine is not a modified install of OS 10.1.5. Applications are in their proper place. My drive is partitioned with 9 and 10 separated. I run Disk Warrior, fsck, MacJanitor and XOptimize regularly. I have so far had 3 kernel panics in over a years worth of use. I do not install a lot of junk, just major league apps, well, if you consider Microsoft major league (but I'm not going there, just trying to make a point).
Maybe when 10.2 comes out and Java finally works right one of these days, LimeWire will happily run in the background while we do all the other things we want to do. For now it's still a tradeoff though. Yes, I have eliminated the crashes, but I still have to deal with frozen mollasses like browsing speeds if I surf while sharing. Not good. Anything I can turn off for that?