Thanks a lot. Its not a deadlock or a selector problem, but the good old SP2 connecting socket limit. We'll see how we can go about fixing it.

If you feel like more testing, could you try patching your system to disable the limit? Its ok if you don't - we're 99.99% sure this is the culprit.

Thanks Jum, you've been very helpful as always!

Well, the patching of these core Windows components sounds scary enough to not do it in my current situation as I do not have my XP install disks around if I happen to mess things up.

We have some changes in CVS that should alleviate the issue. Wanna give'm a try? ;-)

Oops, I did not see any commit email for two days, did I get dropped off the lists somehow?

Why is there now talk about people patching their operating systems? I thought this had been established to be a Limewire problem, not an OS problem, seeing as how it doesn't affect anything else -- web browsing for example works fine even while Limewire is spazzing out dropping connections, refusing to reconnect, or whatever.

Also, I definitely have the problem, and I have a fully up to date XP home system -- all official patches and bugfixes applied as of this morning in fact. So I don't see how it can be a patch I've failed to install given that I haven't failed to install any patches at all.

Some of the people who post in this forum have been submitting patches, testing betas, and doing other helpful things for the better part of two or three years. It's not unjustified to patch the OS to determine if that is the cause of the problem. Sure, it'd be unreasonable to expect everyone to run a patch, but it's certainly useful to ask a friendly beta tester if they can do it to see if it pinpoints what we should look at to fix the problem.

Well, you've got your answer then -- my own system is fully up to date on patches, but the problem still occurs, so it looks like an out-of-date OS setup isn't the cause.

This is actually a slightly different "patch", an unofficial one that actually reverses an official one from Microsoft. There's more info available through google if you're interested.

Are you telling me that Limewire 4.9.x requires that you NOT install an OS patch in order to work correctly? And that to make it work correctly you have to muck about with system files installing files of dubious trustworthiness? Who's brilliant idea was this? Limewire should work with the OS fully up to date -- period.

Shinsengumi, as my first response to you said, the suggestion was done so that we could pinpoint what was causing the problem. We do not expect, nor want, every LimeWire user to install the patch. We would, however, like a helpful beta tester who is experiencing the problem to let us know if this fixes it. If it does, then we know exactly what is causing it and can look into ways of fixing it.