Thanks for the help everyone, very much appreiciated.
A Happy problem free New Year to everyone.
John

"cquirke (MVP Windows shell/user)" wrote:

> On Fri, 23 Dec 2005 11:29:02 -0800, "jrsjs"
>
> >Thanks. It hadn't ocurred to me that could happen.
>
> Me neither.
>
> When did this start?
> Are we hearing massed screams yet?
> What CPU do you have, and did that change?
>
> Some CPUs support DEP in hardware, but there may be differences
> between AMD and Intel tribes, and problems could arise if you change
> from a non-DEP CPU to a DEP one, or vice versa. Where the CPU has no
> hardware DEP, the OS fakes it as best it can.
>
> The other (slim?) possibility is that some other code is involved that
> permeates these apps and affects their DEP compatibility. Both
> malware and anti-malware (av) come to mind, especially as av often
> have problems with DEP (possibly because they may load code into thier
> own data space to single-step or breakpoint-run it for heuristics)
>
> >"PA Bear" wrote:
>
> >> Perhaps one or more of the Critical Updates you installed recently caused
> >> the behavior as a security measure.
>
> >> jrsjs wrote:
>
> >> > I seem to have sorted it by making exceptions for programs which were
> >> > being closed by DEP in change the settings.
>
> >--------------- ----- ---- --- -- - - -
> First, the good news: Customer feedback has
> been clear and unambiguous.
> >--------------- ----- ---- --- -- - - -
>