Real VT102 emulation with MAME (2020)
zork.net
zork.net
Also make sure your modem settings in MAME match the settings configured on the VT102. I have them both set to 19200 baud 8N1. I've just done a quick test now, and I can definitely make it through tests 1 and 2 in vttest without the output getting corrupted.
I should also mention that I've got the RS232 device set to null_modem (which is hooked up to a socat instance via MAME's bitbanger feature), rather than the pty configuration that they're using. I'm not sure if that could make a difference to the way the flow control works.
> A copy of the VT102 firmware ROM
I've known for a long time that "terminal emulators" are software emulators of hardware terminals, but until now it never occurred to me that those hardware terminals might have still been largely software constructs.
It's emulation all the way down.
We squeezed computing out of the mainframe and into the terminal.
On the WSL Linux side: socat -d -d exec:'bash -li',pty,stderr,setsid,sigint,sane TCP-LISTEN:11313,reuseaddr,fork
On the Windows side: .\mame.exe vt240 -window -host null_modem -bitb socket.10.0.0.2:11313
I’ve thought before that you could have a couple of USB-to-RS232 adapters and connect them together?
What Linux needs is a real virtual serial driver. PTY isn’t it because it doesn’t fully emulate lower level aspects of RS-232 - it behaves differently from “connecting two RS-232 ports together”