Marc Lewis | 28 Jul 22:06 2013

V7 source code.

Hello All,

I  see  on  the  SETI Berkeley web site that the source code for V7 is
open-source.   Does anyone here have experience in compiling this type
of code to an OS/2 executable?

--

-- 
*****************************************
*  Best regards,
*  Marc.
*****************************************
IMPORTANT: This Message not valid without my S/Mime signature.
Attachment (smime.p7s): application/pkcs7-signature, 7547 bytes
Marc Lewis | 26 Jul 21:28 2013

More recent port.

Hello All,

Does anyone know if there's been, or will be a port of the more recent
BOINC (Seti <at> Home) client.  It would appear that the server is no
longer sending work compatible with the V5.x OS/2 BOINC client.

--

-- 
*****************************************
*  Best regards,
*  Marc.
*****************************************
IMPORTANT: This Message not valid without my S-MIME signature.
Attachment (smime.p7s): application/pkcs7-signature, 5008 bytes
j675wy | 15 Jun 05:48 2013
Picon

Seti version 7

For about a week now Seti has been using version 7. Still in use are the AP v6 work units, but Seti Enhanced v6 is
gone. That probably means that OS/2 does not have the right programs to process the new units unless
someone has the ability to convert the old to the new. John B

------------------------------------

ivanturner90 | 14 Jun 13:50 2013
Picon

No more jobs - wrong version.

I noticed the other day that none of my computers were getting new units.

Looking at the sched_reply_setiathome.berkely.edu.xml I find the following:
<scheduler_reply>
<scheduler_version>701</scheduler_version>
<master_url>http://setiathome.berkeley.edu/</master_url>
<request_delay>303.000000</request_delay>
<message priority="high">Unknown app name in app_info.xml</message>
<message priority="low">No tasks sent</message>
<message priority="high">Your app_info.xml file doesn't have a usable version of SETI <at> home v7.</message>
<message priority="high">Your app_info.xml file doesn't have a usable version of AstroPulse v6.</message>
<project_name>SETI <at> home</project_name>

It appears that they are now looking for v7 while all I have is v6.

Are we likely to get a v7 or is there a way to 'con' the server into sending units.  It would be a shame to stop now
after several years.

------------------------------------

Bob | 7 Nov 19:33 2012
Picon

Re: Stop getting new work

** Reply to message from "John Small jsmall-at-os2world.net" on Tue, 6 Nov 2012
06:22:04 -0500

> If you still have my utilities (specifically REXXRPC) then try:
> REXXRPC --project setiathome.berkeley.edu nomorework

Yes, I still have your utilities.  I will try it.

Thanks

------------------------------------

Robert Blair | 6 Nov 00:07 2012
Picon

Stop getting new work

How do I stop seti from getting new work and finish the work already
downloaded?  I have two computers running seti and want to stop one of them as
I want to retire that computer.  At one time I think I did this by creating a
file with a particular name in the bonic directory but I can not find any
documentation.

------------------------------------

Robert Gammon | 5 Jun 06:46 2012
Picon

Fwd:


http://asmacbcs.com/victory.php?xjfjzos=338&kydikorixi=28

------------------------------------

Christer Jacobsson | 7 May 07:05 2012
Picon

Re: JBSWU_Monitor have begun to bomb out!

