"Brian Cleverly" <Brian.cleverly@btinternet.com> wrote in message
news:3FA64A87.534D6107@btinternet.com...

f/fgeorge wrote:

Are you the screen saver or the command line version?
The command line version(cli) is much better at stopping itself to let
other programs use cpu cycles than the screen saver version.

On Mon, 3 Nov 2003 09:36:29 +0000 (UTC), Brian Cleverly
<Brian.cleverly@btinternet.com> wrote:

my seti program has been chugging away on my Laptops for a few tears

now

quite happily from one Pc upgrade to another. however I have found that
with outlook 2002, when the client does a synchronisation with the
server, it takes hours if seti is still running. If I take seti off,
then it's minutes. i notice on the Task manager that Seti has 99% of

the

resources, but it does seem to release them when I use other programs.
BTW I have Seti on all the time. The laptop runs w2000 pro, has 256Mb
RAM & a P4 1.4G processor. as above, I only have issues when Outlook is
synchronising, any ideas?

screen saver version, but really confused as to why it only affects the
synchronisation

Seti is designed to run at a low priority so as not to effect the CPU usage
of other programs. However sometimes other programs are also scheduled to
use low CPU, syncronization is intended to be done in the background and not
effect any foreground tasks. Sometimes windows doesn't manage to balance the
2 low priority tasks (in theory they should get 50% CPU each) and so the
other task geys virtually nothing. One way is every time you run
syncronization, goto task manager, select progresses, right click the
syncronize task and select the medium priority level.

Jonathan