The core code is entirely cross-platform (it's Java, after all). Your statement is entirely wrong.

Btw Porfiry, when are you gonna limit the number of connections to ultrapeers to 3? LW2.9 users can't change that anymore and with dynamic queries it's stupid to waste ultrapeers connections. AFAIK, 6 connections is better than 3 for the user as of now, but in two months it should not change the number of results.... An OSX limewire user...

It'll drop to 3 when LimeWire 2.9 is widespreaad enough to allow it. I'm taking enough flak as it is for reducing it to 6. If I went to 3 immediately, I'd have a full blown insurrection on my hands.

Glad to hear it Porfiry!!! I understand that newbies don't know the basics and for them less results can be explained by less connections, but they will be proved wrong in the next months... (yes I know that the results are limited by the program, but rare things will be easier to find)

Porfiry, I just updated to the newest release of Aquisition, and I have a major issue with it that wasn't a problem with the previous release:

The network would not connect to ANY peers.... I have left this on all night and by morning still nothing connected. I have tried restarts, re-initializing my cable modem, and resetting the DHCP values in the network control panel. I can connect to the web with ease, use msn, yahoo, and ICQ messengers without any problems, so I don't understand the problem with aquisition. Yes, I did check the preferences, and I have the number of connections set to six, and I could not find anything else out of the ordinary....

- Help! I am P2Pless right now!

0.801 isn't the latest release. 0.802 is, and I suggest you download it.

Ok Ok, so release 0.801 lasted less than a day, that's cool. so I've updated my system with the release candidate of Java 1.4.1 via automatic update, and updated to Aquisition 0.802, and now I get network connections, but none of my searches yield ANY results, for stuff that should come up even with the fewest files available per server, like norton, adobe, microsoft, or eminem.....

By the way, I tried the 2.8.6 release of Limewire with Java 1.4.1 and there is NO change in it's behaviour compared to before.

you're right--looks like a few weeks before LW will link to 1.4.1. I read that one of the team is working on a OSX box fulltime now. Hope they can find an alpha tester to help out with the Classic version. Know anyone who might be willing?
btw--2.9.3 ALPHA looks to have fixed the "could not move" problem.

That's because you never actually tried Limewire 2.8.6 with Java 1.4.1.

Unless, of course, you edited the "Info.plist" file inside the "Limewire.app/Contents/" folder by changing the value of "JVMVersion" from "1.3*" to "1.4.1", "1.4*", or "1.4+".