On Tue, Jun 15, 2010 at 11:14 AM, David Ashley
> Any idea why killer.exe would fail with an access denied during a build?
I have an idea, but I haven't investigated. The access denied comes
from not having enough rights to kill the process.
Originally, killer.exe just worked. Then when we moved to supporting
Vista, I needed to add some code to get it to work on Vista. The
killer process needed to have its rights elevated to kill the rxapi
process. After this, killer worked on both XP and Vista. Then,
sometime around last Christmas, killer stopped working on my XP
So, my idea is that one of the XP Windows Update fixes changed
something in the security model to cause killer to no longer have the
proper access rights to kill rxapi.
What I did on my XP systems is to take the "less work" way out, and
installed pskill from Sysinternals. Then edited makeorx.bat to use
pskill instead of killer:
C:\work\wc\main>svn diff makeorx.bat
--- makeorx.bat (revision 5997)
+++ makeorx.bat (working copy)
@@ -116,7 +116,7 @@
CALL ORXDB %BLDRELEASE%
IF ERRORLEVEL 1 GOTO ENV_VARS_CLEANUP
Since pskill does work, I know it is possible for killer to work. I
just haven't delved into why it stopped working.