Problem with Win XP SP2?

I just downloaded windows SP2, and now my mushclient freezes up at different times. If I type a command, it enters the command, but nothing happens, then about 15-30 seconds later, it loads everything that has happened in that span., then it is active again, only to 'freeze' up in a little bit.

I never had any sort of problem before I downloaded SP2.

Help!

I don't think SP2 is offically released yet, because its still being worked on.



It may be a SP2 problem, not sure. Wait for Nick to reply.

I have the final version, as it was released to beta testers on Friday.

The public release is this week. tomorrow or Tuesday, I am not sure which.

Its obviously a problem with SP2. I thought it wasnt 'officially' released yet.

Anyway, SP2 was known to 'break' a lot of programs (even professional ones). So, apparently MC is one of them.

Has to do with "security" features. It'd probably require a relatively decent rewrite of a lot of the functions MC uses. Or at least, from my knowledge of SP2s changes.

I also believe you wont be able to "uninstall" SP2 (primarily because of its revamp of most of the OS). So, you might be stuck with it and it's broken programs.

You'll have to somehow talk to someone who knows a lot about SP2. The only related issue I've had like this, is my McAfee would freeze MC, when it runs a script, and I'd have to allow the program.

There is one other possibility to consider. I'm not sure if they've gone ahead with it, but there were alot of rumblings awhile back about SP2 turning on the Windows firewall by default. Couldn't hurt to check it.

You also might want to consider disabling the NX feature (assuming your proccessor is compatable). Since this seems to break things with dynamic compilers.

I'm using SP2 and it's working fine for me. I did however turn off the internal firewal... I don't know what to say about that.

I really doubt that NX is affecting MC, because MC isn't a JIT compiler.

The firewall is certainly not affecting MC, because MC doesn't accept any connections.

Incidentally, SP2 is being forcefully pushed onto computers (IE: automatically downloaded) after the 16th.

Hrm..... yet another reason for me never to "upgrade" to XP. What is probably screwing with you is the active scan portion of the patch if you're using any of several antivirus programs that have an active scan function because I've had to fix this "feature" on a number of systems already.

Hah. Yeah right if Im going to have anything automatically downloaded. Maybe if you still have windows update installed/running, but seriously, who does? "Updating" windows is the biggest source of problems.

Its like a 400mb download, Itd be kind of hard to "force" on everyone. Poor dialup people.

And yeah, I agree with Meerclar, try changing different options, If youve got your own AV turn MSs off (seriously though, if microsoft has all these holes in windows, you think their AV is going to be any better?) and their firewall too. The redundancy is probably an issue. And turn off anything else you dont need. If MC is still causing problems, try turning off things option by option until it works, so we can narrow down what the problem is and help other people fix it when the issue comes up.

It's 266mb.

Lets try not to turn this into a MS flamefest, please. It's not warranted.

Incidently, it's not being forced on anyone. The only update that was a required download was SR1 for office 2000, but even then you didn't have to install it if you were ok with missing later updates.

SP2 will be on windows update around then (the 16th) and automatic updates will pick it up, so a lot of people will have it automatically installed, but it's hardly forced.

The entire 266mb won't be downloaded on Windows update. Windows update will download something similar to a "silent web installer", so it will download only what's necessary in the background, assuming you have it set to automatically install.

No need for a flamefest at all and no intention of starting one. It's simply a matter of those that have been in the tech field for any large portion of the last 10 years or so know that 99% of all problems with MS products are caused by "upgrades" and "patches" released by MS. The issues with SP2 are simply another step down a well known MS path.

Here's the likely problem:

Under XP SP2, the number of unresolved outbound connections is limited. If you exceed the limit, outgoing packets/connections are stacked internally until the outbound connections are within tollerance, and then queued connections are resolved in order.

XP SP2 is mostly security upgrades, and this code has been implemented to prevent a computer from spamming the internet, particularly viruses that use wardial like code to search for vulnerable systems, by opening many connections at a time.

