My computer locks up solid after it finishes retrieving the files it needs and starts to process.
I had this same problem when I had tried switching from a DOS based SETI program to BOINC, and gave up and went back to DOS.
I had hoped that by now BOINC had fixed whatever was wrong with it, and am afraid it is still borked, for me at least.
Is there a DOS based version that would work, or am I not going to be able to help in this?
--------------------
Using BOINC Version 4.13
Windows XP Pro
ASUS A7N8X-E Deluxe
AMD 2400(2.18 GHz)
1.5 GB RAM
Ti 4200

To eliminate possible causes, experiment running the 2400+ at its spec speed of 2 GHz. If that doesn't help, try relaxing memory timings a little.

CPDN is more taxing on CPU and memory than pretty much any other DC project so you are not alone in having instability problems with it, but many people run it stably on a wide variety of platforms for long periods of time so it can be done.

Let us know how it goes.

Thanks for the fast response. :)
When I was running SETI as a DOS program, I think it was cranking out the units in about 2.2 hrs or so, and it was eating up as much processing power as I could give it.
I just tried running the program as a Service, and as soon as the Work Unit started, it locked up solid too. An error message pops up as soon as Windows starts to load. "Failed to clean the windows socket interface."
--------------------
Using BOINC Version 4.13
Windows XP Pro
ASUS A7N8X-E Deluxe
AMD 2400(2.18 GHz)
1.5 GB RAM
Ti 4200

> When I was running SETI as a DOS program, I think it was cranking out the
> units in about 2.2 hrs or so, and it was eating up as much processing power as
> I could give it.

I'm not sure what that means in response to my suggestion. SETI isn't CPDN and different DC projects will stress the CPU and memory differently, to greater or lesser extremes, even if those different projects are utilizing 100% of the CPU. CPDN stresses them to the greater exteme. Another DC project running at 100% CPU utilization does not necessarily put the same amount of stress on the PC.

> I just tried running the program as a Service, and as soon as the Work Unit
> started, it locked up solid too. An error message pops up as soon as Windows
> starts to load. "Failed to clean the windows socket interface."
> --------------------

That error message usually means that something is trying to start another instance of CPDN. If you start it as a service when it has already started manually or through the startup folder, it will give this error.