Path: utzoo!attcan!uunet!husc6!rutgers!mailrus!cornell!batcomputer!payne
From: payne@batcomputer.tn.cornell.edu (Andrew Payne)
Newsgroups: comp.sys.ibm.pc
Subject: Re: interrupt driven serial i/o
Keywords: interrupt serial COM
Message-ID: <6846@batcomputer.tn.cornell.edu>
Date: 16 Nov 88 22:21:09 GMT
References: <5728@polyslo.CalPoly.EDU>
Reply-To: payne@tcgould.tn.cornell.edu (Andrew Payne)
Organization: Cornell Theory Center, Cornell University, Ithaca NY
Lines: 27

In article <5728@polyslo.CalPoly.EDU> sjankows@polyslo.CalPoly.EDU (Mr Booga (Krueger)) writes:
>I am writing a simple BBS in Turbo C 2.0 and I would like to use interrupt
>driven I/O.  I know it's possible, but I don't have the resources necessary
>to find the information I need.  The ultimate goal is to have a system
>where a caller and the sysop can use the BBS at the same time.

	One thing you might want to look into is a serial port driver called
FOSSIL (I forgot what the acronym stands for).  Its a serial driver that 
installs under MS-DOS as a device driver (e.g. in your CONFIG.SYS).  You
access it through one of the user INTs, and its a simple matter to write
some Turbo C functions to access the FOSSIL functions.

	One plus about the FOSSIL is that if you write your BBS in modules,
you have a minimal amount of serial support code in each module.  Also, you
don't have to worry about installing and de-installing interrupt vectors.
Finally, since the FOSSIL is always resident, you don't have to worry about
dropping characters between modules.

	Where can you get a FOSSIL driver?  Well, the FOSSIL "standard"
came from the Fido/Opus world, so you should be able to find a driver on
any FIDO/OPUS BBS worth its salt.  If you can't find a copy, drop me mail.

-- 
=  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =  =
Andrew C. Payne               UUCP:  ...!cornell!batcomputer!payne
                          INTERNET:  payne@tcgould.tn.cornell.edu
PHONE: +1 607 253 2776      USMAIL:  5428 Cls '26-UHall 5   Ithaca, NY  14853