Path: utzoo!utgpu!attcan!uunet!cs.utexas.edu!sun-barr!lll-winken!ames!attctc!davidg
From: davidg@attctc.Dallas.TX.US (David Guntner)
Newsgroups: comp.sys.amiga
Subject: Re: Xoper Bug Figured Out.
Message-ID: <10039@attctc.Dallas.TX.US>
Date: 5 Nov 89 20:23:49 GMT
References: <970@unsvax.NEVADA.EDU>
Distribution: all
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 25

From article <970@unsvax.NEVADA.EDU>, by maniac@arrakis.nevada.edu (ERIC SCHWERTFEGER):
>      First of all, Xoper will hang if you don't have "xoper.startup" in s:,
> but this could be related to another bug.

It is.

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

You just found it. :-)

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

Near as I can figure, the only reason that you HAVE to have a s:Xoper-startup
file is because without it, you can't specifiy a line which says "usescreen".
Without that, the default is "usewindow", and THAT will hang the program (and
trash something in low memory, according to GOMF...).
            --Dave

-- 
        David Guntner  UUCP: {ames, mit-eddie}!attctc!davidg
                       INET: davidg@attctc.Dallas.TX.US  (killer)
"...New ship, but she's got the right name. ...Treat     --Admiral L. McCoy
 her like a lady, and she'll always bring you home."   "Encounter at Farpoint"