I wish someone would write a program, so that as soon as BOINC crashes or fails to run, my computer AUTOMATICALLY starts the SETI@Home CLassic.

At the moment I am trying to decide whether to stay (and wait out a delay) with BOINC, or just to stick to SETI CLASSIC that is 100% more reliable.

If someone could program it so that as soon as one went off line the other started, my computer could still work on units!

Hey, If you don't want to Beta test then why do you?

I would recommend sticking with the classic until BOINC goes public (non Beta) if you want 100% runtime.

anyway just make a batch file (.bat) with the commands in it... should work

runseti.bat
----
c:/path/to/boinc/boinc_gui.exe
c:/path/to/seticlassic/setiathome.exe
----
this should start boinc and when boinc exits starts seti classic

Happy crunchin'

Will that really work?

Boinc never "exits", it just stops sending or receiving project credit.

I'd still have to manually close BOINC to trigger Seti....or would I?











> Hey, If you don't want to Beta test then why do you?
>
> I would recommend sticking with the classic until BOINC goes public (non Beta)
> if you want 100% runtime.
>
> anyway just make a batch file (.bat) with the commands in it... should work
>
> runseti.bat
> ----
> c:/path/to/boinc/boinc_gui.exe
> c:/path/to/seticlassic/setiathome.exe
> ----
> this should start boinc and when boinc exits starts seti classic
>
> Happy crunchin'
>
>
>
>

Improved version of Windows stuff:

runseti.bat
----
:loop
c:/path/to/boinc/boinc_gui.exe
c:/path/to/seticlassic/setiathome.exe
goto loop
----

What about telling for which OS? I did something like that for Linux using watch, pgrep, and kill. And it's displaying the log-messages from BOINC and some progress statistics.

> Will that really work?
>
> Boinc never "exits", it just stops sending or receiving project credit.
>
> I'd still have to manually close BOINC to trigger Seti....or would I?
>


well, you said when BOINC crashes...

if BOINC doesn't crash but it is the seti client that fails you should have said that in your question...

BOINC isn't seti so it's good to keep them apart.


I don't really know how to see if BOINC is actually crunching.

For the commandline client there is a flag

-exit_when_idle Get/process/report work, then exit

this might help you as the BOINC client will exit when it doesn't have any work.


so another version might be

runseti.bat
----
:loop
c:/path/to/boinc/boinc_cli.exe -exit_when_idle
goto loop
----

This is probably a really bad way to do it... but it might work for crashes atleast. Not for lack of work from server.

I think I've said more than I should here so...

Hope you get it working the way you want it :)

I'll leave it be for now.

But many thanks for your help.

It's much appreciated :)


> > Will that really work?
> >
> > Boinc never "exits", it just stops sending or receiving project credit.
> >
> > I'd still have to manually close BOINC to trigger Seti....or would I?
> >
>
>
> well, you said when BOINC crashes...
>
> if BOINC doesn't crash but it is the seti client that fails you should have
> said that in your question...
>
> BOINC isn't seti so it's good to keep them apart.
>
>
> I don't really know how to see if BOINC is actually crunching.
>
> For the commandline client there is a flag
>
> -exit_when_idle Get/process/report work, then exit
>
> this might help you as the BOINC client will exit when it doesn't have any
> work.
>
>
> so another version might be
>
> runseti.bat
> ----
> :loop
> c:/path/to/boinc/boinc_cli.exe -exit_when_idle
> goto loop
> ----
>
> This is probably a really bad way to do it... but it might work for crashes
> atleast. Not for lack of work from server.
>
> I think I've said more than I should here so...
>
> Hope you get it working the way you want it :)
>
>

> Hey, If you don't want to Beta test then why do you?
>
> I would recommend sticking with the classic until BOINC goes public (non Beta)
> if you want 100% runtime.

-Cough-

BOINC has gone public. The beta project was shut down shortly after this site came online. Yes, the applications do still say "beta", but this is the public release.