Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!mips!pacbell.com!ucsd!nosc!crash!pro-graphics.cts.com!critical.mass
From: critical.mass@pro-graphics.cts.com (Peter Altamore)
Newsgroups: comp.sys.amiga
Subject: ScreenXv3.0
Message-ID: <6557@crash.cts.com>
Date: 27 Dec 90 12:16:15 GMT
Sender: root@crash.cts.com
Lines: 29

I just got a copy of ScreenX v3.0 and it's misbehaving in ugly ways.  First
question.. is it real or did I get hoodwinked by a bogus new version?
Assuming it's real I don't feel inclined to attribute the bad behavior to
ScreenX bugs due to my faith in Steve Tibbet's programming abilities.  The
program works fine if I run it from wb using the icon, but all attempts to
run it from a shell results in task held requesters or lockup gurus.  I
need to run it from a shell to use the command line switches.
 
>From my shell..
 
ScreenX
Run >NIL: <NIL: ScreenX
Run ScreenX
Runback ScreenX
 
All of these crash the machine in different ways.  Sometimes it freezes up
the pointer and gives me a guru, puts up a task held requester or doesn't
guru until I use the quit gadget on the screenx window.  ScreenX v2.0 does
not conflict with anything I have in the back. My setup is A2000 3mb,
running are newlook, blitzfonts, uclock, pointer animator, dmouse and
dlineart.  Using the leftamiga-DEL option to save the front screen also
brings me to the guru (when run from the icon or otherwise).  Anyone know
the rest of this story?
 
Please reply in email, I can't keep up with the traffic here.
--
      UUCP: crash!pro-graphics!critical.mass    | Critical Mass Software
  ARPA/DDN: pro-graphics!critical.mass@nosc.mil | P.O. Box 23
  Internet: critical.mass@pro-graphics.cts.com  | Short Hills, NJ 07078