Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!ucsd!usc!cs.utexas.edu!uunet!unsvax!arrakis.nevada.edu!maniac
From: maniac@arrakis.nevada.edu (ERIC SCHWERTFEGER)
Newsgroups: comp.sys.amiga
Subject: Xoper Bug Figured Out.
Message-ID: <970@unsvax.NEVADA.EDU>
Date: 31 Oct 89 20:32:31 GMT
Sender: news@unsvax.NEVADA.EDU
Reply-To: maniac@arrakis.nevada.edu.uucp (ERIC SCHWERTFEGER)
Distribution: all
Organization: Univ of Nevada System Computing Services - Las Vegas
Lines: 15


     Well, after much fighting, I think I finally figured out the problems
with Xoper 2.0 (yes, I meant plural).
     First of all, Xoper will hang if you don't have "xoper.startup" in s:,
but this could be related to another bug.
     Second, if you don't specify "usescreen" in the xoper.startup file,
Xoper will attempt to open a window on the WB screen, and will hang.
     Finally, you can't use the -b command on the CLI line, nor can you
use the "hold" command in the xoper.startup file, because both cause
XOper to get hung up.

     In other words, you must have a file "xoper.startup" in s:, and you
must also specify "usescreen" as an option in that file.

Eric Schwertfeger, UNLV, maniac@arrakis.nevada.edu