DEP on Amd64 stops Blitz programs running!
Blitz3D Forums/Blitz3D Programming/DEP on Amd64 stops Blitz programs running!
| ||
| Just posted a bug report about turning on DEP on Amd64 for all programs stopping blitz programs from running. Just tried running a blitz+ program and that didn't work either. I know I can turn off DEP but it seems like blitz is doing something that it shouldn't. At least according to Windows anyway! |
| ||
| DEP=TCPA *BARELY* IN DISGUISE :'( what? its true! |
| ||
| Wasn't there a bug mentioned in the implementation of this system within XP SP2? |
| ||
| Um, you can semi-disable it- dont have it on full dep- just have it for major windows files i dun that i havet had a bug since :D |
| ||
| Is this just when run from the IDE (in which case does it occur both with and without debug on) or does it occur on executables too? The debugger will have to poke about in a program's memory, which would presumably trigger that sort of thing off. No idea how that would be worked around myself! |
| ||
| I first found this after I downloaded the CSP demo from the blitz homepage which probably means it isn't the debugger. Actually, when I think about it, I didn't have the debugger on when I tried to run a little program earlier. I've done like Cygnus said and turned it back to semi-enabled and it is fine. By the way, the only error I was getting was a memory access violation, no mention of DEP or NX or anything to give a clue as to what was wrong! |
| ||
| DEP=TCPA *BARELY* IN DISGUISE :'( Explain how. How does something which only prevents execution of code in specified memory areas have anything to do with TCPA? Where's Fritz? Where's the machine hash? Where's the change certification? Setting media to NX would have no benefit for DRM either, because media files are inherently non-exectuable anyway. Could it be to do with the way the runtime is attached to the EXE and then called? There are problems like this with .NET stuff too, so it's not exactly a problem limited to Blitz programs. Would be nice not to have to worry about it though. |
| ||
| Byside the fact that TCPA will not only control Executables, but all files, especially Media (eg. prevent an Anti-Government Movie from running - I am not kiddin here, they really try to censor the internet, OS-independently), I want to mention that the latest CSP Demo was packed with Molebox and since Molebox does some patching stuff, it may have something to do with molebox. instead of askin yourself what the problem is, please compile a little blitz app and try to run it, i really wonder if it works with this - ehm - DEP thingy (did you know the meaning of the german word DEPP is IDIOT ;) ) |
| ||
| That's a pretty good one too. I guess programs that have been compressed with Molebox or something like UPX might have problems also. DEP is just the Windows way of doing NX (No Execute), which essentially allows programs to restrict which areas of memory that they use are allowed to have executable code in them. It's mainly to prevent buffer overruns and would probably prevent the current JPEG vulnerability from happening. AFAIK only AMD's 64-bit processors (and maybe the derivative Sempron as well) support it currently. TCPA is horrible, but it's not NX. There seems to be a few AMD64 owners with Windows XP here, so it shouldn't be too hard to organise a proper test. |
| ||
| i bet microsoft turn DEP into something more TCPA like :P |
   |