jsmall@xxxxxxxxx wrote:
> >I am getting arithmetic overflow when using the
latest
> >version of JBSWU_Monitor when talking to a windows
> >5.15 enhanced client. This occurs on line 509, and
is
> >a division by zero error.
>
> I am not home. And I do not know how to find a
certain line number using Windows NotePad or WordPad.
But I am guessing that the line 509 is:
> est_total_time = (fpops_est / pfpops) * fact
>
Yes this is the line that Windows reports the divide
by zero error.
> If this is correct, please do the following:
> 1) Use BOINC_CMD or REXXRPC to execute a
"--get_state" command directed to the Windows host.
> 2) Look for the following lines:
> a) the line containing "<p_fpops>"
> b) the line containing "<rsc_fpops_est>"
> On each line there will be a number following the
text given above. Please tell me what these numbers
are. There is no hurry because I will not be able to
fix this before I return home sometime this weekend.
>
boinc_cmd on both Windows and OS/2 do not return fpops
or rsc_fpops_est. I captured both outputs into a text
file and searched for the phrase.
rexxrpc returns the following for Windows
<p_fpops>832568688.373786</p_fpops>
<rsc_fpops_est>60303256868631.898000</rsc_fpops_est>
rexxrpc returns the following on the ecs11 machine
<p_fpops>306053743.037277</p_fpops>
<rsc_fpops_est>27924800000000.000000</rsc_fpops_est>
The fpops numbers make sense as Windows is a 2GHZ
pentium that throttles back but give fp benchmarks of
about 1000, while the OS/2 machine give fp benchmarks
of about 400.
AND NOW ITS WORKING FINE. The WU has progressed to
about 45% complete. The problems were observed when
the %complete was very low.
> >Also, I am not that familiar with ANSI under XP,
but
> >with ANSI on in JBSWU_Monitor.cfg, ANSI commands
are
> >not interpreted, they are merely echo's to the
screen.
>
> So I am TRYING to get the latest JBSWU_Monitor
working
> on XP, but no dice.
>
> You can turn off the use of ANSI by having a
JBSWU_MONITOR.CFG file with a line:
> ANSI=0
> This file should be in the same directory as
JBSWU_MONITOR.CMD.
>
I turned ANSI off in the CFG file.
> When I return, I will change JBSWU so that it
defaults to ANSI=0 when it runs on Windows.
>
Good idea until we figure out how to make cmd /a work
to sttart a command window with ANSI commands turned
on in XP.
Robert Gammon
Houston, TX
------------------------ 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
--------------------------------------------------------------------~->
|
