[Info-vax] EMU-vm follow-up

[Paul Sture]

On Sat, 04 Aug 2012 01:51:25 +0000, Vertis Sidus wrote:

> On 2012-06-18, Single Stage to Orbit <alex.buell at munted.eu> wrote:
>> On Mon, 2012-06-18 at 22:58 +0200, Artem Alimarin wrote:
>>
>>> It be must RAW mode, because the console does not speak TELNET but
>>> rather just sends characters to the VT100 or whatever is connected.
>>
>> It is. telnet passes the stream of bytes to the underlying terminal,
>> which happens to be gnome-terminal on my Gentoo installation which
>> probably doesn't know to force NOECHO/NOLN on.
>>
>> I have another script which perfectly emulates a VT100 terminal which I
>> will try out. If it works, I'll post the script here.
> 
> I know I'm a bit late to this, but I'm using gnome-terminal as well, and
> I'm certain the echo comes from the telnet client, not the terminal. The
> solution I found was to install socat and use this command to connect:
> 
>   socat -,raw,echo=0 tcp:127.0.0.1:20000
> 
> I think netcat will probably work for this too, but I couldn't figure
> out how to make that happen.

Thanks very much.  That incantation of socat works fine here.

My mix is Xfce and Fedora 17 (64 bit).

A SET TERM/INQUIRE gives me VT200 here, but it isn't (EDIT/TPU outputs 
"garbage"). SET TERM/VT100 gets me started, though the numeric keypad in 
TPU is way off and doesn't appear to work at all in EDT.  Things like 
MONITOR MODE and MONITOR SYSTEM display correctly.

VIM  or line mode EDT to the rescue :-)

socat also works during a conversational boot.  Using the raw option of 
PuTTY I was getting dropped characters at the SYSBOOT prompt, to the 
extent where I couldn't even enter SET STARTUP_P1 "MIN".

-- 
Paul Sture