> -----Original Message-----
> From: Mark Hammond [mailto:mhamm...@skippinet.com.au]
> Sent: Wednesday, January 06, 2010 12:41 AM
> To: Ocean
> Cc: spambayes@python.org
> Subject: Re: [Spambayes] FW: Windows 7 x64 - Problems
>
>
> > If you want a log of what happens when a new message comes in, I can
> > try to get that for you from the Trace Collector. However, if you want
a
> > log of what's happening when Outlook starts up and fails to load
SpamBayes
> > in the first place, you'll have to tell me how to get it - since the
only
> > way I've been able to get info from the Trace Collector is to run it
from
> > SpamBayes Manager once Outlook is already loaded.
>
> I'm a little confused - if there are errors when a new message comes in,
> doesn't that mean spambayes is already loaded?
>
When Outlook is started, you get the error message that SpamBayes
failed to load. However, the toolbar is present, and you can interact with
it as normal - although it starts off disabled. I enabled SpamBayes,
started the Trace Collector, and then ran the test suite. That was the
setup for the partial trace logs I supplied earlier.
I suppose it's possible that the Test Suite is failing, but
SpamBayes would actually run correctly once manually enabled (which would
have to be done every time Outlook is started), but I haven't been able to
confirm this (not getting enough spam to test yet).
> I admit I haven't been following as closely as I could - I'm really just
> after the complete copy of any relevant errors - your last email had
> both partial errors, and seemed to include some references to the test
> suite having been run. Anything you can do to achieve that goal (ie,
> relevant errors in their entirety) would be good.
>
I gave you everything relevant insofar as the errors that showed up
while running the test suite. However, *if* SpamBayes is capable of running
correctly, and it's just the test suite that's failing, then the big issue
is what's causing it to not load when Outlook starts. And I still need a
way to get those trace logs.
> > Just to clarify, I've tried running the Trace Collector through
> > Pythonwin as well as through win32traceutil.py, but nothing shows up
when I
> > start Outlook. I only get data when I launch it through SpamBayes.
>
> This sounds like an issue introduced with Vista. If you start a
> cmd-prompt or pythonwin with admin permissions (ie, "run as
> administrator") before starting outlook it should work OK. As mentioned
> above though, unless you plan to hack on the sources, using a binary
> build is probably best.
>
> Cheers,
>
> Mark
Well, first of all, I'm running on an Admin account, so my loading
the Trace Collector is already occurring with admin access (however, I tried
doing it manually just to be sure - no change in results).
And secondly, I do need and prefer to run from source. Although I
could be wrong, I don't recall seeing a binary for 1.1a4. But more
importantly, I made a few very small changes in the source to support
multiple profiles in Outlook (which I had outlined in a prior email to the
mailing list earlier this year). These changes are minor and would not have
anything to do with what's going on now. In addition, I ran Spambayes
perfectly on XP with those mods. If you like, I can tell you exactly what
was changed so you can be sure that it's not causing the load problem.
However, keep in mind that others have reported the exact same problem on
Win 7 x64, and I doubt they're using these mods - so I really feel they are
not relevant here. But it does mean that I have no choice but to run from
source.
_______________________________________________
SpamBayes@python.org
http://mail.python.org/mailman/listinfo/spambayes
Info/Unsubscribe: http://mail.python.org/mailman/listinfo/spambayes
Check the FAQ before asking: http://spambayes.sf.net/faq.html
