You just need to include the executable in the list of DEP exceptions.
If you're in development mode then list vdevw.exe; if it's a runtime
application then the image .exe file.
-----Original Message-----
From: Using Visual Smalltalk for Windows/Enterprise
[mailto:
[hidden email]] On Behalf Of Frank Govaerts
Sent: 09 February 2011 12:43
To:
[hidden email]
Subject: Re: Windows server 2008 leads to protection violation at
startup
Nicolas ,
True, I never had to check that before but that caused the problems so
far.
I turned DEP off completely on a development server but is it sufficient
to
put the VSE in the list of programs to exclude from DEP? Or is this
where
that patching comes in?
Thanks for your fast reply,
Frank
On Wed, 9 Feb 2011 10:24:11 -0000, Nicolas Bryant
<
[hidden email]> wrote:
>Have you checked to see if it's a Data Execution Prevention problem?
>
>
>
>-----Original Message-----
>From: Using Visual Smalltalk for Windows/Enterprise
>[mailto:
[hidden email]] On Behalf Of Frank Govaerts
>Sent: 09 February 2011 10:06
>To:
[hidden email]
>Subject: Windows server 2008 leads to protection violation at startup
>
>Hi,
>I'm verifying how I can run a VSE application on Windows Server 2008
but
>the
>application crashes on a protection violation - even when I run it in
>whatever compatibility mode. It is a vse2000 as far as I can see.
>Is this a known issue? From browsing through the messages here I had
the
*** this signature added by listserv ***
*** Visit
http://www.listserv.dfn.de/archives/vswe-l.html ***
*** for archive browsing and VSWE-L membership management ***
*** this signature added by listserv ***
*** Visit
http://www.listserv.dfn.de/archives/vswe-l.html ***
*** for archive browsing and VSWE-L membership management ***
Locked
