Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site wnuxb.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxt!houxm!ihnp4!mgnetp!hw3b!wnuxb!laj
From: laj@wnuxb.UUCP (JOHNSON)
Newsgroups: net.micro
Subject: Crosstalk woes
Message-ID: <631@wnuxb.UUCP>
Date: Tue, 3-Sep-85 10:32:05 EDT
Article-I.D.: wnuxb.631
Posted: Tue Sep  3 10:32:05 1985
Date-Received: Wed, 4-Sep-85 07:02:04 EDT
Reply-To: laj@wnuxb.UUCP (JOHNSON)
Organization: AT&T - Warrenville Data Center, IL
Lines: 27

In the few articles posted describing various problems with Crosstalk XVI
I expected to see described the problem which plagues me in using the
product.  Since no one mentioned it, I am led to believe that there is
an easy fix which I`m overlooking.

I am running Crosstalk XVI 3.41 under MSDOS 2.1 on an IBM PC.  I have found
that when I'm connected to a UNIX host and issue a "break", I do not 
receive the expected UNIX prompt string.  I hassled with Micro Stuff until
I got determination of the problem and a patch.  For reasons which are
not clear to me, Crosstalk disables interrupts from the UART by resetting
the interrupt enable register for the duration of the break.  Perhaps, this
is to allow them to time the break signal more accurately.  In any event,
interrupts are still disabled when the host, recognizing the break, sends
the prompt string back.  All characters except the last are lost.  The
patch for 3.41 nullified the manipulation of the interrupt enable register
and Crosstalk worked just fine.

I assumed that this was a bug which Micro Stuff would address in the next
release.  However, I just got release 3.5 and the bug persists.  I hate to
keep requesting a patch for this product.  Has anyone else seen this
symptom and found a convenient work-around ?

-- 
						Larry Johnson
						Western ElectricAT&T TechnologiesInformation Systems
						ihnp4!wnuxa!laj
						ihnp4!wnuxb!laj