Path: utzoo!attcan!utgpu!watmath!watdragon!spurge!rszinn
From: rszinn@spurge.waterloo.edu (Scotte Zinn)
Newsgroups: comp.sys.amiga
Subject: Re: Xoper Bug Figured Out.
Message-ID: <17729@watdragon.waterloo.edu>
Date: 1 Nov 89 17:02:05 GMT
References: <970@unsvax.NEVADA.EDU>
Sender: daemon@watdragon.waterloo.edu
Reply-To: rszinn@spurge.waterloo.edu (Scotte Zinn)
Distribution: all
Organization: U. of Waterloo, Ontario
Lines: 37

In article <970@unsvax.NEVADA.EDU> maniac@arrakis.nevada.edu.uucp (ERIC SCHWERTFEGER) writes:
>
>     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.

I just extracted the binary file from the zoo file and ran it and it didn't
hang at all.  Thus, it will work without xoper.startup in s:

>     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.

I was also running it on the workbench screen from a WShell.

>     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.

Haven't tried the switches, wil try them as soon as I'm done everything
important since Murphy sometimes likes to play games.  :-)

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

I think that you should re-examine your configuration since what you have
found as the bugs aren't bugs for me.

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



---
Scotte Zinn
rszinn@spurge.uwaterloo.edu