In article <1206bb1a.0310100711.127c15c8@posting.google.com>, Eric
<eschristie@yahoo.com> writes

Hello,

I have a new dual CPU computer running Win2k.  I would like to use
SetiDriver and SetiSpy to run more than one instance of CLI.  How can
I do this so that one WU is running on one CPU while a different one
is running on a differnet CPU?  If I cannot use these apps to do this,
is there another way?  IT group will not allow any OS other than
Win2k, so no HT capability.  Both processors are XEONs.

Thanks in advance,

E.

I run a dual proc P3 under Win2K Pro. I have a folder titled SETI,
located at <C:\program Files\SETI@Home>. I have placed the following in
it -

        The CLI (.i386-winnt-cmdline)
        SETI Driver
        SETI Spy

On launching Driver and Spy, Driver should default to Maximum processes
2. You need to set the cache size, then log on to Berkeley and down load
WUs. The system then runs fine. You will also need to tick the "Set
Processor Affinity" box. The 2 instances of the CLI, when WUs
downloaded, will be locked to individual processors.

On my network I also have dual 2.8 Ghz Xeons, with HT enabled. This runs
4 instances of the CLI using the same set up as the dual P3. The
difference is Win2K on the P3 and XP Pro on the dual Xeon.

I wanted to use Win2K on the dual Xeon, but when Win2K was installed and
S@H run. We found the OS just saw processor 0 and it's HT virtual
processor (as processor 1). It ran 2 instances of the CLI, but did not
use the other processor.

Win2K's license is for 2 processors, however these are presented. So,
with HT enabled the OS should see 4 processors (WinXP Pro does). Win2K
will see the 1st real Xeon, and it's HT virtual processor. The 2nd Xeon
is spare and forgotten. You may as well have a single proc system.

I assume you can get the 2 Xeons seen by Win2K by turning off HT in the
BIOS. This means Win2K can see 2 real processors. So, to allow Win2K, as
you are forced to use, to see dual processors HT needs to be disabled.

Hope this makes sense and helps?

NOTE:   I ran my dual Xeon with - (a) 1 instance of the CLI; then,
        (b) 2 instances of the CLI; and, finally, (c) 4 instances of the
        CLI. Each addition slowed the individual WU crunching times, but
        the total output rose. In broad detail the results, over 30 WU 
        each set up, was -

        1 CLI  - normal WU crunch times between 2.00 hrs and 2.50 hrs
        2 CLIs - normal WU crunch times between 3.10 hrs and 3.50 hrs
        4 CLIs - normal WU crunch times between 4.50 hrs and 5.50 hrs
-- 
John Clark