Quote:
Originally posted by lespaton
Could you educate the rest of us on what this change actually does to XP ??? Since you guarantee it, you must know in detail what is the effect.
|
XP service pack 2 implements a new feature of memory protection against viruses, this stops code being modified that is listed as "Non Execute" in the memory "NX"
now for some people and future systems this isnt a problem, this technology requires a instruction set on the CPU to work properly, otherwise it is done in softeware emulation. Since the only chips so far that has the NX instructions are the AMD64 chips and some P4's i think.
This causes problems on systems running cpu's without the NX instruction set and therfore causes the crash problem we experience.
DEP is the m$ tag line for the NX technology. by default it is turned on and is set to protecting all windows system programs and services. I've only noticed this problem on sp2 upgrades without the hardware NX support, so far clean installs with sp2 and streamlined installations have had no problems. not too sure why this occurs must be how the os has delt with programs in the past and sp2 changes it and ergo the crash.
but since right click is a system command this poses a puzzler
in all sense and purposes, the threat this prevents or helps to prevent isnt live in the world atm its very deep down underground.
for the home user, not having a chip with NX causes an extreme system resource hog and slows down the system / programs and causes more crashes. but thank something your using XP cos if this crash occured in 9x then you would have a blue screen everytime you wanted to do anything, admitidly you would anyway LOL but thats not the point.
Turning off the DEP will stop the crashes and will make ur system almost 99% as fast as it was without sp2. DEP is not needed atm, with a good AV and firewall, you are safe. DEP will be critical in a few years when NX enabled chips are mainstream.