I miss the connection changing feature. Helps to conserve bandwidth, or increase number of hits if your doing a search for a rare piece. I'm getting much fewer results because LW defaults to 3 connections... any way to raise this?

No. Although increasing the number of leaf-ultrapeer connections increases the number of search results *you* get - it reduces performances for everyone else. Once there are enough 2.9 ultrapeers out the number of results you will find should increase very much.

Just a quick update on an earlier problem. This time a single LW 2.9.0 on the G4 stopped Web, mail and gnutella access on the G3: (interrupted Acquisiton .74 downloads). I only had to quit LW to regain mail and web access.

Luckily, this didn't break my Acq. hosts, but did interrupt three active downloads.
Acq still shows uninterrupted uptimes, but the active downloads stalled, and haven't yet restarted 30 mins later (cache entries are being written, though, and new searches are giving new results).

More irony, though. This happened while getting the Limewire FAQ link for another post and I only fired up LW on the G4 to check the keystroke for Audio contextual menus (and searched for "canon" to see song results)!

No Console entires noted on the G3; G4 Console wasn't running.

Were you running as an ultrapeer while that happened?

I think I've found something but it doesn't seem to be related to ethernet downloads but to searching while you are an ultrapeer.

This is what happened: When running LimeWire in ultrapeer mode a search, when I start it, might cause all connections to be dropped. So far it appears to be some weird synchronization problem that keeps connections from being initialized properly after I started a search. Disconnecting LimeWire and connecting after several seconds solves the problem.

I'll be able to tell you more in an hour or so.

Don't know. Only had it up for a few minutes, and yesterday the G4 kept to three connections. The few files didn't show as ethernet either (I did remember to scan the IP's). If yesterday's logs are any help, feel free to grab them.

Did the search drop affect any other machines?

Thanks for the info--maybe I can stall on fiddling with IPNetRouter.

Just reproduced the bug. Yes, the G4 was trying to be an UltraPeer. No Console entries, though. I'll give up my Acq. UltraPeers (uptime >15 hrs), and see if it just affects the browser on the G3.

I'm not able to reproduce the bug reliably, so I can't tell what causes it. - It doesn't seem to be too bad on linux and it didn't cause any weird network activity either.

The problem went away after a minute or so...

Yeah, I tried again a few times with and w/o Acq.
Couldn't reproduce the same behaviour when Acq G3 wasn't running: Instead, Limewire G4 as UltraPeer crashed after Acq started up (logged--130+threads; no Console), but no web or mail loss--I tried. Restarted Limewire while Acq still running, Limewire went into leaf mode and I haven't been able to make more problems since. Quit Acq on the G3, and tried twice more to get Limewire in Ultrapeer mode--it's behaving.

Looks like two clients trying to hold down quite a few connections is needed first for me. Explorer was running on both machines too. Oh well, another weekend not wasted.

use limewire on the g3 & g4. i dunno what could be going wrong with acquisition, because i don't know how he's modified certain things. i assume in no instance you had both programs running on a single machine, because that is just asking for a crash.

if the problem's related to acquisition, i'm not sure how much of a help i can be.

Right. I'll see if I can reproduce it again later this week if it's still unsolved.

Yesterday was all Limewire--I just ran Acq last night to get a sense of the differences and was pleased with the stability of the connections, so let it run all day today on the G3 (my main machine). As I said, it was a fluke I triggered today's crash. Someone asked a question about Limewire, so I started it up on my wife's G4, and that triggered the discussion above. I might try running them together for personal curiousity, but I fully expect that to bring trouble.

Don't worry about helping me--afisk did the right thing by posting this release as alpha. If these bugs help you and other developers come up with better Mac clients, I don't mind testing what I can. I do appreciate the expertise you and trap_jaw freely offer.

Were you able to get hold of the logs? If the iDisk isn't efficient, just email me at stief1@mac.com. I'll dump today's limewire.crash.log in there too.

Cheers, and good luck with this week's developments.