console problem HP 700/96

[Fred Martin_1]

I have an HP 700/96 system console. One day I walked in the server room and found a heavy pile of papers on the keyboard, the keyboard clicking away.

I powered off the terminal, but had problems, so I tried both a hard reset and a soft reset, as described in the console's manual.

Still, it acts now as though the term type is wrong; I have to stty the backspace so it works right, and going into 'vi' is a disaster as it misinterprets the control codes.

The TERM variable is set to VT220, same as it has always been.

Any ideas? I've had to reset it in the past, but it always came up happy. Not this time.

[Marco Santerre]

You may want to turn off your console, press the "D" key and hold it, then turn the power on on your console to restore the default values.

[Uday_S_Ankolekar]

If you haven't tried this then,

- To perform a soft reset, press .
- To perform a hard reset:
keys simultaneously.

If both fails then last chance is to turn off, then turn on the terminal while pressing .



-USA..

[Fred Martin_1]

I found that "D" key to go back to defaults in other discussions here - tried that too. Same problem.

The terminal communicates OK, as long as control codes don't come into play. So it's nothing to do with COMM settings.

Anything else to try?

[Fred Martin_1]

Oh yeah I restarted the console getty, too, that didn't do anything.

In SAM, the console is listed at hardware path 8/0/0, port 0, speed 0. That seemed odd to me but as I said, it works except for control codes so I suspect that part it fine.

[David Bell_1]

Fred,

Try checking the terminal ID string in the "terminal configuration". See if it says "700/96". If not, try changing it to that.
This is not where the terminal is set to VT220 or VT100, etc.


HTH,

Dave

[Pete Randall]

Fred,

When you say the TERM variable is set to VT220, are you referring to the ConfigKeys/TermConfig menu selection? It seems to me that for a HP 700/96 console, that ought to be set to HP - at least that's what mine are set to.

Pete

[Fred Martin_1]

Well I was referring to the TERM variable in the OS.

But, I looked in the terminal's config menu.

Keyboard: USASCII
Terminal ID: 70096

[Patrick Wallek]

What happens if you set your TERM to HP after you log in?

# export TERM=hp

[Pete Randall]

Fred,

Do you know if that's what the TermID has alwasy been set to?

I'm wondering what keys may have gotten pressed while the pile of papers were "auto-keying".

Pete

[Fred Martin_1]

Setting the shell's TERM to HP helps a little, i.e. 'vi' isn't as bad. Still, I get garbage on screen.

I don't know the previous setting for the terminal ID, or if it's changed.

[Hai Nguyen_1]

Can you try setting TERM to vt100? I used to have some problem with vt200.

Hai

[Marco Santerre]

I do have my consoles set up with a terminal emulation of HP on the console config (I don't remember correctly the right sequence, but if you press "config keys" "terminal config" and the last option set to "HP") and once I log in, I also do a
#export TERM=hp
#tset

[Pete Randall]

Fred,

My completely unguaranteed recommendation would have to be to set both the TermID and the TERM variable to hp.


Pete

[Fred Martin_1]

I can try the TERM settings and I will, but I must say, prior to the keyboard event it all worked, and the shell has not changed.

I've no doubt that it's an issue with the terminal itself.

[Pete Randall]

Fred,

In that case, maybe you could try setting the TermID to match the VT220 TERM variable. In either case, I think you need to change the TermID and then match that with the TERM variable.

Pete

[Fred Martin_1]

OK I got it...

All I changed was TERM ID in the Terminal Config to EM220 (was HP).

Everything is good.

Now I just need to make sure it's saved in the config...

Thanks for the input folks!

[Fred Martin_1]

Sorry not TERMID -- the field was Term Mode.