Rodney Pont | 1 May 10:06 2006
Picon

Re: New JBSWU beta uploaded

On Thu, 6 Apr 2006 18:25:40 -0400, John Small wrote:

>I have uploaded a new beta of JBSWU_MONITOR. The file name is jbswubeta.zip.
>
>The changes:
>  1) A fix for crashes which occur occasionally when there are no workunits in
>progress.
>  2) A fix for display corruption which occurs after uncommon TCP/IP errors
>occur.
>  3) Diagnostic code has been added to detect display corruption.

I've been running this since your April 17th update and have had no
problems at all so far. Usually no news is good news but I just haven't
had anything to report and it's about time I said so and thanks John.

Regards - Rodney Pont
E-mail by PMMail - listm4 <at> infohitsystems.ltd.uk

really weird out of context words courtesy of PMMail's spellchecker

 
WD Loughman | 1 May 11:11 2006
Picon
Picon

Re: New JBSWU beta uploaded

Rodney Pont wrote:
> On Thu, 6 Apr 2006 18:25:40 -0400, John Small wrote:
> 
> 
>>I have uploaded a new beta of JBSWU_MONITOR. The file name is jbswubeta.zip.
>>
>>The changes:
>> 1) A fix for crashes which occur occasionally when there are no workunits in
>>progress.
>> 2) A fix for display corruption which occurs after uncommon TCP/IP errors
>>occur.
>> 3) Diagnostic code has been added to detect display corruption.
> 
> 
> I've been running this since your April 17th update and have had no
> problems at all so far. Usually no news is good news but I just haven't
> had anything to report and it's about time I said so and thanks John.
> 
> Regards - Rodney Pont
> E-mail by PMMail - listm4 <at> infohitsystems.ltd.uk

John -

I've been running the same, since 4-16-06.  I did have problems and 
wrote you with screenshots attached.  I re-sent the attachments.  Never 
received acknowledgement, etc.

Did you receive the following?
____________________________________________________
John -
(Continue reading)

John Small | 1 May 15:25 2006
Picon

Re: New JBSWU beta uploaded

** Reply to message from WD Loughman <wdloughman <at> earthlink.net> on Mon, 01 May
2006 02:11:30 -0700

>
>I've been running the same, since 4-16-06.  I did have problems and 
>wrote you with screenshots attached.  I re-sent the attachments.  Never 
>received acknowledgement, etc.
>
>Did you receive the following?
>____________________________________________________
>John -
>
>The attachment contains three screen-shots:
>
>JBSWU_monA.jpg    40777   4-15-06   0:21 ImgWdl 4OS2 problem
>JBSWU_monB.jpg    48281   4-15-06   0:21 ImgWdl 4OS2 problem
>JBSWU_monC.jpg    44849   4-16-06   2:48 ImgWdl CMD.EXE is okay

Yes, I did. But I'm sorry to admit that it got overlooked until I saw this
message.

The new beta I uploaded today should fix "A" & "B".  The problem was that 4OS2
apparently displays a message when a file is deleted.  CMD.EXE does not.

>IMPORTANTLY, in "C" the blue demonstrates screen areas *not blanked* by 
>your WU-monitor -- causing the problem shown in "B".
>
>I had a similar corrupt display (under 4OS2) with an earlier version of 
>your WU-monitor.  Wrote you about it then; and you fixed it.
>
(Continue reading)

WD Loughman | 1 May 21:34 2006
Picon
Picon

Re: New JBSWU beta uploaded

John Small wrote:
> ** Reply to message from WD Loughman <wdloughman <at> earthlink.net> on Mon, 01 May
> 2006 02:11:30 -0700
	[  snip  ]
>>Did you receive the following?
	[  snip  ]
> Yes, I did. But I'm sorry to admit that it got overlooked until I saw this
> message.
> 
> The new beta I uploaded today should fix "A" & "B".  The problem was that 4OS2

It does eliminate the "A-B" problem.

> apparently displays a message when a file is deleted.  CMD.EXE does not.
> 
> 
>>IMPORTANTLY, in "C" the blue demonstrates screen areas *not blanked* by 
>>your WU-monitor -- causing the problem shown in "B".
	[  snip  ]
> "C" occurs when the background color is something other than the default
> (black).  Fixing "C" may take a while.  In fact I may not be able to fix it and
> therefore I would have to abandon the color for the messages displayed
> occasionally at the bottom of the screen.
> 
> As a temporary fix (which disables the color), you can do the following:
>    Lines 834-835 should read:
>       cfg.ansi = (CheckAnsi() == 1)
>       if cfg.ansi == 1 then
>    Insert a line between them so that they are:
>       cfg.ansi = (CheckAnsi() == 1)
(Continue reading)

John Small | 2 May 02:42 2006
Picon

Re: New JBSWU beta uploaded

** Reply to message from WD Loughman <wdloughman <at> earthlink.net> on Mon, 01 May
2006 12:34:15 -0700

>...  Another problem is back:
>Invoking the beta monitor from a CLI works just like from a desktop
>object.  EXCEPT: when closing the monitor window, the entire CLI window
>goes away too.

I'm not sure I understand this.  Are you saying that when you use CTRL+C to
terminate JBSWU, that one version of JBSWU closes the window and another does
not?

There is nothing in my program which should close the window as far as I know. 

My object has the following settings (which keep the window open after CTRL+C):
Path and file name: 	CMD.EXE
Parameters:		/k jbswu_monitor.cmd
Working directory:	<directory where jbswu_monitor.cmd and rexxrpc.cmd are
located>

I tried changing CMD.EXE to a full path and filename for 4OS2.exe.  This
doesn't work well.  It pegs my CPU meter even though I have the Seti client run
mode set to never.  I know little more about 4OS2 except that it exists (and
that is displays a message when deleting a file!?).  So I don't have any idea
why this is happening.

