Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!samsung!gem.mps.ohio-state.edu!ctrsol!emory!auc!haj
From: haj@auc.UUCP (Harvey Johnson)
Newsgroups: comp.sys.amiga
Subject: Re: Xoper 2.0 in binaries - dead?
Summary: Place Xoper.startup in S:
Message-ID: <32309@auc.UUCP>
Date: 29 Oct 89 22:10:14 GMT
References: <671@uwm.edu>
Reply-To: haj@auc.UUCP (4-Harvey Johnson)
Organization: Atlanta University Center
Lines: 22

In article <671@uwm.edu> duncan@csd4.csd.uwm.edu (Shan D Duncan) writes:
>I recently download the 2.0 version of Xoper and have not had any luck
>with the executable as posted.
>
>I get a blank window that will not accept input, can not be
>killed with the window gadget and will not iconify.
>
>Is this a problem with xoper 2.0 as it was posted to c.b.a? Or...

When I first ran Xoper, the same thing happened to me, so I went back and
read the documentation and saw that I forgot to place "Xoper.startup"  in
"s: " as instructed.  Once I did this, everything worked fine.  However,
using the -b option hung up, so I just used Xoper.

The program is quite nice, running quietly in the background until needed.
It is similar to the 'monitor' command on the VAX.  Since I almost entirely
use the CLI (shell) interface, it comes in very handy for tracking tasks
and processes (also, memory, resources, devices, etc.).

Setup:  Amiga 500 expanded to 1M (A501).

harve!