Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!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: v11i233, v11i233: conex60, communications program Summary: Won't work on COM4 Message-ID: <1991Apr25.030426.11398@cbfsb.att.com> Date: 25 Apr 91 03:04:26 GMT Sender: news@cbfsb.att.com Organization: AT&T Bell Laboratories Lines: 33 I tried CONEX60 on my XTurbo10 because I liked the idea of having a graphics terminal emulator. For various reasons I have a mouse on COM1 and a printer on COM2, so my 1200-baud modem is configured as COM4. This works well with Boyan 4.0 as well as another terminal emulator used at Bell Labs. The first time I tried to configure CONEX for COM4, it told me COM4 wasn't installed. I fixed that by entering the port address of COM4 in the port table in the kernel, where DOS looks for port definitions. After that, CONEX accepted the configuration, and dialed out when I typed in the modem command to dial, and the modem established the connection. Then there was a more serious problem: 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. After the connection was made, I got only odd single isolated characters. If I stayed in command mode, without dialing, and just gave the modem commands, the echo delay increased to two characters, and then more. I suspect that CONEX is not responding to interrupts and therefore not reading received characters except when it sends one. But I don't really understand how that works. Has anybody had any better luck with CONEX on any port, but in particular on COM4? And does anybody have any idea why I'm having trouble or any suggestions on how to fix it? -- Martin B. Brilliant hoqax!marty (Winnertech Corporation) HO 2J-528 (908)949-1215