Communications Manager Woes (ASCII terminal emulation)

Article View: comp.os.os2

Article #820

#820

From: Andrew T. Robinson
Date: Thu, 04 Apr 1991 02:22

11 lines
977 bytes

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)?

Technical Details

Message-ID: <91093.212206ANDY@MAINE.BITNET>

Path:

arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!uw-beaver!mit-eddie!bbn.com!nic!mars!maine!andy

Show Full Headers

Complete Article Headers

Path: arc1-ca.pugleaf.net!utzoo!utgpu!news-server.csri.toronto.edu!rpi!batcomputer!cornell!uw-beaver!mit-eddie!bbn.com!nic!mars!maine!andy
From: ANDY@MAINE.BITNET (Andrew T. Robinson)
Newsgroups: comp.os.os2
Subject: Communications Manager Woes (ASCII terminal emulation)
Message-ID: <91093.212206ANDY@MAINE.BITNET>
Date: 4 Apr 91 02:22:06 GMT
Organization: University of Maine System
Lines: 11