http://blogs.technet.com/askperf/archive/2007/10/05/the-program-compatibility-assistant-part-two.aspxIn our previous post on PCA, we discussed several runtime issue detection scenarios. Today, we are going to examine some program startup scenarios (specifically application blocking) and discuss the management of the Program Compatibility Assistant. Let'sen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.technet.com/askperf/archive/2007/10/05/the-program-compatibility-assistant-part-two.aspx#2114027Fri, 05 Oct 2007 15:52:53 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:2114027microsoft » The Program Compatibility Assistant - Part Two<p>PingBack from <a rel="nofollow" target="_new" href="http://microsoft.whitewitty.info/?p=3469">http://microsoft.whitewitty.info/?p=3469</a></p> http://blogs.technet.com/askperf/archive/2007/10/05/the-program-compatibility-assistant-part-two.aspx#2178515Mon, 15 Oct 2007 21:43:45 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:2178515pete<p>Never mind. The answer seems to be &quot;include a manifest resource in your program which indicates you know what you are doing.&quot; I'll try that and and then try to remember to post details here.</p>http://blogs.technet.com/askperf/archive/2007/10/05/the-program-compatibility-assistant-part-two.aspx#2323225Sat, 03 Nov 2007 21:39:53 GMTd5e57398-b9ef-4490-9955-07cbb4e4a80d:2323225Tanveer Badar<p>And let me guess the ISV's name, isn't it Symantec?</p>