Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!beach!mrimages
From: mrimages@beach.gal.utexas.edu
Newsgroups: comp.sys.amiga.hardware
Subject: Kill and Getting Killed, heh.
Message-ID: <378.2830d367@beach.gal.utexas.edu>
Date: 15 May 91 12:21:27 GMT
Lines: 19

From: R.Luebbert, University of Texas Medical Branch at Galveston


1) Never heard a reply to the earlier question about a kill command for
AmigaDOS.  Is this ever going to be developed?  It sure would save my ctrl-A-A
keys from wear and tear after dead programs start piling up.

2) Is there a way to safely (or reasonably safely) change the contents of
screens/windows opened by other processes?  Using public screens would be
lovely, unfortunately the screens I want to write to are created by programs
that do not use public screens, like my term program.  I have been able to
locate and write data to the screens, but after I do so, I cannot open new
screens, change the resolution of screens already open (like CED), or run my
compiler. I usually get the guru 8100000C after moving on to other tasks,
always at the same address. I am always careful about using LockIBase before
poking around in intuitionbase, but it doesn't seem to help.  I am using
AmigaDOS 2.0.

Any questions or comments would be greatly appreciated.