Hi anon

Sorry to hear about this bug again--looks like you've made a more than reasonable attempt to track it down and fix it. I guess you already emailed the Console entries, contacted Pro Support, and have seen the links to the past versions of LW.

In the meantime you may want to give Jens-Uwe Mager's most recent build of LW a try: it includes the latest CVS changes (3.6.7).

btw--don't worry about the number in the connections list: that depends on whether your code calculates if it's better to run as a leaf or an Ultrapeer--searches and transfers are basically the same under either mode.

If you did a really clean install by searching and trashing the preferences folder (if you used a really old LW before, also search for invisble files containing "limew"), you'll always start out as a leaf until you build up whatever stats are needed (like uptime, bandwidth, and the ability to accept incominng connections) to determine if your connection is suitable for an ultrapeer. Sometimes, after running for a couple of hours, if you choose disconnect, and then connect, you can help regain Ultrapeer status.

btw--have you tried creating a new Admin user and installing LW there? That's the best way to isolate User set-up problems. A second idea is to reinstall Java with the stand-alone updater from Apple. That used to solve some java problems for me.

Do post back if something works--looks like quite a few will be grateful.