Xref: utzoo comp.windows.ms.programmer:1832 comp.os.os2.programmer:622
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!emory!gatech!bloom-beacon!eru!hagbard!sunic!chalmers.se!mathrt0.math.chalmers.se!d9mikael
From: d9mikael@dtek.chalmers.se (Mikael Wahlgren)
Newsgroups: comp.windows.ms.programmer,comp.os.os2.programmer
Subject: Re: Communication Packages needed with Windows? OS2?
Message-ID: <1991Apr14.055404.8916@mathrt0.math.chalmers.se>
Date: 14 Apr 91 05:54:04 GMT
References: <1991Apr10.161018.18635@wem2.hf.intel.com> <1991Apr12.123630.19704@watson.ibm.com>
Sender: news@mathrt0.math.chalmers.se (Evald Nyhetsson)
Organization: Chalmers University of Technology, Gothenburg, Sweden
Lines: 20

In article <1991Apr12.123630.19704@watson.ibm.com> larrys@yktvmv writes:
>In <1991Apr10.161018.18635@wem2.hf.intel.com>, wayne@wem2.hf.intel.com (Wayne McDaniel) writes:

>>for sell to write DOS communication programs.  What about Windows and
>>OS2?  Does one use the same communication packages that are
>>available for DOS or does Windows and OS2 have built in communication
>>support?
>
>OS/2 has the "extended edition" which contains the communication support.

You don't need Extended Edition if the only thing you want to do is
interrupt-driven asynchronous communication.  There is a COM-driver
in OS/2 that you work when you write an asynchronous program.  THe driver
itself is interrupt-driven, so the application program don't need to
worry about these things.

There are plenty of asynchronous communication programs available for
OS/2, both PM and text.

Mikael Wahlgren      d9mikael@dtek.chalmers.se