Around the time of the WMF scare, I turned my Windows XP SP2 DEP level
up to maximum - and with an Intel P4 640, this is hardware DEP, the
only type reckoned to have been of ant use against the exploit.
Quite surprised, when as well as "the usual suspects", a few old
programs known to require DEP exceptions, Kodak Easyshare (ver
5.2.0.0) caused a DEP error on the next boot.
Queried it on Kodak support, and eventually got a callback ... from
someone who was completely off track on just what DEP actually does,
convinced it was part of Windows Firewall.
Has anyone else turned DEP to "full" (all programs other than those
specified) and had to make an exception for Easyshare ?
What DEP is:
It halts a program if it attempts to execute code located in a
non-code segment - particularly intended to trap buffer overflows and
other ways in which code may be incorrectly run.
It should not happen in normal programs, as the normal method of
compiling and linking should mark executable program segments
appropriately, though some ways of self modifying or creating code
will upset it - techniques which break rules that were previously not
enforced, but in the most part were followed as "good practice".
--
I may be dozzzy, but take the ZZZ's out to mail me
http://www.junkroom.freeserve.co.uk/jvc2080.htm - 2x2x24 CD-RW troubles
If you drop a cactus, don't try to catch it!