** Reply to message from WD Loughman <wdloughman@xxxxxxxxxxxxx> 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?
P.S. I'd get around to writing an install program but there are a lot of
complicating issues:
- close the window or not on exit? (You and I might prefer the second option
but many might prefer the first.)
- which command processor to use?
- automatically start on bootup?
- if yes, should the Boinc/Seti software be started first?
- if yes, then how to control the sequence?
- What working directory should be used?
- Is REXXRPC available?
- Should an install program offer to assist in customizing JBSWU (through the
.CFG file)?
- if yes, then how?
--
John Small
|
