Subj : Re: Commandline Telnet Client...
To   : Shurato
From : Shurato
Date : Fri Feb 09 2024 11:09 pm


 Sh> https://shsbbs.net/lintel.png for the linux telnet output in syncterm and:
 Sh> https://shsbbs.net/wintel.png for the windows telnet output in syncterm.
 Sh> You can see why one is much better than the other, but I don't  understand
 Sh> why none of the windows CLI options (Microsoft telnet, cygwin telnet
 Sh> and plink.exe) work as well as the linux one. I'm using a Debian
 Sh> 12 VM with ssh telneting internally to my BBS to allow an SSH tunnel
 Sh> to the BBS.  I'd love to be able to do this within windows the same
 Sh> way, but it doesn't look likely. I'll just live with a Linux VM that
 Sh> only has a few purposes taking up 3Gb of RAM and 2 cores... :(.

I didn't see a single reply after this  message, but upon logging onto
another fsxnet system, saw several...  It looks like I need to turn off ANSI
parsing for windows some how, but I don't know how to do that.  I thought
using plink.exe or cygwin's telnet would do that, but they just display
garbled ansi that even syncterm can't interpret.

---
Shurato, Sysop Shurato's Heavenly Sphere (ssh, telnet, pop3, ftp,nntp)
(ports 22, 23, 110, 21, 119) (ssh: login bbs password shsbbs)


*** THE READER V4.50 [freeware]
---
 * Origin: Shurato's Heavenly Sphere telnet://shsbbs.net (21:2/148)

.