Bugs item #988095, was opened at 2004-07-10 03:00 Message generated for change (Comment added) made by mhammond You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=988095&group_id=61702
Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: Outlook Group: Binary 1.0rc2 Status: Open Resolution: None Priority: 5 Submitted By: mlarma (mlarma) Assigned to: Mark Hammond (mhammond) Summary: Athlon64, SP2, NX (no execute)=no workee Initial Comment: When enabling the NX function underneath WinXP with SP2 RC2 (32 bit edition, not 64 bit windows), I was unable to start Outlook with the SpamBayes plug-in. After disabling and only disabling NX (remove /noexecute from boot.ini), it worked. Funny thing is that the owner of the company I work for developed a Bayesian spam filter as well and it had the same issue with the NX. Not sure what the problem is, but the NX feature would be nice to turn on. Does anyone know if NX can be disabled at the application level so that the other processes were protected with NX? Mark ---------------------------------------------------------------------- >Comment By: Mark Hammond (mhammond) Date: 2005-08-10 15:31 Message: Logged In: YES user_id=14198 Just had a report that Pythonwin also fails with this turned on. This makes it less likely the problem is simply py2exe. ---------------------------------------------------------------------- Comment By: Mark Hammond (mhammond) Date: 2005-07-23 04:06 Message: Logged In: YES user_id=14198 another possibility is that py2exe is the culprit. It isn't obvious to me that is *is* the problem, but it certainly is possible. It would be interesting to know if the source version of SpamBayes has the same problem. When I get back to Aus, I will try and reproduce this. ---------------------------------------------------------------------- Comment By: Paul Quinn (paulquinn) Date: 2004-07-21 01:04 Message: Logged In: YES user_id=815032 This is a problem with NX protection...this is how I got it to work: There are ways to disable NX at application level: a) Through the UI... i) "Control Panel" > "System" ii) Click on the "Advanced" tab iii) Under "Performance" section, click "Settings" iv) Click on the "Data Execution Prevention" tab v) Click "Add" and select the appication you want to disable NX for b) Registry... Under "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers" (there are equivalent HKEY_CURRENT_USER keys), create a new string key, its name being the full path to the executable file you want to disable NX for, the value being "DisableNXShowUI" ...you'll notice that in the UI, only executable files can be added. This means that I had to select the "Outlook.exe" file to get Spambayes to work again. I tried adding the spambayes_addin.dll and the python23.dll paths to the registry as a workaround, but this didn't work... Also, if you are using Outlook 2003, you may need to re-enable the plug-in by deleting its resilliency key (the COM Add-in Manager won't remember the re-enable setting no matter how many times you try): http://groups.google.co.uk/groups? hl=en&lr=&ie=UTF-8&safe=off&selm=uZ%24FJzyFEHA.3984% 40TK2MSFTNGP10.phx.gbl FYI, the same techniques work with Inboxer etc. I'm guessing, as tim_one said, it's to do with the Python libraries. Paul ---------------------------------------------------------------------- Comment By: Tim Peters (tim_one) Date: 2004-07-10 03:35 Message: Logged In: YES user_id=31435 You'll really have to ask about NX gimmicks on an Athlon list. SpamBayes is written entirely in the Python programming language, and that never, ever tries to execute code from a data region (I'm very familiar with Python's implementation) My only guess is that Outlook itself, or MAPI, try to do this when interfacing with extensions. Or Mark Hammond is playing disgusting games (the only kind he knows, really <wink>) in the win32all Python extensions. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=988095&group_id=61702 _______________________________________________ Spambayes-bugs mailing list Spambayes-bugs@python.org http://mail.python.org/mailman/listinfo/spambayes-bugs