Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!sri-unix!hplabs!hp-sdd!ncr-sd!bigbang!crash!cacilj!paul
From: paul@cacilj.UUCP
Newsgroups: comp.sys.apple
Subject: Interrupts on the //c
Message-ID: <220@cacilj.UUCP>
Date: Thu, 22-Jan-87 20:22:58 EST
Article-I.D.: cacilj.220
Posted: Thu Jan 22 20:22:58 1987
Date-Received: Sat, 24-Jan-87 20:03:13 EST
Reply-To: paul@cacilj.UUCP (Paul Close)
Distribution: world
Organization: CACI, Inc. - Federal, La Jolla, CA
Lines: 20
Keywords: Is it me or what?

Recently I've been involved in modifying a local Kermit so that the super
serial card driver will work on the //c.  This driver is interrupt-driven.
No problem.  The only problem is that even with an interrupt-driven driver,
the poor //c can't go much faster than 1200 baud!!!  (i.e. forget 2400).  I
also tried the built-in terminal (IN#2 + ^AT) firmware, and it exhibited the
same (rotten) behaviour.  Has anyone else had these problems?  I've heard that
a //e running the same driver can hit 9600 baud!!!

I know the //c interrupt firmware has a lot to do, but this is ridiculous!
I've thought about replacing the interrupt routine with my own, streamlined
routine, but haven't got around to it yet.  Anyone else tried that? (replacing
the $FFFE driver, that is)

	Thanks,

	Paul
-- 
	Paul Close
	paul@cacilj.UUCP
	(...!{crash, gould9}!cacilj!paul)