Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!purdue!haven!umd5!cgs
From: cgs@umd5.umd.edu (Chris G. Sylvain)
Newsgroups: comp.sys.ibm.pc
Subject: Blocking BIOS (Re: OS/2 versus UNIX (was Re: Buying a 386 clone))
Message-ID: <4652@umd5.umd.edu>
Date: 2 Apr 89 22:02:58 GMT
References: <3177@imagen.UUCP> <1309@bucket.UUCP> <7956@chinet.chi.il.us> <13420@steinmetz.ge.com> <8029@chinet.chi.il.us> <13449@steinmetz.ge.com> <29177@bu-cs.BU.EDU>
Reply-To: cgs@umd5.umd.edu (Chris G. Sylvain)
Organization: University of Maryland, College Park
Lines: 24

In article <29177@bu-cs.BU.EDU> madd@buit4.bu.edu (Jim Frost) writes:
>
>OS/2 cannot make use of a blocking BIOS, which is the normal one in
>PC's.  There are two simple approaches to getting around this: the
>first is to put in a non-blocking BIOS (in addition to the normal one)
> [.lots deleted.]

Interesting, well written article..
But, whoa! Just minute.. "blocking BIOS is the normal one in PC's", huh?

Please, name your source.

My source, _The IBM PC From the Inside Out/Includes the PC AT_ by Sargent
and Shoemaker, Addison-Wesley, ISBN 0-201-06918-0 (so it's a good book, and
you might what it for your library), clearly states that in the PC interrupt
handlers (almost) invariably reenable interrupts upon entry.

Doesn't sound like a "blocking BIOS" to me.. Would you explain "blocking BIOS"
further, please?
-- 
--==---==---==--
.. Beware the Jubjub bird, ..
   ARPA: cgs@umd5.UMD.EDU     BITNET: cgs%umd5@umd2
   UUCP: ..!uunet!umd5.umd.edu!cgs