Thanks! That worked. Joshua: In my testing, the patch to strip trailing \r\n is not necessary as checking the “Telnet mode” box in the socket configuration makes telnet work. There’s also a bug in the patch which causes commands to no longer be accepted over the socket when “Telnet mode” is enabled.
Ken: I’m not sure you still need to have a non-telnet option. Even simple command line tools like netcat are able to handle telnet negotiation these days. $ echo sd | nc -t localhost 2023 Welcome to the VirtualT v1.8 TELNET interface. Use decimal, C hex (0x2a) or Asm hex (14h) for input. Return data reported according to specified radix. Type 'help' for a list of supported comands. Ok> Dec 24,2025 Wed 10:48:38 VirtualT 1.8 BASIC TEXT TELCOM ADDRSS SCHEDL -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- -.- Select: _ 29638 Bytes free Ok> Or, if plain sockets are needed, may I suggest that “Telnet mode” should be on by default when the socket interface is enabled? —b9 P.S. This is probably too much work, but it might be useful to implement Unix domain sockets. Since it'd just be a file in the current directory, it would be secure for Virtual-T to enable the socket interface by default without fear of inadvertently opening the service to the whole world as can happen with TCP/IP.
