Bugs item #1895575, was opened at 2008-02-17 14:01 Message generated for change (Comment added) made by montanaro You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1895575&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: 1.0.4 >Status: Closed >Resolution: Accepted Priority: 5 Private: No Submitted By: Andy (wardlea) >Assigned to: Skip Montanaro (montanaro) Summary: Outlook 2003 SP 3 fails loading 1.0.4 and 1.1a4 on Win2K Initial Comment: Whenever I try to run the 1.0.4 or 1.1a4 versions of SpamBayes (I'm running Windows 2003 Server R2 Service Pack 2) and Outlook 2003 Service Pack 3, Outlook fails during initialisation and offers me the chance to disable the add-in. Enabling it causes the same problem all over again. I've got DEP enabled, but I've excluded all of the executables/dlls in the SpamBayes bin directory - it makes no difference. I suspect it's more of a problem with Windows 2003 than Outlook 2003 SP3 - I think the problem first occurred before I upgraded to SP3. The log file is empty. ---------------------------------------------------------------------- >Comment By: Skip Montanaro (montanaro) Date: 2008-02-18 07:48 Message: Logged In: YES user_id=44345 Originator: NO I updated the FAQ with this extra bit of information. I'm closing this ticket, as that's about the best we can do I think. ---------------------------------------------------------------------- Comment By: Andy (wardlea) Date: 2008-02-18 07:33 Message: Logged In: YES user_id=2011950 Originator: YES Jesse Pelton reminded me that excluding Outlook itself from DEP had worked for Athlon x64 CPUs (see http://spambayes.sourceforge.net/faq.html#after-installing-spambayes-outlook-crashes-and-then-asks-for-the-plug-in-to-be-disabled), and this proved to be the resolution for my problem on my Core 2 Duo CPU. Thanks, Jesse :-) As a newbie to this forum I'm not sure whether or not that means this Bug is closed, or simply has a workaround, so hopefully someone more experienced will make that judgement for me ... ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=498103&aid=1895575&group_id=61702 _______________________________________________ Spambayes-bugs mailing list Spambayes-bugs@python.org http://mail.python.org/mailman/listinfo/spambayes-bugs
