In article <1109617634.090577.229720@g14g2000cwa.googlegroups.com>,
 <linus_das@yahoo.co.uk> wrote:
  [ ... ] 

Normally these machines work very reliably, so surely S@Hmust have been
the cause.  I find that amazing, as I'veused SETIStash + Classic CLI on
my own Windows 2000 box for the past 5 years with no issues whatsoever
- I can'ttell the difference whether S@H is running or not.  Whatwent
wrong on these Win XP Pro boxes?  Were they short on memory (my home
box is 576 MB vs 256 MB for these) or was it some kind of resource
conflict?

What were the processor temps? S@h will cause them to run much hotter
than normal, and if the systems have a cheap/marginal HSF, are full
of dust, or have insufficient airflow problems, the CPUs may be slowed
to reduce heat or can lock up. 

Install Motherbord Monitor if they don't have something that lets you
keep an eye on the temps, and see if they spike when S@h is started.

I had a system get full of dust recently; in BIOS setup, it was showing
56C at idle. After cleaning, it's running at 54C while crunching.


Gary

-- 
Gary Heston  gheston@hiwaay.net 

"I should have known something was up. She had all her teeth."
Potential juror re: being arrested for solicting an undercover officer.