Path: utzoo!utgpu!attcan!uunet!snorkelwacker!think!ames!attctc!davidg
From: davidg@attctc.Dallas.TX.US (David Guntner)
Newsgroups: comp.sys.amiga
Subject: Re: Xoper 2.0 in binaries - dead?
Message-ID: <10037@attctc.Dallas.TX.US>
Date: 5 Nov 89 20:09:06 GMT
References: <671@uwm.edu>
Organization: The Unix(R) Connection, Dallas, Texas
Lines: 31

From article <671@uwm.edu>, by duncan@csd4.csd.uwm.edu (Shan D Duncan):
> 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...
 
There definately seems to be some kind of bug here.  When I run it as such, I
get the same thing (blank window that you can't do anything with), plus the
GOMF requestor (I'm running v3.0, with the switch set to watchdog low memory
vector tables) pops up screaming that something trashed low memory.  It's able
to fix the vector tables, but it can't seem to find the window of the program
(automatically) and remove it as part of the cleanup process.  This only seems
to happen if you're trying to use a window on the WorkBench screen.  If you
create a s:Xoper-startup file, and in it include a line saying "usescreen"
(don't put in the quotes), it will create it's own custom screen and use it 
instead.  This screen works fine.

> A2000 2mg (40 meg quantum with GVP conroller 1 mg). 1084 and 2 floppies.
> Running under Wshell.
 
I'm using an A500 with an A501 memory expansion, and one external drive.
                     --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"