FreeWheelin Frank,
Looking at the quality of your post, I would think you would be the last person who could effectively differentiate between gibberish and a nice coherent piece of writing.
Obviously, you didn't even read the article on Slick IT. In fact, the author - a guy that I know personally - even took the time to put a disclaimer in the article for dumbasses such as you. If you would have read it, you would have realized that the screen shots were from Windows 7 as he tells you, but the issue described is for Windows XP SP3.
You are right about XP SP3 not having the MVM - but what you are failing to take into account is the upgrade path that resulted in SP3 being applied. If you are going from SP1 on an OEM CD - like many people are - and end up using MS update to get up to SP3, MVM will be installed, alive, and well on that machine. Furthermore, it will be the source of issues as Paul pointed out.
Instead of offering anything helpful, you instead point the person to Opera or Firefox. This is not a solution - it isn't even a workaround.
Disabling DEP...again that is not a solution. DEP, a feature that was engineered by people holding Ph.Ds in computer science, was put in place to stop rogue applications, bad drivers, and root kits from executing code in protected memory space. I know you don't understand what that means, but you have definitely felt the effects on your spyware infested OS. Disabling DEP is stupid - it is a valuable tool in the fight against malware.
In the future, if you are going to critique a piece of writing, you should get your facts straight and take some time to actual (sp) read the post.