So over the last few days I've been looking into Windows Data Execution Prevention (DEP)
I've never given it much attention until I needed to use PICVideo Mjpeg for something, prior to this I have strictly been using Indio5.1 with decent results.
PICVideo prior to version 3.0 is incompatible with DEP and will cause Explorer to be shut down when browsing a folder with Picvideo files and generally stop every program playing Picvideo files too.
Indio is also also causing some problems but only during thumbnail view in explorer, it seems very stable running in everything else.
After reading around a bit it would seem there are few negative reports about PICVideo Ver3.0 and DEP. Perhaps the problem isn't completely fixed, a little annoying considering I just upgraded to this version. So far "fingers crossed" ver3.0 seems very stable, it's only been a couple of days though. As DEP at a hardware level rolls out I can see it being a huge headache for people using incompatible software/codecs, I would hate to have to recode my entire library.
So I was back up and running with Mjpeg, then I installed 2.4 and it just wasn't happening, constantly crashing. Generally I would open it up then when I would go to browse files, drag to slots etc the browser section would stop working, then the program would become unresponsive, then crash. over and over.
So I deleted all the Mjpeg files went back to Indio, same thing. damn
Back to Resolume 2.4beta Indio working fine then Mjpeg, both working fine. At that point It was about 2am so I went to sleep
I've got a show that I'm working hectically on so 2.4 is on the back burner for now.
Recently I believe a Microsoft update swapped the DEP default setting from critical apps to all apps with exceptions.
Last night 2.4beta crashed as it often does while closing the app, it came up as blocked by DEP. No idea if that's a codec or the program, just as explorer crashes and subsequently gets listed when browsing bad pre-ver3.0 PICVideo files.
ATM I'm going to run Windows with a DEP exception list on Resolume, if that doesn't work I'll edit the boot.ini to turn DEP off system wide.
I just read about the Resolume log start option so I will give that a go to see if I can catch anything too.
If other people are experiencing the same thing maybe give it a try. I've read the exclusion list is not working for some people while the system wide changes are.
more info
http://www.microsoft.com/technet/securi ... cnfxp.mspx
Q5: I am running an application using a Pegasus Imaging product on Windows XP SP2 and I get a Data Execution Protection (DEP) dialog. Windows XP Service Pack 2 makes several operating system improvements focused primarily on security in an effort to make computing more reliable and less prone to malicious attacks. One of the improvements includes protection against buffer overruns which are commonly associated with viruses and worms. To prevent such attacks from occurring in the future, Service Pack 2 supports hardware-based Execution Protection (NX) and software-based Sandboxing. While enforcing memory protection is good for computing overall, it does present a compatibility issue which requires resolution by software vendors throughout the world.
Pegasus Imaging has tested its code on Windows XP Service Pack 2, and has found that running in this environment on the 64-bit AMD K8 and Intel Itanium hardware platforms will cause hardware protection to be triggered. Other hardware platforms do not exhibit similar behavior, and should run without issue. However, it is expected that future processor iterations made for Windows systems will have hardware protection capabilities, so migration plans should take this into account. When hardware protection is triggered, a Data Execution Protection (DEP) dialog appears and asks the user if the application should be trusted to run. This capability places the decision in the hands of the user and provides a workaround.
