AH! Sorry, thank you.
--
bkw
On 1/8/20 10:00 PM, Kurt McCullum wrote:
No, that's not what I was saying.
Page 72 of the TELCOM manual for the T200 (Same as M100 but double the
lines)
"....TELCOM uses the same codes as a 'vt52'....."
Then right after that it explains that a normal vt52 would have 24 lines
and so a new termcap entry would have to be made with only 16 lines and
called td200. The M100 would be the same with only 8 lines.
mComm doesn't do any screen emulation. The only thing that mComm does is
handle buffering so the serial port on the Model-T doesn't get overloaded.
Kurt
On Wed, Jan 8, 2020, at 4:17 PM, Brian K. White wrote:
On 1/8/20 6:10 PM, Charles Hudson wrote:
> Thank you Kurt for your reply. I'll start looking for C64 BBSs to
> contact; makes sense now I think of it. Never would have guessed
VT-52,
> either.
>
> -CH-
I think Kurt was saying that if you used mComm's virtual modem, mComm
emulates vt-52. In that scenario, mComm is the terminal as far as the
BBS is concerned. The M100 is only connected to mComm, not the bbs, and
mComm knows how to talk to a M100. So mComm ends up being a proxy or
translator between the M100 and the BBS.
The M100 itself doesn't emulate anything else, unless you run a terminal
emulator app on it. Otherwise, it just IS a Model 100 terminal. It would
be up to any host to know how to talk to a M100 terminsl.
Few/No BBS's will have a m100 terminal option. If you were connecting to
a linux of unix box of your own, the way you would get proper terminal
behavior is you would install an m100 termcap or terminfo entry onto the
linux box, which teaches all apps on that box how to talk to an M100.
BBS's generally only offer a very few, or even just one terminal option,
generally just "ansi". So instead of the server having a dictionary of
definitions for all kinds of different terminals, a BBS just has one
very common terminal definition, and all clients have to emulate that
standard.
You have about 5 options:
* convince a bbs sysop to add M100 terminal support to their bbs
* find a terminal emulator app that runs on an m100 and emulates a
common terminal like vt-100 or pc-ansi
* live with the terminal not being perfectly matched to the host. Just
try to get the main things like the break key and the lines & columns if
they are configurable per-user or per-session, and call yourself lucky
* go through an intermediary like mComm or a raspberry pi, where you can
configure the Pi with a proper M100 termcap, and run gnu screen or
minicom or telnet or something on the pi, and IT does vt100 or ansi
emulation to the bbs. m100 logs in to the Pi, then you run something on
the pi to log in to the remote bbs.
* see if the bbs offers a plain text or "ascii" or "glass tty" or "dumb"
option. You could use that.
There's a few different m100 termcap definitions floating around.
I haven't gone through them to figure out which is best, if they are not
all identical.
http://www.club100.org/library/libref.html
http://m100.bbsdev.net/
http://www.ordersomewherechaos.com/rosso/fetish/m102/web100/docs/termcap.html
--
bkw
--
bkw
