Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!cs.utexas.edu!usc!snorkelwacker!ira.uka.de!smurf!nadia!dialog!root
From: root@dialog.stgt.sub.org (Christian Motz)
Newsgroups: comp.os.os2.misc
Subject: Re: A modem on com2:
Message-ID: <2467@dialog.stgt.sub.org>
Date: 26 Aug 90 10:38:31 GMT
References: <15590007@hpmcaa.mcm.hp.com> <1990Aug17.084138.5548@mathrt0.math.chalmers.se> <4048@tuminfo1.lan.informatik.tu-muenchen.dbp.de> <1990Aug24.135527.6356@mathrt0.math.chalmers.se>
Sender: uucp@dialog.stgt.sub.org
Reply-To: root@dialog.stgt.sub.org (Christian Motz)
Organization: Dialog Software Development
Lines: 20

In article <1990Aug24.135527.6356@mathrt0.math.chalmers.se> d9mikael@hackes.dtek.chalmers.se (Mikael Wahlgren) writes:
>In article <4048@tuminfo1.lan.informatik.tu-muenchen.dbp.de> rommel@lan.informatik.tu-muenchen.dbp.de (Kai-Uwe Rommel) writes:
>
>>Is the 16550 UART supported by OS/2 1.2? I.e.is the FIFO buffer used by
>>the COM0x.SYS drivers? The IBM PS/2 machines have 16550's as the
>>standard UART (as far as I know). Windows 3.0 for example, does not
>>support the 16550 FIFO with its comm.drv driver.
>
>Yes, the 16550 UART with FIFO is fully supported by OS/2 1.2.  But note that
>early versions of OS/2 1.2 COM01.SYS-drivers was buggy, and didn't work with
>hardware handshaking.  Now, it seems to work perfectly (CSD 4053) at least
>it does for me, with both COM02.SYS and COM01.SYS drivers.

Only one thing to add from my side: You can see  whether  or  not  the
16550 has been detected and the FIFO enabled  when  the  COM0x- driver
brings up the message "COM0x supports extended hardware buffering." or
something to that effect.

--
Christian Motz                                root@dialog.stgt.sub.org