Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site sftig.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!sftig!rbt
From: rbt@sftig.UUCP (R.Thomas)
Newsgroups: net.micro.apple
Subject: Re: IIe Termcap; Bug in the 80 Col Monitor.
Message-ID: <493@sftig.UUCP>
Date: Mon, 28-Jan-85 14:48:29 EST
Article-I.D.: sftig.493
Posted: Mon Jan 28 14:48:29 1985
Date-Received: Wed, 30-Jan-85 04:21:06 EST
References: <287@boulder.UUCP> <828@pucc-i>
Distribution: net
Organization: AT&T Bell Laboratories, Summit, NJ
Lines: 23

> It's more like a documented non-feature.  The Apple monitor does not
> actively support interrupts, which are the only solution to the problem.
> On the other hand, the hooks are available so that user programs can do
> their own interrupt processing.  One of the reasons most terminal programs
> do not do this is that most communications cards do not adhere to the
> Apple standards for interrupt handling, which were established rather
> late in the game.  See the Apple //e Reference Manual.
> -- 
> Dave Seaman			 ..!pur-ee!pucc-i:ags

In fact, the Apple Super Serial Card even does not support the protocol for
interrupt priority as written down in the //e reference manual.  However, if
you have only one interrupting card, and that is your Super Serial Card, (The
most likely competition would be a clock card, and if you have a clock card
you dont need to have the SSC interrupt, because you can ask the clock card
to interrupt once every 4 ms or so, and poll the SSC in the clock service
routine.) then the protocol is followed by default.

For what it's worth.  The above inforamtion can all be gleaned by a careful
reading of the SSC reference manual and the //e reference manual.  It's all
there, you just have to know where to look.

Rick Thomas		ihnp4!btlunix!rbt