Path: utzoo!attcan!uunet!snorkelwacker!usc!zaphod.mps.ohio-state.edu!uwm.edu!bionet!ames!excelan!saddison
From: saddison@excelan.COM (Skip Addison)
Newsgroups: comp.dcom.lans
Subject: Re: int 14
Summary: He's right.
Message-ID: <1563@excelan.COM>
Date: 18 Jul 90 03:27:12 GMT
References: <12920042@acf4.NYU.EDU>
Sender: news@excelan.COM
Reply-To: saddison@Novell.com (Skip Addison)
Organization: Novell, Sunnyvale, CA.
Lines: 19

In article <12920042@acf4.NYU.EDU> chapman@acf4.NYU.EDU (Gary W Chapman) writes:
>Can someone explain the idea of INT 14 redirectors to me?  My impression
>is that some asynch comm programs can be told to do i/o via int 14, and
>that some telnet clients can be configured to use int 14 as their 
>interface to the comm program (which thereby functions as a user
>interface/front end to telnet).  Is this off-base?
>
>-Gary Chapman, chapman@nyu.edu

Your understanding is correct.  The INT 14 interface is based on the original
IBM ROM BIOS serial port support (which was largely ignored).  There are now
many different implementations of INT 14 (including 2 different ones from IBM,
naturally) to provide access to various modem pools, async gateways, etc.

There is now a great deal of support for the NASI interface which was designed
from the start to be used over a network.  It's a similar concept, but more
advanced and standardized....

-- Skip