Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!zephyr.ens.tek.com!tektronix!percy!m2xenix!puddle!p101.f4.n494.z5.fidonet.org!Pat.Terry
From: Pat.Terry@p101.f4.n494.z5.fidonet.org (Pat Terry)
Newsgroups: comp.lang.modula2
Subject: JPI v. 2.0 interrupt co-routine questions
Message-ID: <2292.27DCA785@puddle.fidonet.org>
Date: 12 Mar 91 06:36:11 GMT
Sender: ufgate@puddle.fidonet.org (newsout1.26)
Organization: FidoNet node 5:494/4.101 - Settler City Fido, Grahamstown RSA
Lines: 43

mhughes@loft386.uucp (Mike Hughes) asks

 >Has anybody written a working interrupt-driven routine in JPI v 2.0?

JPI have (look at PROCESS.MOD).  I have written some in ver 1.1x, but not tried 
them in version 2 yet.

 >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

Yes.  Note that the release 2 manuals are appallingly bad (at least mine are.  
They may hvae redone them by now).

 >and is it bit-on or bit-off to disable a given interrupt?

Bit-on disables.  eg MODULE AllDisabled [0FFH];

 >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?

The interrupt "number" for the PC.  eg 08H for raw time, 1CH for chained timer, 
09H for keyboard ...  I suppose you call that the index into the jump table.

 >3. What do the following link error messages mean?
 > 
 >SYSTEM$TRANSFER unresolved...
 >_new_priority unresolved...

maybe another version 2 bug?  Don't know.  You may have to install for the 
"multithread" model to be able to use IOTRANSFER with version 2.

I have some notes and examples, prepared for my students, of IOTRANSFER use on 
PC's - would you like a copy?
 




--  
uucp: uunet!m2xenix!puddle!5!494!4.101!Pat.Terry
Internet: Pat.Terry@p101.f4.n494.z5.fidonet.org