SetWindowLong GWL_WNDPROC XP,2003 - SOLVED
in [Win32 Kernel]
|
Prev: SetWindowLong GWL_WNDPROC XP,2003
Next: Deadly embrace between SetUnhandledExceptionFilter() and thread rundown(???) in Server 2003
From: Hector Santos on 4 Jan 2010 01:23 Oh brother! Thanks that was it. Appreciate it. Wasted 3 days on this. Never had to deal with it before. Ivan Brugiolo [MSFT] wrote: > First of all, have you considered Data-Execution-Protection / NX issues ? > > NX is disabled in all but trusted system processes on WinXp, while it is > enabled on all but explicitly disabled applications on Server SKUs. > There is a long list of DLLs, more or less known to the system and > complete , > where DEP is disabled for a process that fails to set the execution bit > on pieces of memory where it uses to generate code to be later-on executed. > SetProcessDEPPolicy should be your friend here, if you are writing code, > or, the UI for DEP/NX should allow you to white-list that application. > -- HLS
From: Hector Santos on 4 Jan 2010 02:33 Apparently for 2003, this SetProcessDEPPolicy() is not available in kernel32.dll. Oh well, has to be a manual instruction for customers having this issue. Thanks to all. Hector Santos wrote: > Oh brother! Thanks that was it. Appreciate it. Wasted 3 days on this. > Never had to deal with it before. > > > Ivan Brugiolo [MSFT] wrote: > >> First of all, have you considered Data-Execution-Protection / NX issues ? >> >> NX is disabled in all but trusted system processes on WinXp, while it is >> enabled on all but explicitly disabled applications on Server SKUs. >> There is a long list of DLLs, more or less known to the system and >> complete , >> where DEP is disabled for a process that fails to set the execution bit >> on pieces of memory where it uses to generate code to be later-on >> executed. >> SetProcessDEPPolicy should be your friend here, if you are writing code, >> or, the UI for DEP/NX should allow you to white-list that application. >> > > > -- HLS
From: Paul Baker [MVP, Windows Desktop Experience] on 4 Jan 2010 08:45 Hector, It is possible to configure DEP programatically without instructing the user to follow a manual process. There are DisableNXShowUI and DisableNXHideUI compatibility modes. They are not well documented, but here is a forum post that may explain enough for you to successfully implement it. If not, you can search the Internet for additional information. http://social.msdn.microsoft.com/Forums/en-US/os_fileservices/thread/f6283fee-af4c-4b1a-9024-96426c586f0a Paul "Hector Santos" <sant9442(a)nospam.gmail.com> wrote in message news:e2i8ZBRjKHA.2132(a)TK2MSFTNGP05.phx.gbl... > Apparently for 2003, this SetProcessDEPPolicy() is not available in > kernel32.dll. > > Oh well, has to be a manual instruction for customers having this issue. > > Thanks to all. > > Hector Santos wrote: > >> Oh brother! Thanks that was it. Appreciate it. Wasted 3 days on this. >> Never had to deal with it before. >> >> >> Ivan Brugiolo [MSFT] wrote: >> >>> First of all, have you considered Data-Execution-Protection / NX issues >>> ? >>> >>> NX is disabled in all but trusted system processes on WinXp, while it is >>> enabled on all but explicitly disabled applications on Server SKUs. >>> There is a long list of DLLs, more or less known to the system and >>> complete , >>> where DEP is disabled for a process that fails to set the execution bit >>> on pieces of memory where it uses to generate code to be later-on >>> executed. >>> SetProcessDEPPolicy should be your friend here, if you are writing code, >>> or, the UI for DEP/NX should allow you to white-list that application. >>> >> >> >> > > > > -- > HLS
From: Hector Santos on 5 Jan 2010 04:37 Wonderful Paul! I was trying to see how to get the Exe listed in that box. That is what I thought SetProcessDepPolicy() would do which does seem to do the job to white list the process during its run time. I just tried the registry option, it worked! Appreciate the great input. -- Paul Baker [MVP, Windows Desktop Experience] wrote: > Hector, > > It is possible to configure DEP programatically without instructing the user > to follow a manual process. > > There are DisableNXShowUI and DisableNXHideUI compatibility modes. They are > not well documented, but here is a forum post that may explain enough for > you to successfully implement it. If not, you can search the Internet for > additional information. > > http://social.msdn.microsoft.com/Forums/en-US/os_fileservices/thread/f6283fee-af4c-4b1a-9024-96426c586f0a > > Paul > > "Hector Santos" <sant9442(a)nospam.gmail.com> wrote in message > news:e2i8ZBRjKHA.2132(a)TK2MSFTNGP05.phx.gbl... >> Apparently for 2003, this SetProcessDEPPolicy() is not available in >> kernel32.dll. >> >> Oh well, has to be a manual instruction for customers having this issue. >> >> Thanks to all. >> >> Hector Santos wrote: >> >>> Oh brother! Thanks that was it. Appreciate it. Wasted 3 days on this. >>> Never had to deal with it before. >>> >>> >>> Ivan Brugiolo [MSFT] wrote: >>> >>>> First of all, have you considered Data-Execution-Protection / NX issues >>>> ? >>>> >>>> NX is disabled in all but trusted system processes on WinXp, while it is >>>> enabled on all but explicitly disabled applications on Server SKUs. >>>> There is a long list of DLLs, more or less known to the system and >>>> complete , >>>> where DEP is disabled for a process that fails to set the execution bit >>>> on pieces of memory where it uses to generate code to be later-on >>>> executed. >>>> SetProcessDEPPolicy should be your friend here, if you are writing code, >>>> or, the UI for DEP/NX should allow you to white-list that application. >>>> >>> >>> >> >> >> -- >> HLS > > -- HLS
From: Paul Baker [MVP, Windows Desktop Experience] on 5 Jan 2010 09:06
I think SetProcessDepPolicy() is just a convenient wrapper. If you don't have it, it's not a problem. Paul "Hector Santos" <sant9442(a)nospam.gmail.com> wrote in message news:OP1LXrejKHA.2160(a)TK2MSFTNGP02.phx.gbl... > Wonderful Paul! > > I was trying to see how to get the Exe listed in that box. That is what I > thought SetProcessDepPolicy() would do which does seem to do the job to > white list the process during its run time. > > I just tried the registry option, it worked! > > Appreciate the great input. > > -- > > Paul Baker [MVP, Windows Desktop Experience] wrote: > >> Hector, >> >> It is possible to configure DEP programatically without instructing the >> user to follow a manual process. >> >> There are DisableNXShowUI and DisableNXHideUI compatibility modes. They >> are not well documented, but here is a forum post that may explain enough >> for you to successfully implement it. If not, you can search the Internet >> for additional information. >> >> http://social.msdn.microsoft.com/Forums/en-US/os_fileservices/thread/f6283fee-af4c-4b1a-9024-96426c586f0a >> >> Paul >> >> "Hector Santos" <sant9442(a)nospam.gmail.com> wrote in message >> news:e2i8ZBRjKHA.2132(a)TK2MSFTNGP05.phx.gbl... >>> Apparently for 2003, this SetProcessDEPPolicy() is not available in >>> kernel32.dll. >>> >>> Oh well, has to be a manual instruction for customers having this issue. >>> >>> Thanks to all. >>> >>> Hector Santos wrote: >>> >>>> Oh brother! Thanks that was it. Appreciate it. Wasted 3 days on >>>> this. Never had to deal with it before. >>>> >>>> >>>> Ivan Brugiolo [MSFT] wrote: >>>> >>>>> First of all, have you considered Data-Execution-Protection / NX >>>>> issues ? >>>>> >>>>> NX is disabled in all but trusted system processes on WinXp, while it >>>>> is >>>>> enabled on all but explicitly disabled applications on Server SKUs. >>>>> There is a long list of DLLs, more or less known to the system and >>>>> complete , >>>>> where DEP is disabled for a process that fails to set the execution >>>>> bit >>>>> on pieces of memory where it uses to generate code to be later-on >>>>> executed. >>>>> SetProcessDEPPolicy should be your friend here, if you are writing >>>>> code, >>>>> or, the UI for DEP/NX should allow you to white-list that application. >>>>> >>>> >>>> >>> >>> >>> -- >>> HLS >> >> > > > > -- > HLS |