Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!gatech!gitpyr!robert
From: robert@gitpyr.UUCP
Newsgroups: comp.os.minix
Subject: Re: Which clones *don't* run MINIX
Message-ID: <3070@gitpyr.gatech.EDU>
Date: Mon, 9-Feb-87 21:30:08 EST
Article-I.D.: gitpyr.3070
Posted: Mon Feb  9 21:30:08 1987
Date-Received: Tue, 10-Feb-87 18:39:16 EST
References: <275@ihnp3.UUCP> <459@moncol.UUCP> <2529@well.UUCP> <172@axis.UUCP> <1192@husc6.UUCP>
Reply-To: robert@gitpyr.UUCP (Robert Viduya)
Organization: Office of Computing Services, Georgia Tech
Lines: 20
Keywords: MINIX BIOS COMPATIBILITY

>ddl@husc6.UUCP (Dan Lanciani) (ddl@husc6.UUCP, <1192@husc6.UUCP>):
> In article <172@axis.UUCP>, philip@axis.UUCP writes:
> > But, the most important reason (as given in the book) is that the BIOS
> > calls do not use interrupts.
> 	This is plain wrong.  The IBM PC keyboard is interrupt-driven.
> Int 9 is used, if you are interested.

It's not plain wrong.  It's halfway wrong.  The keyboard, yes, is
interrupt driven, along with the disk drivers.  However, the async ports
are not.  Ever try to write a communication program that uses the bios
calls to do async port i/o?  You can't get better than 1200 baud without
dropping characters.  To handle high baud rates you have to write your
own interrupt handler.

			robert
-- 
Robert Viduya					     robert@pyr.ocs.gatech.edu
Office of Computing Services					(404) 894-4660
Georgia Institute of Technology
Atlanta, Georgia	30332