Re: DEP and /NXCOMPAT troubles...
- From: Jeroen Mostert <jmostert@xxxxxxxxx>
- Date: Sun, 09 Nov 2008 00:27:16 +0100
Ira Baxter wrote:
So, what on earth does /NXCOMPAT:NO actually *do*?I answered this question on 2008-10-19. In case you missed my reply, here's the relevant bit again:
The other (YES) state, implies the program is compatible
with DEP and can be run that way.
"The MSDN documentation says "/NXCOMPAT:NO can be used to explicitly specify an executable as not compatible with Data Execution Prevention". This is not how it works, at least not for XP -- the semantics *might* actually be that for Vista (that is, your exe's subsystem version is 6.00), but I have no idea.
For XP and earlier, at least, this should say "/NXCOMPAT:NO can be used to specify an executable as not tested to be compatible with Data Execution Prevention", because that's the actual inverse of /NXCOMPAT. It merely *clears* the bit that says the application *is* compatible with DEP, which does not mean the application definitely is *not* compatible with DEP. If DEP is set to OptOut, your application must still be added to the list of exceptions to disable DEP. /NXCOMPAT can be used to opt-in to DEP, but not to opt-out.
To actually say your application absolutely positively cannot handle DEP and should get a break, you have to call SetProcessDEPPolicy() from within the application. This function is only availabe from Vista SP1 onwards, however."
--
J.
.
- References:
- Re: DEP and /NXCOMPAT troubles...
- From: Ira Baxter
- Re: DEP and /NXCOMPAT troubles...
- Prev by Date: Re: DEP and /NXCOMPAT troubles...
- Next by Date: Re: Finding Paged Pool and Non-Paged Pool Limits as determined by memory manger
- Previous by thread: Re: DEP and /NXCOMPAT troubles...
- Index(es):
Relevant Pages
|
