Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!think!mintaka!mit-eddie!uw-beaver!ubc-cs!alberta!dvinci!weyr!p0.f104.n203.z2.FIDONET.ORG!Mikael.Wahlgren
From: Mikael.Wahlgren@p0.f104.n203.z2.FIDONET.ORG (Mikael Wahlgren)
Newsgroups: comp.os.os2
Subject: Re: Os/2 Comm. Manager
Message-ID: <509.25CCC2A0@weyr.FIDONET.ORG>
Date: 31 Jan 90 20:02:00 GMT
Sender: ufgate@weyr.FIDONET.ORG (newsout1.26)
Organization: FidoNet node 2:203/104.0 - TriGem BBS, Gothenburg
Lines: 23

In a message to Loren Jones <01-22-90 19:52> Ron Merts wrote:

<RM>in the blank).  If I read the docs right, you cannot use
<RM>the COM0x.SYS
<RM>drivers in conjunction with the ASYNCxxx.SYS drivers the
<RM>Comm Manager
<RM>uses.  I am not an expert on OS/2 by any stretch of the
<RM>imagination; but
<RM>it seems to me that this will disable the use of ANY other
<RM>communications

   Well, I think it is still possible to run the COM0x-driver on another
COM-port.  There ARE some people around having one COM-port to connect to
the local mini, and another COM-port for the modem.  It is possible to use
CM for the mini communications, and a public communication program for the
modem...  But still....  CM is worthless.
         / Mikael  
 
--  
Mikael Wahlgren - via FidoNet node 1:140/22
UUCP: alberta!dvinci!weyr!2!203!104.0!Mikael.Wahlgren
Internet: Mikael.Wahlgren@p0.f104.n203.z2.FIDONET.ORG
Standard Disclaimers Apply...