No... there's nothing wrong with the LW site. It's just fairly common for people to get confused and download a production version instead of a beta.

Hmm--I'm confused. After you posted I checked LW's site, and the release version is listed as 4.10.5, and the beta links had been removed from the download page and the Pro page.

I guess zab moved 4.10.5 into production either on Friday or this weekend. I was actually out sick on Friday. I didn't expect this to happen until early next week, but the beta was looking pretty solid.

The poster's confusion over the version number that he downloaded doesn't give me confidence that he found his way to the beta download page. (Finding the beta download page can be a little tricky. The regular download pages have nice big red buttons to click, while the beta has a grey button to click. This helps prevent people from accidently downloading a beta.)

We were racing the G5 iMac against the Core Duo iMac on Thursday, comparing LW startup speed and gui responsiveness on the 4.10.5 beta.

I just now downloaded the latest LW to check it out... and it looks like Mac JNI libraries we're shipping somehow got "thin" (only PPC code) while the Mac libraries in cvs are still "fat" (PPC and i386 code).

If you're familiar with the Mac command line, the following command will tell you if the native libraries support the Core Duo Macs:

lipo -info /Applications/LimeWire/LimeWire.app/Contents/Resources/Java/*.jnilib

The output should tell you that each and every library has both PPC and i386 code.

I'm working to get to the bottom of this, but I was out on Friday, and it's 4 a.m. Sunday morning here. I'll keep you posted.

Update: "lipo" on OS X Panther doesn't appear to detect fat libraries. Rogerk assures me that the libraries didn't magically get thin.

On a side note: why does Apple ship a version of lipo that doesn't detect fat libraries? I thought that was the whole reason for calling the tool "lipo".