DEP Service release.

[hutch--]

These will not effect many people yet except for those who are using a late version of Windows with hardware DEP enabled on a late enough box to have the hardware support. I have rebuilt a reasonable number of the EXE files in the masm32 project so that they will run under a DEP enabled machine without any problems. Eventually I will do another version of masm32 where all of the installation is compatible with hardware DEP.

[attachment deleted by admin]

[Shantanu Gadgil]

All binaries run fine. :thumbu :thumbu

Have not actually used the binaries, so can't say anything 'bout that, just did a for %s in (*.exe) do %s

No "this program has performed..."  messages!!!

Regards,
Shantanu

[hutch--]

Shantanu,

Many thanks, the testing is appreciated.  :thumbu

[Cobra]

Thanks. It was driving me nuts trying to get an INC file for the GDI+ library.  :U

[MoreBits]

Hi,

It would be great to know, that there is a complete  "special" version of the installation package available - I just encountered such a problem (still don't know how!) and at the moment I'm not sure how to change my system back. But - the files from dep_binaries.zip work!

kind regards

MoreBits

[hutch--]

morebits,

There is little  can do about it, when masm32 version 9.0 was produced, the DEP specs had not been implimented yet. I tracked the problem and changed the binaries to suit the altered specifications of 32 bit PE files and placed the zip file where it is readily available. It will be no problem in the next version as it will be released AFTER the DEP specifications were put in place. It is only a problem for XP SP2 and higher and finally I am not responsible for specification changes from Microsoft.

[MoreBits]

HI,

hutch, of course you're not the person in charge for MS... and I'm far away from blaming you for the problem.

But here some other results of my tries to get the (old) files working again and to understand the problem:

Tests (as described e.g. in MS KB912923) showed, that I have DEP (software and hardware), which is by default (MS) set to OptIn. That is, all windows system files, and others, which have "Opt In" are secured. So ,why MASM32 files are affected at all?

For the next try I switched DEP off (in Boot.ini: /noExecute=AlwaysOff) - same problem as before. The error report shows (as also before) stop error 0xC0000005, this is (if I'm not wrong) "segment violation". So, is it really a problem of DEP?


kind regards

MoreBits

[MoreBits]

Hi,

a short update concerning the last results:

With DEP mode "AlwaysOn" I only got a special DEP-message _before_ the already known message, that the program was ended because of some errors.

Some minutes ago the guilty party was found - it was not MASM32 and it was not WinXP/MS: Kaspersky Internet Security (v6.0.2.614, MP2)  does something deep within the system provoking such errors. With another setting for KIS (a so called "compatibility mode") the older Masm32-.exe run as to expect - no problems at all.

Despite of this, I'd like to see a "DEP-ready" MASM32-version soon  :wink..

Thanks for all hints and ideas!

regards

MoreBits

[Tedd]

Works fine for me - with DEP on (full.)
BUUTT.. all of the packed extensions and plugins need to rebuilt too (namely "addmenu.dll", "menuedit.dll", "setini.dll", "printtxt.dll", etc) - they still trigger.


Also with the 'new' version of QEditor, strangely, I get "Cannot find addmenu.dll" if I click the menu item "Selection -> More Text Functions...." -- even though it's clearly found, otherwise that menu option wouldn't appear.

[hutch--]

Thanks Tedd, I thought I had done the plugin DLLs but it seems to be not so.  :thumbu