The problem is that the CLI runs at priority 4 and Outlook XP, 2003, and
Windows XP all have user interface threads that run below this priority.
SETI Driver has an "IDLE" setting that will force the CLI to run at priority
1, which will eliminate this problem.

Mike Ober.
http://www.wakeassoc.com/setidriver

"salvatore" <salvatore.palmisano@gmail.com> wrote in message
news:98861b00.0409271053.5546310b@posting.google.com...

Anyone experience a slowdown of Outlook 2003 while running the S@H
CLI?  Ive found it slows to an unusable state while S@H is running,
and shutting it down immediately alleviates the problem.

All of this of course on win32 systems, specifically WinXP Pro SP2.

Thanks.

-- 
.salvatore
blatherings - http://www.sienar.org/
general nonsense - http://www.palmisanonet.com/
psn radio - http://www.palmisanonet.com:9875