Disabling Data Execution Prevention (DEP) for Windows 7 - Part I
This is a general research notes on the new way Date Execution Prevention (DEP) in Windows 7 systems prevents many of the old applications getting executed on the system (mostly memory address areas). There are various details that can be looked into for in-depth knowledge on this issue. Truly speaking this is tight and there is no such workaround except ROP gadgets (Return - Oriented Programming) that is more of ethical hacking than a workaround and is a subject in itself. The problem which usually comes up with is more technical and is related to diverse factors. Actual Exception from Visual Studio: This actual exception comes up while instantiating the new Java Axbridge ActiveX object. System.AccessViolationException was caught Message="Attempted to read or write protected memory. This is often an indication that other memory is corrupt. This followed up by NullReference exception as it failed to create the object. Standalone Executable may come up with the fo