Commented by: Alice F. Bird (firebirds)

Date: 2004-10-15 13:21
Sender: danielrail
Logged In: YES
user_id=238419

Have you looked on Microsoft's website.

Here's the search results that I did on MSDN(watch the wrap):
http://search.microsoft.com/search/results.aspx?
qu=data+execution+prevention&View=msdn&st=b&c=0&s=1&s
wc=0

And, I think the developers should look at it too, and maybe
check to make sure that the embedded server is not the
actual cause of the problem. Or, could it be the ODBC driver?

Commented by: Alice F. Bird (firebirds)

Date: 2004-10-15 12:00
Sender: sitman
Logged In: YES
user_id=1126332

Sorry, bu I'm not able to deliver you such details.
I can only tell you what I'm doing and what's happening.
Are you able to reproduce the error?
I check some other Windows environments and the result is,
that under XP Service Pack 1 and under Windows 2000
Service Pack 4 the error is reproduceable too!
For me it seems to be a general problem of the embedded
engine under Windows,
because I'm not able to run embeeded engine on Windows at
all!

Commented by: Alice F. Bird (firebirds)

Date: 2004-10-13 05:57
Sender: robocop
Logged In: YES
user_id=62823

If I understand correctly, WXP says that some data is being
treated like a code sections and therefore, being executed.
However, since there are no details, it's hard to guess
where it happens. I don't know if Dr. Watson can be set up
to trap this problem.

Commented by: @dyemanov

Tried to reproduce this with FB 1.5.3/2.0 Embedded and Firebird ODBC driver ver. 2.0 on my WinXP SP2 box - no error happened.