Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!news.cs.indiana.edu!arizona.edu!arizona!dave From: dave@cs.arizona.edu (Dave P. Schaumann) Newsgroups: comp.sys.amiga.datacomm Subject: Re: Features I'd like to see in JRCOMM Message-ID: <846@caslon.cs.arizona.edu> Date: 12 Feb 91 04:35:56 GMT References: <1991Feb3.075026.1923@ckctpa.UUCP> <910203.083436@lerami.lonestar.org> < <1991Feb03.221430.19135@hoss.unl.edu>> < <18a3147a.ARN02ec@zikzak.in-berlin.de>> <971@faatcrl.UUCP> Organization: U of Arizona CS Dept, Tucson Lines: 17 In article <971@faatcrl.UUCP> jprad@faatcrl.UUCP (Jack Radigan) writes: >vic@wookumz.ai.mit.edu (Vic Rattlehead) writes: >[...] >>3) How about making it live happily with other programs. LaceWB gurus, >>Mach II's clock when popped to the jrcomm screen gurus. > > LaceWB? haven't tried it. Mach II? Too much of a memory hog and it >blanks all sprites, not just the pointer sprite like Qmouse does, which >isn't a cpu hog either. I have been told that LaceWB exits in a "hanging forbid" mode, which apparently can (& does!) cause the system to guru at a later date. No fault of JR-Comm. -- Dave Schaumann | DANGER: Access holes may tear easily. Use of the access | holes for lifting or carrying may result in damage to the dave@cs.arizona.edu | carton and subsequent injury to the user.