Then I moved the 4OS2 files into the path and just put 4OS2.EXE in the "Path
and file name" setting.  This worked well.

How is your desktop object set up?
(Continue reading)

John Small | 7 May 13:30 2006
Picon

Seti-Warp future?

I'm wondering about the future of Seti-Warp.

The following is on the Seti project page:

May 4, 2006  
We've started distributing work for a new version of SETI <at> home called SETI <at> home
Enhanced. 

And my Boinc client is reporting:

2006-05-07 06:27:40 [SETI <at> home] Sending scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
2006-05-07 06:27:40 [SETI <at> home] Reason: To fetch work
2006-05-07 06:27:40 [SETI <at> home] Requesting 42405 seconds of new work
2006-05-07 06:27:48 [SETI <at> home] Scheduler request to
http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
2006-05-07 06:27:48 [SETI <at> home] Message from server: No work sent
2006-05-07 06:27:48 [SETI <at> home] Message from server: (won't finish in time)
Computer on 98.9% of time, BOINC on 98.7% of that, this project gets 100.0% of
that
2006-05-07 06:27:48 [SETI <at> home] No work from project

I guessing
	- these are related.
	- the server wants to send work for the Seti <at> home enhanced version 
	- that without the "enhanced" Seti software there may not be future work for us

Please tell me I'm wrong or that there is hope for a Warp/eCS version of the
"enhanced" Seti software.

(Continue reading)

Robert Gammon | 7 May 13:50 2006
Picon

Re: Seti-Warp future?

The web page also said, We won't finish distributing the new client for 
at least a month, as we are concerned about the bandwidth needed to send 
out all the updates. 

We need a new client, yes, but we have some time

John Small wrote:

> I'm wondering about the future of Seti-Warp.
>
> The following is on the Seti project page:
>
> May 4, 2006 
> We've started distributing work for a new version of SETI <at> home called 
> SETI <at> home
> Enhanced.
>
> And my Boinc client is reporting:
>
> 2006-05-07 06:27:40 [SETI <at> home] Sending scheduler request to
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi
> 2006-05-07 06:27:40 [SETI <at> home] Reason: To fetch work
> 2006-05-07 06:27:40 [SETI <at> home] Requesting 42405 seconds of new work
> 2006-05-07 06:27:48 [SETI <at> home] Scheduler request to
> http://setiboinc.ssl.berkeley.edu/sah_cgi/cgi succeeded
> 2006-05-07 06:27:48 [SETI <at> home] Message from server: No work sent
> 2006-05-07 06:27:48 [SETI <at> home] Message from server: (won't finish in 
> time)
> Computer on 98.9% of time, BOINC on 98.7% of that, this project gets 
> 100.0% of
(Continue reading)

John Small | 7 May 14:14 2006
Picon

Re: Seti-Warp future?

** Reply to message from Robert Gammon <rgammon51 <at> yahoo.com> on Sun, 07 May
2006 06:50:55 -0500

>The web page also said, We won't finish distributing the new client for 
>at least a month, as we are concerned about the bandwidth needed to send 
>out all the updates. 

But I think that they will only be distributing clients for "supported
platforms" and OS/2 is not a "supported platform".

>We need a new client, yes, but we have some time.

Is anyone working on a new client?

--

-- 
John Small

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Get to your groups with one click. Know instantly when new email arrives
http://us.click.yahoo.com/.7bhrC/MGxNAA/yQLSAA/9rHolB/TM
--------------------------------------------------------------------~-> 

 
Robert Gammon | 7 May 16:47 2006
Picon

Re: Seti-Warp future?

My XP machine was on its LAST WU.  I used BoincMenu to tell it to go
get more work.

I downloaded the new client and 6 new workunits, all from 1999 data. 
CPU is overheated so I am stopping the client to let the cpu cool, and
then run benchmarks again.

My ecs11 machine was down to only 1 WU in queue.  I told it to go get
more work and it got 10 new WUs, also from 1999.

So the new cleint is starting to be distributed and workunits are
being fed to new and old clients.

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Everything you need is one click away.  Make Yahoo! your home page now.
http://us.click.yahoo.com/AHchtC/4FxNAA/yQLSAA/9rHolB/TM
--------------------------------------------------------------------~-> 

 
j675wy | 7 May 19:15 2006
Picon

Re: Seti-Warp future?

I have two machines that have now received the new "Enhanced" client
One is still working off old style units. Of course the OS2 machines
are still working on 4.18 units. I have also noticed that Seti has
said from time to time that it is not sending new units even as my
system requests some. I am guessing that they do not have enough of
both styles to go around. One of my machines processes with an
"optimized" client and it will not receive the new version either.
Guessing again that those using optimized clients and unsupported
clients such as OS2 will be able to process the 4.18 workunits for
some time to come. 
As far as a enhanced version for OS2 goes....Yuri has the knowledge
but I suspect he got "burned out" trying to get the 4.18 version
going. Do not know about any other possibilities, but then until it
arrived I did not know about the current OS2 client either. Gratefull
for Yuri's work though and hopes he will at least help in getting a
new enhanced version going. One of my machines was processing a
workunit in just under 4 hrs and now it looks like it will take about
7 hrs for the first enhanced unit. Can not say yet if that ratio will
hold. Later. John

--- In seti-warp <at> yahoogroups.com, Robert Gammon <rgammon51 <at> ...> wrote:
>
> The web page also said, We won't finish distributing the new client for 
> at least a month, as we are concerned about the bandwidth needed to
send 
> out all the updates. 
> 
> We need a new client, yes, but we have some time
> 
> 
(Continue reading)


Gmane