Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!cs.utexas.edu!uunet!mcvax!ukc!axion!galadriel!robing
From: robing@galadriel.UUCP (Robin Gape)
Newsgroups: comp.sys.atari.st
Subject: Re: Code conflicts
Message-ID: <273@galadriel.UUCP>
Date: 1 Jun 89 07:43:29 GMT
References: <8905301722.AA09574@ucbvax.Berkeley.EDU>
Organization: RT6115, BTRL, Martlesham Heath, England
Lines: 27

From article <8905301722.AA09574@ucbvax.Berkeley.EDU>, by 01659@AECLCR.BITNET (Greg Csullog):
> If I have a screen save utility (called NITE.PRG) installed, dbMAN halts
> execution when the screen blanks and restarts when I touch the mouse or a
> key to refresh the screen. Why would a screen blank interrupt cause dbMAN
> to halt?
> 
> When I have NEOCNTRL.ACC installed, UNITERM goes into some weird mode when
> I press INSERT to call up the keyboard buffer. The only way out is to reboot
> my ST. Anyone have ideas on this one?

Second question. Yes, UNITERM has the exceptionally antisocial habit of
burrowing into the keyboard vectors and re-configuring the mouse
handler. This is done to allow it to detect simultaneous clicks of the
mouse, or some such. Unfortuneately, when UNITERM terminates it does NOT
release the vectors bnack to normal operation. This is fine for floppy
based systems, and people running under TOS-in-RAM who expect lots of
bombs, but a real pain-in-the-anatomy if you're using a hard disk,
especially with GDOS.

The UNITERM documentation does mention this habit, but it makes no
reference to the consequences. Remember, the prog. was written a while
ago, when applications tended to be less sophisticated.

Hope this helps

Robin Gape
(robing@uk.co.bt.galadriel)