Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!timbuk!shamash!case
From: case@shamash.cdc.com (Steven V. Case)
Newsgroups: comp.lang.ada
Subject: Re: Meridian Ada and IBM PC serial ports
Message-ID: <30011@shamash.cdc.com>
Date: 23 Jan 91 03:12:08 GMT
References:  <2583@sparko.gwu.edu>
Distribution: comp
Organization: Control Data, Arden Hills, MN
Lines: 31

In article <2583@sparko.gwu.edu>, mfeldman@seas.gwu.edu (Michael Feldman) writes:
> In article  mskuhn@faui09.informatik.uni-erlangen.de (Markus Kuhn) writes:
> >I am developing an (public domain) application with Meridian
> >Open Ada 4.1 (was AdaZ) with lots of pre-emptive tasking
> >and access to the serial ports (an OSI system!).
> >
> >Can this problem also be solved with Meridian's interrupt
> >entry mechanism? Somebody wrote here a few weeks ago that this
> >would be to slow.
> >
> I assume you have access to the AdaZ documentation. Their DOS Environment
> Library has a package called Interrupt. Gives you direct access to the
> DOS interrupts without using the "right" Ada way to do it, which is the
> interrupt entry. Looks similar to what you're used to in TP.

Sorry, but the DOS Environment Library does not help here.  The Interrupt
package provides 'calls' to the interrupt vectors.  The original post was
looking for information on how to implement their own handler to respond
to calls to the interrupt vectors.

As it turns out, the 4.0 version of Meridian Ada does not appear to support
user implemented interrupt handlers for the RS-232 interrupts.  I don't know
if the 4.1 version will provide the capability.  I am (im)patiently waiting
for my upgrade.  As soon as it arrives I will port my 4.0 code over and 
see what happens.

-- 
  ____  ____        Steve Case - HQG526           email: case@shamash.cdc.com
 / ___||___ \       Control Data Corporation      AT&T : (612) 853-3345
| |___  ___| |      3101 East 80th Street                 
 \____||____/       Bloomington, MN 55425