For more information, see this link:Note, it is NOT likely MUSHclient with all the open connections, but some other software you are running, like a P2P program, that is hogging all the outbound connections, and thus causing MUSHclient to suffer as it's own connection(s) get delayed in the queue.

Ah heck, here's the relevent text, quoted from the page I gave URL for:

Limited number of simultaneous incomplete outbound TCP connection attempts
Detailed description

The TCP/IP stack now limits the number of simultaneous incomplete outbound TCP connection attempts. After the limit has been reached, subsequent connection attempts are put in a queue and will be resolved at a fixed rate. Under normal operation, when applications are connecting to available hosts at valid IP addresses, no connection rate-limiting will occur. When it does occur, a new event, with ID 4226, appears in the system’s event log.

Why is this change important? What threats does it help mitigate?

This change helps to limit the speed at which malicious programs, such as viruses and worms, spread to uninfected computers. Malicious programs often attempt to reach uninfected computers by opening simultaneous connections to random IP addresses. Most of these random addresses result in a failed connection, so a burst of such activity on a computer is a signal that it may have been infected by a malicious program.

What works differently?

This change may cause certain security tools, such as port scanners, to run more slowly.

How do I resolve these issues?

Stop the application that is responsible for the failing connection attempts.

lol

Since when is making it harder for something that shouldn't be installed in the first place considered a security feature? The point is the prevent malicious software from installing in the first place, not making Microsoft look better by slowing it down so they can claim later that the OS must have been infected less often. This is a bloody stupid 'feature' imho. This is like deciding that you shouldn't be allowed to drive at the speed limit on a freeway, since someone 'may' choose to drive at 60-70 in a 20mhp zone instead. Why not just prevent the car from driving faster than 20mph in the first place? Problems solved right? Sigh... And here I was considering getting a copy of XP, since I have gotten tired of the few truely annoying glitches in 98 and can't run some newer software. :(

Shadowfyr, just dont install SP2, I have no intention of getting it, ever. Its designed for people who download every file they are emailed, and click on every single link on every webpage. And allow all activeX controls on every webpage, and all that other fun stuff.

Personally, I have NEVER gotten a virus email, I get AX popups, but of course, I never allow them.

And I agree, that "feature" is innately stupid, whats the point of having all those ports if you cant use them?

Well.. Some of the problems it fixes go a tad beyond not letting some things run. If you use Windows and IE isn't patched, you can get nailed, plain and simple, though a real firewall would help a lot. Right now this isn't much of a problem, but if I ever get broadband, which is likely to happen once I in fact have the cash to get XP too...

I just think this is an example of how MS 'fixes' problems. Instead of solving the real issues, they merely disable features. It doesn't stop the stuff from installing or slowing down the system, it just keeps it from spreeding. Kind of like a twisted sort of quarentine. The sort of thing you might expect from medieval doctors during the black plague, but not from modern times when it is considered more reasonable to kill the bug carrying the disease in the first place. It isn't the first time they have used such a lame and pointless tactic to solve a problem they refused to find a way to properly fix either.

But yeah. You can just decide not to install it, but that doesn't give you any right to complain when something bites you in the rear that it could have prevented, if not for all the crap you didn't want it to change and wasn't related to the problem in the first place.

It's not like they didn't fix the hole, they're just guarding against future infections. I agree, it is a bit stupid, and there should at least be an option for it, but it doesn't make Microsoft the devil...

I keep seeing people talk about how you can just make it so it doesnt automatically download it. For any completely oblivious reader's out there, you might wish to know how. Its simple.

Get into the control panel (start->control panel on most computers), open up System.

This will bring up the system properties menu. Go to the Automatic Updates tab.

Most computers will be on Automatic, since its the recommended setting. Merely change it to any of the others. Turning off is probably not the best idea in the world, but hey, its up to you. Personally I recommend the third one down (Notify me but don't automatically download or install them). That way you have complete control over what "updates" go on your computer.

Most people could probably figure that out, but hey, maybe I helpped someone.

For Example XP-Antispy can set the Number of max.
connections (in tcpip.sys) to unlimited.

so long, Twrx.