Martin <ml_news@ddnospamddml1dd.co.uk.dd> wrote in message news:<L2Bwc.23$Tp4.12@newsfe6-gui.server.ntli.net>...

George wrote:
[...]

Good thought, but that's not a problem.  Comp gets cleaned once a month 
reguarly, since it's in a business environment.  Uninstalled SETIQueue 
(which, BTW, I notice the SQ homepage is gone) but still having problems 
with SETI hanging.

That 'business environment' means nothing for clean computers.

You may well have the outside of the case nice and clean and shiny. The 
inside may well be full of thermally insulating dust, with a fan choked 
to a feeble slow rotation, and everything running nicely hot.

If the insides are clean and the fans are working, then next try 
remounting the CPU heatsink with some fresh thermal grease (clean off 
the old stuff first). If still not working, then you've likely got some 
capacitors on their way out on the motherboard or in the PSUs.

Try memtest86 to check out the RAM, and the GIMPS torture test to check 
out the CPU & RAM.

Silicon runs better the cooler it is.

Good luck,
Martin

I posted the "Setiqueue Blues" message, the computer internals are
clean, yet the problems that I conveyed still exists. I strongly feel
that the problems that I am experiencing with seti driver and
setiqueue are somehow a setiqueue software/network related problem.

In addition to having an internally clean machine, I have performed a
clean Win2k install with only seti driver and setiqueue, downloaded
fresh copies of seti driver and setiqueue, MD5 checked the products,
installed a clean Win2K installation on a new motherboard and hard
drive, changed setiqueue connection type (i.e. Default Winet, WinNet
Direct, etc.) and I refreshed the firmware on my router.

Under these conditions, with a new machine, clean install and fresh
copies of seti driver & setiqueue, the same problems that I reported
earlier in message "Setiqueue Blues" still exists. It seems reasonable
to me that the same errors would not persist with a new machine, a
clean install, and fresh copies of seti driver and setqueue.

Presently, the only configurations that work within my home network
are: (1) PC A with seti driver using PC B's setiqueue and PC B with
seti driver using PC A's setiqueue or (2) PC A & B seti drivers
uploading to a public Setiqueue host.

Setiqueue will simply not correctly serve a local seti driver client
on the same machine, it will receive the result, attempts to download
a wu, records the wu in the pending queue and then lockup the machine
during the download to the seti driver client and kill all tcp/ip
processes. There are no error messages generated in the Win2K system
event logs and there is no indication within setiqueue logs about a
problem with all of the debug options set.

The only way to resolve this is to reboot the machine. I truly do not
understand why a stable environment suddenly behaves this way. If
anyone has an answer, please share your advice.

Thanks,
Benu