Re: [spambayes-dev] [Spambayes] SpamBayes installation error
Hi all, I'm redirecting this support request to the -dev list. According to my CVS logs, the FlashWindowEx problem with NT was fixed back in October 2004, and the fix included with pywin32-203. I've just confirmed that build 208 of pywin32 does successfully load win32gui on NT. Is it possible that 1.0rc2 was shipped with pywin32-202 or earlier? If there is some issue preventing an upgrade to pywin32, let me know and I'll help resolve it. Cheers, Mark -----Original Message----- From: spambayes-bounces@python.org [mailto:spambayes-bounces@python.org]On Behalf Of Gregg Yauch Sent: Sunday, 9 July 2006 12:01 AM To: spambayes@python.org Subject: [Spambayes] SpamBayes installation error I'm trying to install SpamBayes 1.0rc2 on a WinNT4 pc with Outlook 2000. I get the following error: "The procedure entry point FlashWindowEx could not be located in the dynamic link library USER32.dll" The outlook_addin_register.exe.log file reads: Traceback (most recent call last): File "addin.py", line 40, in ? File "win32gui.pyc", line 9, in ? File "win32gui.pyc", line 7, in __load ImportError: DLL load failed: The specified procedure could not be found. Any ideas? Thank you, Gregg Yauch
I'm trying to install SpamBayes 1.0rc2 on a WinNT4 pc with Outlook 2000. I get the following error: [...] I'm redirecting this support request to the -dev list. According to my CVS logs, the FlashWindowEx problem with NT was fixed back in October 2004, and the fix included with pywin32-203. I've just confirmed that build 208 of pywin32 does successfully load win32gui on NT.
Is it possible that 1.0rc2 was shipped with pywin32-202 or earlier? If there is some issue preventing an upgrade to pywin32, let me know and I'll help resolve it.
It seems to me that the better question is: why is Gregg using 1.0rc2 (June 26, 2004), rather than the latest stable version (1.0.4, March 24, 2005)? FWIW, given those dates, I expect the answer to your question is "yes" (unless you snuck in an unreleased pywin32 into 1.0rc2; too long ago for me to remember). =Tony.Meyer
Is it possible that 1.0rc2 was shipped with pywin32-202 or earlier? If there is some issue preventing an upgrade to pywin32, let me know and I'll help resolve it.
It seems to me that the better question is: why is Gregg using 1.0rc2 (June 26, 2004), rather than the latest stable version (1.0.4, March 24, 2005)?
Ack - sorry about that - I know I *meant* to check that before mailing :) Mark
participants (2)
-
Mark Hammond -
Tony Meyer