Date: Thu, 12 Feb 1998 16:54:42 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To: Nigel Megitt <nigelm AT rd DOT bbc DOT co DOT uk>
cc: djgpp AT delorie DOT com
Subject: Re: Serial ports?
In-Reply-To: <6bupsu$9eo@bbcnews.rd.bbc.co.uk>
Message-ID: <Pine.SUN.3.91.980212165035.20700A-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Precedence: bulk


On 12 Feb 1998, Nigel Megitt wrote:

> Yes, but how do I make them do this? Do I have to write my own interrupt
> drivers and hook them in? I really don't want to, if I can avoid it.

It depends on the baudrate you need to use.  AFAIK, using DOS or BIOS 
will never get you past 9600 baud.  Beyond that, you will *have* to use 
interrupts.

> I had a look at DZCOMM, but, what with needing Allegro too, it seems to be a
> sledgehammer for this nut.

Did you look at BCSERIO?

> Unfortunately my program needs to access both COM1 and COM2 at the same 
> time - is this possible using stdaux?

No.

> Also, the question comes up again - if using stdaux, how can I
> set the port up?

Use BIOS functions, either _bios_serialcom (Microsoft style) or bioscom 
(Borland style).

> The _bios_serialcom function gives me all the things I need to
> set a port up the way I need. If I just use that, will stdaux behave 
> correctly?

AFAIK, yes.