I don't know if any of you noticed, that my Seti production suddenly dropped off aproximately a month ago?
I work at a Call Center handling business data solutions (ie non private datalinks, ISDN, ADSL etc.), actually my primary function is making network statistics but that's a long story, anyway I'm superuser deluxe, god this is being long winded...
I'm the de facto administrator, so I have access to a lot of workstations (30-40 PII/I 300-866).
I shot down Seti because it interfered with Outlook. Every 5 min? Outlook would become totally unresponsive for a period of 3-5 sec.
A few users commented on this, of course they didn't know what caused it but I knew because it happened on my own workstation too when Seti was running.
Lately I've been trying out Genome, but it seems it's doing the same thing.
If I should venture a guess it would be that the background polling of the Exchange server is freezing Outlook. Under normal circumstances this is only taking a split second, but if the polling is running at lowest priority then it may be battling S@H/G@H for CPU time.
My questions (finally) are:
Does anyone know what I'm babbling about?
Does anyone know how to circumvent the problem?
My colleagues are very dependent on Outlook and I won't let these projects be a hindrance, also it could be looked upon as counterproductive, which would forfeit my permission to run them anyway.
It sure would be a waste
Misc.:
NT 4.0
Outlook 97
S@H as service
Kim
I work at a Call Center handling business data solutions (ie non private datalinks, ISDN, ADSL etc.), actually my primary function is making network statistics but that's a long story, anyway I'm superuser deluxe, god this is being long winded...
I'm the de facto administrator, so I have access to a lot of workstations (30-40 PII/I 300-866).
I shot down Seti because it interfered with Outlook. Every 5 min? Outlook would become totally unresponsive for a period of 3-5 sec.
A few users commented on this, of course they didn't know what caused it but I knew because it happened on my own workstation too when Seti was running.
Lately I've been trying out Genome, but it seems it's doing the same thing.
If I should venture a guess it would be that the background polling of the Exchange server is freezing Outlook. Under normal circumstances this is only taking a split second, but if the polling is running at lowest priority then it may be battling S@H/G@H for CPU time.
My questions (finally) are:
Does anyone know what I'm babbling about?
Does anyone know how to circumvent the problem?
My colleagues are very dependent on Outlook and I won't let these projects be a hindrance, also it could be looked upon as counterproductive, which would forfeit my permission to run them anyway.
It sure would be a waste
Misc.:
NT 4.0
Outlook 97
S@H as service
Kim
Comment