Path: utzoo!utgpu!attcan!uunet!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: <10040@attctc.Dallas.TX.US>
Date: 5 Nov 89 20:29:05 GMT
References: <696@uwm.edu>
Distribution: all
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 17

From article <696@uwm.edu>, by duncan@csd4.csd.uwm.edu (Shan D Duncan):
> I reread the docs and it does say xoper will not startup until after
> the file xoper.startup has been read.  He also says the file goes in
> S:

Actually, it says that it will read in a s:Xoper-startup file, IF IT IS
AVAILABLE.  In other words, you shouldn't HAVE to have the file there for the
program to work.  However, the default condition is usewindow if you don't
have the file there with a line saying usescreen, and usewindow will hang you
out to dry....
             --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"