I have a few spare machines lying around that I'd like to put to use when I'm not using them for coding/testing purposes for my apps.

I have a COMPAQ Prolinea 575 (upgraded to Pentium 120MHz) running Windows 95A, a Pentium 166MHz Classic clone running Windows 95A, and a unknown Micron machines upgraded to a Pentium 150MHz CPU running Windows NT 4.0 SP6a. All of them have BOINC installed and running, and all of them attempt to get data but keep getting "No Work from Project" messages even though all my other machines are receiving work units.

Are these machines considered to be too slow for BOINC to give them data? Is there any way I can use these machines to help in the SETI cause?

Thanks in advance.

SETI and other BOINC project dish out work using benchmarks that the client has taken... This ensures that there is enough RAM/HDD space to crunch the numbers. You should be able to run SETI on the NT machine at least, if it has the memory. (I'm not sure about Win95 support.)

> SETI and other BOINC project dish out work using benchmarks that the client
> has taken... This ensures that there is enough RAM/HDD space to crunch the
> numbers. You should be able to run SETI on the NT machine at least, if it has
> the memory. (I'm not sure about Win95 support.)
>
>
>
>

Thank you for asnwering. The Prolinea has a 700MB hard drive with 250MB free and 64MB of RAM (which I believe is the minimum for BOINC), the Clone has a 2.1GB hard drive with about 1GB free and 64MB of RAM as well, the Micron has 2.1GB hard drive too with about 1.7GB free and currently only 48MB of RAM that I plan to upgrade later (I plan on maxing out each system on RAM).

I was under the impression that each system met the minimum requirements and I thought all Win32 OSes were supported. Wouldn't the installer inform you if you don't meet the minimum requirements, or at least won't the program warn you?

> > SETI and other BOINC project dish out work using benchmarks that the
> client
> > has taken... This ensures that there is enough RAM/HDD space to crunch
> the
> > numbers. You should be able to run SETI on the NT machine at least, if it
> has
> > the memory. (I'm not sure about Win95 support.)
> >
> >
> >

> The minimums for BOINC and any given project that runs under BOINC may be
> different. BOINC itself uses less than 20 MB HD. S@H uses about the same.
> Predictor requires 150MB, and CPDN requires 600MB free. BOINC and S@H require
> 64 MB of RAM to run. I belive that Predictor will run in the same. CPDN
> requires more, but I am not certain how much.
>
> I am running S@H and Predictor on BOINC on a machine with 64MB of RAM, about
> 250 MB free HD, and a 166Mhz Processor. Recently I have switched it over to
> 4.x to run BOINC Alpha, and test a failure case in CPDN (it should not get
> work, but earlier it was).
> <img> src="http://15.boinc_alpha.sig.boinc.dk?142">
>

So that means since there are multiple project capable of running on the BOINC infrastructure that the installer and program will not warn me if I don't meet the requirements because each project has different requirements.

So then the next logical question is, does anyone know if those systems meet the requirements or if there's some sort of setting that I must apply to get them to receive WU?

Last minute update - I just checked the Micron machine running NT4 and it *IS* recieving WU, so I'm presuming that Win95 isn't supported under S@H/BOINC? I'd be willing to upgrade to Win98 but I have an explicit use for multiple OSes on seperate machines (I'm still trying to figure out how to get OS/2 Warp 3 non-connect to network) and it seems a waste of CPU cycles to let them just sit there. But I suppose if I have no choice then so be it.