John Small wrote:
> ** Reply to message from Christer Jacobsson <cribo.jacobsson <at> gaea.se> on Sat,
> 05 May 2012 21:41:43 +0200
> 
> 
>> John Small wrote:
>>> ** Reply to message from "Rodney Pont" <yhlisto4 <at> infohit.me.uk> on Sat, 05 May
>>> 2012 06:39:34 +0100 (BST)
>>>
>>>
>>>> On Fri, 4 May 2012 19:13:15 -0500, John Small wrote:
>>>>
>>>>> To test a fix for this, please do the following:
>>>>> 1) Open REXXRPC.CMD in an editor. (Be sure it is the one that will be called by
>>>>> JBSWU.)
>>>>> 2) At or around line 563 you should find the following 4 lines (watch for word
>>>>> wrap):
>>>>> RPC.Cmd.Prefix =   '<boinc_gui_rpc_request>' || RPC.eol || ,
>>>>>         '   <major_version>5</major_version>' || RPC.eol || ,
>>>>>         '   <minor_version>2</minor_version>' || RPC.eol || ,
>>>>>         '   <release>1</release>' || RPC.eol
>>>>> 3) Replace all four lines with the single line:
>>>>> RPC.Cmd.Prefix =   '<boinc_gui_rpc_request>' || RPC.eol
>>>>> 4) Save the changes.
>>>>>
>>>>> Let me know if this works (or at least gets farther before crashing).
>>>> I will try that when I go to v7 again.
>>> I am going to hold off uploading a new REXXRPC until you have had a chance to
>>> test this.
>>>
(Continue reading)

j675wy | 6 May 17:41 2012
Picon

To John Small

I just got notified that a file (JBSU_Monitor) has been uploaded and I checked. It has a date of May 5,2012, so
it looks like your upload was successful. Though in trying to look at the profile of any of the members I got a
"Not Found" message. Maybe Yahoo has other problems. John B

------------------------------------

Christer Jacobsson | 5 May 21:41 2012
Picon

Re: JBSWU_Monitor have begun to bomb out!

John Small wrote:
> ** Reply to message from "Rodney Pont" <yhlisto4 <at> infohit.me.uk> on Sat, 05 May
> 2012 06:39:34 +0100 (BST)
> 
> 
>> On Fri, 4 May 2012 19:13:15 -0500, John Small wrote:
>>
>>> To test a fix for this, please do the following:
>>> 1) Open REXXRPC.CMD in an editor. (Be sure it is the one that will be called by
>>> JBSWU.)
>>> 2) At or around line 563 you should find the following 4 lines (watch for word
>>> wrap):
>>> RPC.Cmd.Prefix =   '<boinc_gui_rpc_request>' || RPC.eol || ,
>>>         '   <major_version>5</major_version>' || RPC.eol || ,
>>>         '   <minor_version>2</minor_version>' || RPC.eol || ,
>>>         '   <release>1</release>' || RPC.eol
>>> 3) Replace all four lines with the single line:
>>> RPC.Cmd.Prefix =   '<boinc_gui_rpc_request>' || RPC.eol
>>> 4) Save the changes.
>>>
>>> Let me know if this works (or at least gets farther before crashing).
>> I will try that when I go to v7 again.
> 
> I am going to hold off uploading a new REXXRPC until you have had a chance to
> test this.
> 

As Salaam Aleikum!

I just downloaded the new version of JBSWU_MONITOR.CMD from Seti <at> home at 
(Continue reading)

John Small | 5 May 12:50 2012
Picon

Re: JBSWU_Monitor have begun to bomb out!

** Reply to message from "Rodney Pont" <yhlisto4 <at> infohit.me.uk> on Sat, 05 May
2012 06:39:34 +0100 (BST)

>On Fri, 4 May 2012 19:13:15 -0500, John Small wrote:
>
>>To test a fix for this, please do the following:
>>1) Open REXXRPC.CMD in an editor. (Be sure it is the one that will be called by
>>JBSWU.)
>>2) At or around line 563 you should find the following 4 lines (watch for word
>>wrap):
>>RPC.Cmd.Prefix =   '<boinc_gui_rpc_request>' || RPC.eol || ,
>>         '   <major_version>5</major_version>' || RPC.eol || ,
>>         '   <minor_version>2</minor_version>' || RPC.eol || ,
>>         '   <release>1</release>' || RPC.eol
>>3) Replace all four lines with the single line:
>>RPC.Cmd.Prefix =   '<boinc_gui_rpc_request>' || RPC.eol
>>4) Save the changes.
>>
>>Let me know if this works (or at least gets farther before crashing).
>
>I will try that when I go to v7 again.

I am going to hold off uploading a new REXXRPC until you have had a chance to
test this.

--

-- 
John Small

------------------------------------

(Continue reading)


Gmane