Some serial links were 7-bit, and wouldn’t even pass all 7-bit characters; for instance, sending a Ctrl-S could lock up a remote until you sent Ctrl-Q.
Ironically, the times I actually needed (or would be greatly helped) by kermit, I never had it on the remote. If you’re exceedingly crafty, you can usually do a lot of good (or evil) with Tcl expect module. I’d write shell snippets to set echo off, raw mode, and spawning base64 -d > rx and other such things and it generally worked ok. Sometimes you can manage to really write fast to the serial port and overrun the buffer on the receiving end so I usually set the baud rate in the lower end. It probably explains why some of these serial port tools had some form of CRC or error correction.
Nothing to do with 7-bit characters, and the “lock up” was a deliberate feature. See https://en.wikipedia.org/wiki/Software_flow_control .
That caught my eye too, but I took it to mean a complication to watch out for while sending arbitrary data across the wire.
mattdamonaging.gif
Ironically, the times I actually needed (or would be greatly helped) by kermit, I never had it on the remote. If you’re exceedingly crafty, you can usually do a lot of good (or evil) with Tcl expect module. I’d write shell snippets to set echo off, raw mode, and spawning
base64 -d > rxand other such things and it generally worked ok. Sometimes you can manage to really write fast to the serial port and overrun the buffer on the receiving end so I usually set the baud rate in the lower end. It probably explains why some of these serial port tools had some form of CRC or error correction.EDIT: I use to use this a lot, when I dealt with debug serial consoles on various devices… https://github.com/adedomin/dot-files/blob/master/.config/zsh/util-bin/termview The idea is you’d just throw tcl code into your config as a key bind.
Still use C-Kermit for some automation tasks, and I used it heavily on a Commodore 128 when all I had for Internet access was a dialup shell account.