As I promised, I've come back to check out LimeWire 2.9.x

Running 2.9.3 on a G4/400MHz under OS 10.2.4 with 512MB, java 1.4.1, and a 1.5M ADSL line:

1. since moving over to Acquisition, my shared files have grown to 5.2GB (118 files). I knew this would be too much to throw at LimeWire all at once, so I only included my mp3s (0.5GB, 48 files) when I fired LimeWire up. The program became so hung recomputing the SHA1 hash that even Forced Quit wouldn't work. I had to cut power and restart. I tried again with 16 files, same result. Finally I managed to start LimeWire with only 4 files (65MB) in the Shared folder.

2. Once I had LimeWire running OK, I launched System Manager to check program performance -- ye ole spinning beach ball! Again, even Forced Quit wouldn't work. I'm guessing this is the infamous Window Manager bug. In any case, I can't give you any performance numbers.

3. Tried again, this time without System Manager. Did several searches, started a download, then decided to check out any new features: clicked an item in the menu bar -- beach ball, long wait, menu slooooowly pops down. Click an item in the pop-down menu -- beach ball, long wait, item slooooowly responds. At this point I gave up.

Now, I know I don't have the world's fastest cpu, but this is absurd!

I'll try again when 2.9x moves from alpha stage to beta.

And now a question, specifically to Trap-Jaw: you threatened to blacklist Acquisition when you thought Dave had reduced requery times from 45 minutes to 10, but LimeWire continues to display a 5 minute requery cycle. What is this? Just a sham?

Janet