Sorry 'bout this tardy response.
John Small wrote:
> ** 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?
No, no. When I invoke the monitor by command-line *from within a
command-line window*:
1) The monitor opens (in a new[?] NON-resizable window), and
2) the original command-line window goes away.
3) The monitor works just fine. And *thanks* for your efforts!
If then I use ctl-c to close the monitor:
1) It stops, and...
2) ...the command-line prompt returns - as though I'd gotten back my
original window. BUT...
2a) ...it's not the original - it's not resizable. Doing anything
useful in that small window is an exercise in frustration.
>
> There is nothing in my program which should close the window as far as I
> know.
Perhaps it's resizing the original, then hi-jacking it. The *effect* is
as though it closed. What's left after closely the monitor isn't useful.
I do a huge amount of work from the CLI.
Losing the CLI every time I invoke the WU-monitor is a real drag.
Getting a new CLI, changing drives and directories, drilling down to
where I need to be... A drag.
>
> 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've tried "everything". No joy.
Using "Path and file name: CMD.EXE" in the object defeats my use of 4OS2
of course.
Invoking the monitor under CMD.EXE (instead of 4OS2) also behaves as
I've described above.
>
> 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.
I'd imagine it might seem to, if you've not enhanced 4OS2 with various
colors for characters and backgrounds.
>
> How is your desktop object set up?
Path and file name E:\JBSWU_Monitor\jbswu_monitor.cmd
Parameters none/blank
Working directory E:\JBSWU_Monitor
My desktop object isn't a problem. This works exactly as advertised.
[Well, apart from the incomplete background wiping under 4OS2...]
--> It's running the monitor from the CLI that concerns me.
- Bill
--
WD "Bill" Loughman - Berkeley, California USA
http://home.earthlink.net/~wdloughman/wdl.htm
------------------------ Yahoo! Groups Sponsor --------------------~-->
Home is just a click away. Make Yahoo! your home page now.
http://us.click.yahoo.com/DHchtC/3FxNAA/yQLSAA/9rHolB/TM
--------------------------------------------------------------------~->
|
