{"id":549,"date":"2004-08-09T00:00:00","date_gmt":"2004-08-09T00:00:00","guid":{"rendered":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php\/2004\/08\/09\/windows-xp-service-pack-2-good-for-amd-chips\/"},"modified":"2021-12-30T11:37:39","modified_gmt":"2021-12-30T11:37:39","slug":"windows-xp-service-pack-2-good-for-amd-chips","status":"publish","type":"post","link":"https:\/\/www.cybersecurityinstitute.com\/blog\/?p=549","title":{"rendered":"Windows XP Service Pack 2 good for AMD chips"},"content":{"rendered":"<p>AMD announced that with the release of Microsoft Windows XP Service Pack 2 (SP2), Enhanced Virus Protection (EVP) can now be enabled on all AMD Athlon64 processors.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>This unique hardware and software combination is designed to keep computers protected against certain malicious viruses, computer worms and Trojan horses.<\/p>\n<p>When combined with the Data Execution Prevention technology found in Windows XP SP2, it provides a multi-layered defense against many common online threats.  It not only identifies certain malicious code, specifically those that execute buffer overflow attacks, but also prevents them from replicating and spreading throughout the system.<\/p>\n<p>The hardware and software technology from AMD and Microsoft is designed to proactively defend computers from these far too prevalent attacks, providing critical protection from some of the fastest-growing and most damaging viruses in the world today,&#8221; said Rob Enderle, President and Principal Analyst, Enderle Group.<\/p>\n<p>Every AMD Athlon64 FX-53, AMD Athlon64 mobile and desktop, and Mobile AMD Sempron processor customer will be able to use the built-in EVP capability when enabled by Windows XP SP2.<\/p>\n<p>http:\/\/www.cooltechzone.com\/index.php?option=content&#038;task=view&#038;id=457&#038;Itemid=0<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[29],"tags":[],"class_list":["post-549","post","type-post","status-publish","format-standard","hentry","category-news"],"_links":{"self":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/549","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=549"}],"version-history":[{"count":1,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/549\/revisions"}],"predecessor-version":[{"id":3036,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=\/wp\/v2\/posts\/549\/revisions\/3036"}],"wp:attachment":[{"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=549"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=549"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.cybersecurityinstitute.com\/blog\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=549"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}