Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!cbfsb!cbnewsb.cb.att.com!mbb
From: mbb@cbnewsb.cb.att.com (martin.brilliant)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: v11i233, v11i233: conex60, communications program
Message-ID: <1991Apr29.145208.17566@cbfsb.att.com>
Date: 29 Apr 91 14:52:08 GMT
References: <1991Apr25.030426.11398@cbfsb.att.com>
Sender: news@cbfsb.att.com
Organization: AT&T Bell Laboratories
Lines: 24

In article <1991Apr25.030426.11398@cbfsb.att.com> I wrote:
>I tried CONEX60 on my XTurbo10 ....  > I couldn't receive anything.
>I noticed also that when the modem echoed the dialing command, each
>character appeared on the screen only after I typed the following
>character....
>
>I suspect that CONEX is not responding to interrupts and therefore
>not reading received characters except when it sends one....

I sent an email inquiry to the author (using the address in the doc
file in the conex60 distribution) and received the following reply:

: I expected that COM3 and COM4 might not work since I never had
: any opportunity to test it. Originally I took interrupt 11 for
: COM3 and 10 for COM4, the IO address is read from BIOS
: communication area.
:    I send you CONEX with interrupt 4 for COM3 and interrupt 3
: for COM4, which you only need to decode. In future releases
: this parameter will be configurable. Please tell me if you could
: make it run.

These are presumable IRQ4 and IRQ3, which seem to be conventional in
most systems.  The new version works, but only after I powered off the
computer (and modem) to reset everything.