pdfCreator 0.9.8 on Windows Server 2008 R2, RemoteDesktop Environment, crashing in settings

Hi Forum,

I'm using PDFcreator like described in the Subject and all works as expected, except:

Whenever we click settings ("Einstellungen", its a german installation ) in PDFcreators print-dialog, it crashes with the following informations:
` Problemereignisname:    APPCRASH
  Anwendungsname:    PDFCreator.exe
  Anwendungszeitstempel:    4a02051d
  Fehlermodulname:    StackHash_8028
  Fehlermodulzeitstempel:    00000000
  Ausnahmecode:    c000041d
  Ausnahmeoffset:    74e54cad
  Betriebsystemversion:    6.1.7600.
  Gebietsschema-ID:    1031

The job remains in the queue, but isn't processed until the next printout. It doesn't matter whether the user is logged in on the local console or via a remote desktop session.

Any idea?


edit: subject updated

I had this problem too on Server 2008 R2. It is caused by DEP.All you need to do is go to Control Panel, System, Advanced system settings, and click on the Settings button under Performance. Then click the Data Execution Prevention tab. Click the Add button and browse to and select the PDFCreator.exe file to add it to the DEP exceptions. Click OK, OK and close System. You should now be able to open the PDFCreator settings without errors.

Thanks a lot, that was it!

The german expression for DEP is "Datenausführungsverhinderung" btw. Well, this is not really german, but MS's translation for a word that doesn't exist in german.

Any chance that we get a fix for this sometime? Activating DEP has its advantages, I guess.

Dear cageu,

"It is caused by DEP" is not an explanation of the problem: if DEP is blocking PDFCreator, it probably means that PDFCreator is attempting to execute data blocks of memory, which it shouldn't.

Buffer overflows (prevented by DEP) are the most usual way to execute malicious code; we do not want applications with buffer overflows to be running on our systems (which seems to be the case with PDFCreator, if DEP is blocking it...) because they are potential targets for malware.

So, please, anyone with good programming skills (not my case...), find the problem and solve it... otherwise PDFCreator might have to be put off for security reasons.