Minor bad news

[micron]

<< Seti does affect something - Outlook. >>

It doesn't effect Outlook 2000 on my dad's machine 😕.

 

[torque2k]

<< First thing blamed? The SETI client - which isn't even installed or running on the box! >>



That's what you get for installing SETI on a box with an EDIot attached to it... 😀

Peace!
Torque2k

 

[Migroo]

Yeah I hear there are different cases.

My machine: Outlook 98
My Office: Outlook 2000

Both machines running CLI and Windows 2000, both Outlooks are heavily affected by SETI.

 

[Maggotry]

Yeah, no problem with Outlook Express in 98SE, ME, or XP.

 

[Migroo]

Hmm, thanks Micron and Maggotry.

I'd like to get this cleared up, as its annoying. It gives short burts of inactivity for Outlook, as if it times out for 5 seconds or so and doesnt respond.

Its not enough for me to remove SETI on affected machines, but you can relate to how annoying a problem can be 🙂

 

[Sukhoi]

<< Is there a simple benchmark that could be run to demonstrate that the client does not impair performance? It would be nice to have something objective to throw in the faces of the alarmists.

-bazilla >>



You could just run Sandra twice or something. 🙂

 

[Crazee]

I have no problem with Outlook XP at home.