2
« on: April 02, 2008, 02:21:01 pm »
Wake up people, Gigaherz isn't some random idiot come in from the street, If he can't get it working, then theres obviously some fault in the application preventing it from working on his, and potentially others setups,
Its not the first time such a problem has arisen in an application, as i remember a few years back a well known game would crash straight away when run on CPU's with EMT64 rather then AMD64.
The first red flag that comes out to me, is that since this machine is that of a developer, its possible that the game is conflicting with one of the libraries installed by his compilers.
The second is that it triggers a crash in DEP, typically crashes in DEP are caused by applications trying to access memory space that they aren't supposed, while disabling DEP may fix this, it is not a satisfactory outcome to just get one game working, rather the application should be fixed to remove the problem altogether, By Disabling DEP, you prevent crashes by disabling DEP, and instead open a path for buffer overflows to lead to code execution. The fact is, if the application was coded correctly, it shouldn't be triggering DEP at all, and if i remember correctly, this isn't the first time that Planeshift has had buffer overflow's.
So rather then posting the typical scripted "use admin persmission" jargon, try and think outside the square, because Gigahertz is definitely not the type to make a noob mistake like that.