Peter Krueger <spam_korb@lycos.de> wrote in message news:<boefra$3h9$07$3@news.t-online.com>...

Ravenmadtaoist wrote:

average, 107+ hours.  The one I am currently processing is at about
50% in under 9 hours....  As it's such a large discrepancy I was

My AMD 600mhz normally uses around 10 hours for one WU. Maximum around 
14 hours. But I use the DOS Version and not the GUI interface.

Variation will be also very high, if parallel processes like gaming ... 
are take part.

Peter

Hi :)

Yes, I am aware that other processes running parallel would slow it
down.  That's why I found the extended length of time so odd....

I have a blank desktop... no icons.  I have screen saver and sleep
modes disabled.  During the time that those two particular WU's were
processing there was no gaming.  No viruses present and no spyware.  I
did several complete shutdowns (instead of restarts) and even shut
down folding. SETI process still remained at a snail's pace. At no
time have I experienced the fatal shutdown error or problems with
submitting WU's either.  Upon continued inspection there has not been
any significant difference in performance when Outlook is running.
Which was why I was at a loss and concluded that there must be some
aspects to the WU's that would cause variations in processing.  I was
thinking it was possible that those WU's may have been corrupted but
they did complete (finally) and submitted without issues...

For some undetermined reason I've never been able to run the DOS
clients for folding or SETI on this comp.  When installed they cause
repeated system crashes.  As everything else runs on here the way I
want it too I simply bit the bullet and installed GUI for both.

Thank you for your input :)  I guess I should have been clearer as to
the extent I was "trouble shooting" before I posted.  It really was a
source of frustration!  As it stands now I have processed 5 since and
they have taken anywhere between 8 and 12 hours.  I completely disable
my DC clients when my kids play Sims, it seems to cause video driver
conflicts, otherwise I'm sure there'd be more done :)