R
RJ
Interesting things spotted on a quick overview read of all comments
at the SANS XP SP2 page:
http://isc.sans.org/xpsp2.php
1.. It appears SP2 doesn't like the Prescott chip, AT ALL. Almost everyone with critical problems
was running a Prescott. (One suggestion by a poster was that Intel's NX technology is glitched, and
thus is not allowing the boot code to finish running.)
2.. Those with "issues" seemed to find these cleared up either with a fresh install, followed by
SP2, or by installing a version of XP that was slipstreamed with SP2. The problems might have been
caused by something running in memory (an uncaught virus, or spyware?).
3.. Recommendations are very, VERY firm about running a full antivirus scan, followed by a scan
for spyware (and other malware) before doing an install.
4.. Some drivers need to be re-installed, especially for devices using USB.
5.. Most all other "issues" were with programs that needed to be added to the Windows firewall.
Don't use the Windows Firewall. It is rather useless. Use a firewall such as ZoneAlarm.
6.. One major problem (for some) was the port speed limitation that Microsoft added. In other
words, if you have a single program that opens more than 10 simultaneous connections (Ie, some of
the newer file transfer protocols, or NMap to test your system for vulnerabilities), Microsoft
automatically limits the thru-put to around that of a 1200bps modem. Under normal conditions, you'll
never see this -- but if you try to run NMap (or other software that opens a TON of connections
simultaneously), you'll see this -- fast."
As always, Windows Service Pack installs require homework and testing. You could be one of the
lucky ones that downloads, installs and voila, no problems. But do you want to take that chance?
Do your homework. Send the bill for your time and effort to Microsoft Corp.
at the SANS XP SP2 page:
http://isc.sans.org/xpsp2.php
1.. It appears SP2 doesn't like the Prescott chip, AT ALL. Almost everyone with critical problems
was running a Prescott. (One suggestion by a poster was that Intel's NX technology is glitched, and
thus is not allowing the boot code to finish running.)
2.. Those with "issues" seemed to find these cleared up either with a fresh install, followed by
SP2, or by installing a version of XP that was slipstreamed with SP2. The problems might have been
caused by something running in memory (an uncaught virus, or spyware?).
3.. Recommendations are very, VERY firm about running a full antivirus scan, followed by a scan
for spyware (and other malware) before doing an install.
4.. Some drivers need to be re-installed, especially for devices using USB.
5.. Most all other "issues" were with programs that needed to be added to the Windows firewall.
Don't use the Windows Firewall. It is rather useless. Use a firewall such as ZoneAlarm.
6.. One major problem (for some) was the port speed limitation that Microsoft added. In other
words, if you have a single program that opens more than 10 simultaneous connections (Ie, some of
the newer file transfer protocols, or NMap to test your system for vulnerabilities), Microsoft
automatically limits the thru-put to around that of a 1200bps modem. Under normal conditions, you'll
never see this -- but if you try to run NMap (or other software that opens a TON of connections
simultaneously), you'll see this -- fast."
As always, Windows Service Pack installs require homework and testing. You could be one of the
lucky ones that downloads, installs and voila, no problems. But do you want to take that chance?
Do your homework. Send the bill for your time and effort to Microsoft Corp.