One test for the original poster. If you are using a full null cable, just enable RTS/CTS on your settings and give it a try. This would eliminate the question.
I say this because my T200 gave me a few issues when I was developing mComm. The thing that was strange was I had to have RTS/CTS enabled on the PC side so I could talk to TELCOM. I realize that goes against conventional wisdom, and that may be the case for 'my' T200 but I thought I would throw that out there. The compulink cables that Rick used to build were loop backs so connecting one of these would have the affect of enabling RTS/CTS and DTR/DSR. But at the same time killing the functionality. http://www.club100.org/library/doc/cables.html Notice he only used 3 wires and two loop backs. Kurt On Thu, Jul 18, 2019, at 12:36 PM, John R. Hogerhuis wrote: > " know TELCOM in the M100 ignores RTS/CTS, and I thought that was also true > of the T200" > > TELCOM ignores RTS/CTS. > > Many Model T programs require DSR signal or they won't send anything. I'm not > sure about TELCOM. > > The other issue is the duplex. Half duplex, you see what you type. Full > duplex, you only see what the other side echoes back. And if there's no > "other side" no one can echo back so for sure at full duplex, you can expect > to see nothing from typing. > > -- John.
