Hi Stratcat!

Thanks for the brain storming :)


Stratcat wrote:

so I'm assuming you meant "remove", rather than delete. If by some
chance you "deleted" the BOINC s/w, rather than "removed" it
via the Control Panel, this could easily have caused your probs. I hope
I haven't insulted your intelligence w/this suggestion. I'm just trying to
touch on all bases.

Uh oh, now that you mention ist, I'm not so sure about it.

Since the issue appears to be occuring during comm attempts, have you
ascertained the integrity of you networking h/w & drivers? IOW, your NIC
is fine, you haven't moved it around or messed w/the drivers, or done any
reconfig'ing (intentionally, or inadvertently) to your networking
parameters? Are other local apps able to comm, as usual, to the outside
world?

It's a reach, but have you considered  running Prime95 Torture for an
hour, or two, just to eliminate other possibilities? Again, I'm just
tossing out ideas.

No problems with other software. I ran the Prime95 test for a few hours
without any errors. In fact this computer sometimes acts as backup network
fileserver in our local LAN and happily delivers a lot of (big) files
(Linux Isos, OpenOffice.org builds and stuff..) for hours.

Did you set a sys restore point before the BOINC d/l, that you can return
to, or, if not, is there a restore point prior to the BOINC d/l that will
work for your current sys config? Sys restore has save my arse a few
times, particuliarly when I was running the dreaded WinMe.

Hey, good idea. I think I'll REMOVE :) BOINC, revert to a restore point
before my first BOINC install and start over again. If that doesn't help,
I'll have to check out the linux client :)

Oh, a last bit of information: The Computer runs WinXP HOME. Perhaps there's
a problem which only occurs on the HOME and not on the Prof. versions? But
that seems unlikely...

MfG

Sebastian Schildt