First post, by pengo
Hi I'm new here but often found the information around here amazingly well researched.
There are a lot of Morse code related DOS programs that ignore what serial ports are usually used for and just use a couple of serial port pins to receive or send Morse code signals, e.g. just shorting and breaking a connection to produce Morse code. These pins have names like Clear-to-Send (CTS) and Data Set Ready (DSR) and are meant for flow control, but they're used by amateur radio software for sending morse code signals or to wire up a morse code key or paddles to a PC without ever setting a baud rate or agreeing on parity bits. [They're still used this way in modern Windows software too] Here's one random example of such a program that sends Morse on a serial port without touching the data pins: mpp-110a https://archive.org/details/mpp-110a
I made a simple sidetone generator (https://github.com/pengowray/upsidetone/) that DOS programs can connect to via a pair of virtual com0com serial ports on windows, but while it works for me, I'm not happy with the mess of extra virtual serial ports that my imaginary users would have to install and configure to get going. [In the distant future I'd like to find a way to create a virtual interface for dosbox serial ports for when it's embedded on a web page]
Trying to work out if I could connect more directly using the ENET UDP protocol that dosbox supports. I _can_ find docs and libraries for ENet, but not anything on how Dosbox uses it. Please save me from having to reverse engineer the dosbox code or snoop the connections myself. Does/can dosbox send events when non-data pins are toggled (CTS DSR DTR RTS) or is it only for higher level data transmission? Thanks