So, I'm trying to get my mod to run on my Vista 32 bit computer. SC works fine, and I can connect to ShadowFlare's Realm. However, when I try to run my mod, Vista says "Starcraft has stopped working" and a bubble in the bottom right says that Starcraft has been prevented from running due to DEP. So, I grapped ToggleNX. No help. I tried adding SC to the exception list for DEP -- to which I found out that SC CANNOT be added to the exception list. I tried: bcdedit.exe /set {current} nx AlwaysOff, it STILL says DEP prevented the program even though it is completely off. I tried running as admin...
Nothing seems to work, and yet, I remember at one point in time I could run my mods on Vista 32 bit (I recently had my computer's hard drive wiped clean by HP).
Did I forget something I did long ago? I have also tried getting MPQDraft for Vista and tried running my Firegraft mod through it, but the grafting changes don't show up. Any help is appreciated.
LOL SOLVED.
You need to restart after doing the command prompt.
Hmm, has a more recent version of FireGraft or a plugin started putting code in memory that isn't being marked as executable? (note: this isn't a question for you, but for the creators of those)
Last I knew of, no recent utilities required that to be disabled for it to run...
None.
The most recent version of Firegraft I have (the non-beta) requires me to disable DEP, so I just took DEP off completely using the command prompt; DEP is quite useless in my opinion, it doesn't even stop viruses. And, MPQDraft works fine without disabling DEP, its just .exe files that require DEP to be turned off.
And, for people who have the same problem:
1. Open Command Prompt (search for it in the start menu)
2. Type in: bcdedit.exe /set {current} nx AlwaysOff
3. Restart your computer
4. ????
5. Profit!
It isn't useless. It can prevent code from running that is injected by an intentional buffer overflow, for example. The buffer overflow could be from a specially crafted file (sometimes related to compressed data that is designed to overflow when decompressed), a specially crafted web site (possibly related to a javascript exploit), etc.
Buffer overflows are probably one of the most common things that is exploited and Data Execution Prevention is one of the mechanisms in place to make sure it can't be exploited.
None.