error modifying OPA0: error message on login
pbritto
%SET-W-NOTSET, error modifying OPA0:
-SET-I-UNKTERM, unknown terminal type
I was told (thanks for this group) that the graphic card I've got is
not supported by OpenVMS a PowerStorm. Is this a configuration problem
or it's the card fault?
By the way, I think this is the same reason why I can start the EDIT?!
Thanks
Alan Greig
pbritto wrote:
> When I login I get the 2 following errors:
> %SET-W-NOTSET, error modifying OPA0:
> -SET-I-UNKTERM, unknown terminal type
Technically that's one error :-) It just means that VMS couldn't
identify the terminal. Might still be worth actually trying SET
TER/VT100 to see if most basic emulation works. Otherwise startup IP and
telnet into the box using a decent terminal emulator (Putty is a good
free one). Or else connect to the serial port with a terminal emulator.
>
> By the way, I think this is the same reason why I can start the EDIT?!
Related. Your console is stuck in basic mode. You are not running a
DECWindows terminal.
>
> Thanks
>
--
Alan Greig
Peter 'EPLAN' LANGSTOEGER
>When I login I get the 2 following errors:
>%SET-W-NOTSET, error modifying OPA0:
>-SET-I-UNKTERM, unknown terminal type
This is one error (%), the second line is only an additional more precise
info on a continuation line (-). It tells, that you (probably SYLOGIN.COM
or LOGIN.COM) did a SET TERMINAL/INQUIRE and the terminal (emulator)
didn't respond to the emitted escape sequences (for identifying).
So you have some options:
1) Use a terminal emulator which understands and responds to the escape
sequences (PuTTY comes to mind).
2) Replace SET TERMINAL/INQUIRE with a SET TERMINAL/DEVICE=xxx (where xxx
is "VT52", "VT100", "VT220" and so on - best bet is VT100 for 7bit ASCII)
The terminal type you choose must match (one of) the type(s) your terminal
(emulator) understands/supports.
3) Live with the error message.
But probably the error message is not your problem. Not able to EDIT
is more likely your problem.
>I was told (thanks for this group) that the graphic card I've got is
>not supported by OpenVMS a PowerStorm. Is this a configuration problem
>or it's the card fault?
Only half of the PowerStorm cards are supported by VMS:
3D30, 4D20, 300, 350
Others (with the texture buffer = "T") are unfortunately not supported
4D40T, 4D50T, 4D51T, 4D60T
So, it's your fault that you took a graphic card, which is not supported
by OpenVMS, for OpenVMS with MOTIF. There are no drivers for them, nobody
wrote them. Live with it. Or better, replace the cards with supported ones.
>By the way, I think this is the same reason why I can start the EDIT?!
Yes and no. EDIT needs a terminal which understands the (escape) sequences
for cursor control and video attributes. One step is to have such a terminal
(which might or might not be a problem for you) and another step is to tell
it all VMS applications - like EDIT - (via SET TERMINAL/DEVICE) which one
of the list of possible/supported terminals it is.
--
Peter "EPLAN" LANGSTOEGER
Network and OpenVMS system specialist
E-mail pe...@langstoeger.at
A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist
Peter 'EPLAN' LANGSTOEGER
I forgot to add, you are probably not using a terminal (emulator) on a
serial (console) line, but the monitor on the graphic card in console
(VGA) mode. I remember having seen a basic terminal emulation builtin
in Alpha console mode. And if I remember correctly, it was VT52. I don't
know if all Alphas/SRM had this (undocumented ?) feature.
So, do a SET TERM/VT52 and then try to EDIT/EDT (EVE doesn't support VT52
and brings %TPU-E-NONANSICRT, SYS$INPUT must be supported CRT) and tell us
what it does. (EDT can be used in line mode and is better than nothing for
editing files on a console monitor).
H Vlems
likely looking at a PC style monitor, with the PC style mouse and
keyboard as well.
That is the side effect of a non supported graphics card (I know
because my AS1000A does exactly the same thing :-).
You cannont SET TERMINAL/INQUIRE because the monitor either does not
know how to reply to that inquiry or does answer but the answer is not
understood by the terminal driver. Whatever happens, the end result is
a terminal type set to UNKNOWN.
If you want to edit files and you want / must use OPA0 then you've got
several options:
(1) SET TERM/VT52 and use EDIT/EDT: some graphics cards allow that.
Personal experience: ELSA Gloria card on Digital Server 5305. Not
everything works in EDT but you'll learn to live with the limited
possibilities, or:
(2) SET TERM/LA34 and use EDIT/EDT in line mode: enter commands on the
* prompt.
This always works but requires some knowledge about EDT and the
contents of the file to navigate.
Hans
FredK
news:1131450113.5...@g14g2000cwa.googlegroups.com...
When an unsupported graphics card with a valid VGA mode is used as a console
to boot VMS, the runtime I/O to the card is purely via firmware callbacks.
There
is no ANSI or otherwise CRT emulation available - it is a "glass TTY".
If the card is supported by VMS for VGA/Graphics - the screen will change
during the boot and display a "OpenVMS Console" message on the 25th line.
If this line is displayed, the graphics driver has a rudimentary VT52
emulator
built-in. You can use SET TERM/DEV=VT52 to allow the use of EDIT/EDT
when in the non-graphics console mode.