Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!abvax!iccgcc!klimas
From: klimas@iccgcc.decnet.ab.com
Newsgroups: comp.os.os2.misc
Subject: Re: Communications Manager Woes (ASCII terminal emulation)
Message-ID: <4290.280af7b4@iccgcc.decnet.ab.com>
Date: 16 Apr 91 18:10:12 GMT
References: <91093.212206ANDY@MAINE.BITNET>
Lines: 15

In article <91093.212206ANDY@MAINE.BITNET>, ANDY@MAINE.BITNET (Andrew T. Robinson) writes:
> Every time I invoke CM, which is configured to auto-start ASCII/ACDI
> with the VT100 configuration file, I get a "critical error" and the
> session does not start--that is literally all the information provided
> by the error message (don't remember the number off the top of my
> head.)
> 
> When CM starts up I can see that it blips the TD light on my IBM 2400
> BPS modem (model 5853) but it goes no further.  I have an IBM modem
> cable so it should be pinned out properly.  Anyone else experienced
> this (this is why I didn't use CM months ago and instead opt to use
> YTERM from the DOS box)?

	There are a lot of bugs in the OS/2 r1.2 Comm. Mgr. that are fixed 
	by the Corrective Service Diskettes available from IBM.