Path: utzoo!attcan!uunet!samsung!usc!apple!claris!sts!octopus!pyramid!prls!philabs!philmtl!zap!zoom!marc
From: marc@Clik.QC.CA (Marc Boucher)
Newsgroups: comp.sys.amiga
Subject: Re: Xoper Bug Figured Out.
Message-ID: <777@zoom.Clik.QC.CA>
Date: 2 Nov 89 23:51:14 GMT
References: <970@unsvax.NEVADA.EDU> <696@uwm.edu>
Reply-To: marc@Clik.QC.CA (Marc Boucher)
Organization: Clik Telematique Inc., Montreal QC
Lines: 37

In article <696@uwm.edu> duncan@csd4.csd.uwm.edu writes:
!From article <970@unsvax.NEVADA.EDU>, by maniac@arrakis.nevada.edu (ERIC SCHWERTFEGER):
!> 
!>      Well, after much fighting, I think I finally figured out the problems
!> with Xoper 2.0 (yes, I meant plural).
!>      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.
!>      In other words, you must have a file "xoper.startup" in s:, and you
!> must also specify "usescreen" as an option in that file.
!> 
*** sorry, but my xoper crashes if I put "usescreen" in the startup file..
which looks like:

IconifyOff
TrapGuru
; UseScreen
Hide Xoper
Hide RAM
Hide CON
Hide NULL
Hide NEWCON
Hide DH0
Hide A590/A2091 IORequest handler
Hide A590/A2091 SCSI handler
Hide File System
Hide input.device
Hide trackdisk.device
Hide DMouse
Hide Snap


!Good work Eric!
	Really? :-)

-- 
Marc Boucher, sys/netadm @ Clik Telematique Inc - marc@clik.qc.ca | zoom!marc
5144668932_home 5149337161_clik 5149332164_fax  - uunet!philmtl!zap!zoom!marc