Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!rpi!uupsi!sunic!fuug!demos!news-server
From: ZAITCEV@TWIN.srcc.msu.su
Newsgroups: comp.lang.modula2
Subject: Re: JPI v. 2.0 interrupt co-routine questions
Message-ID: <81E11AA203zaitcev>
Date: 12 Mar 91 03:06:51 GMT
Sender: news-server@jumbo.hq.demos.su
Reply-To: ZAITCEV@TWIN.srcc.msu.su
Organization: unknown
Lines: 20


 I'm  sorry  for publishing news instead of using regular mail. I'm not
 the  complete  stupid.  Simple  I'm  not  sure  that domain "uucp" for
 "loft386!mhuges" is availiable from the RELCOM. (where I resides)
 
 In <1991Mar4.234410.21080@loft386.uucp> "loft386!mhuges" writes:
 >1. The manual says that the module [priority] on PC systems is a bit
 >mask and then falls forever silent.  I assume this mask refers to the
 >IRQs with bit 0 corresponding to IRQ0, but is this correct and is it
 >bit-on or bit-off to disable a given interrupt?
 >2. What, exactly, is the "interrupt vector" required by IOTRANSFER?
 >An IRQ number, an index into the jump table (0CH for Com1, etc.) or
 >something entirely different?
 I worked  with the  JPI v1.15  much and  I hope  that  v2.00  will  be
 compatible with  v1.15. If so, SYSTEM.NewPriority really uses mask for
 PC interrupt  controller(s). Low/Rigth  byte is  mask for &21 port and
 other is  for &A1  port. Also, IOTRANSFER requres INT vector NUMBER or
 "index  into  the  jump  table"  in  original speach. Sure, this works
 in real mode only.
                                                            Pete