Motif can not start correctly in an ES47 alphaserver machine with OPEN VMS 8.2

[WilliamSmith11]

Hi
I have install a open vms OS in a ES47 alpha server machine , but the windows motif does not start correctly , the screen in back like trying to start up but it not come up, is necessary to make the following key sequence for that motif start up from the black screen.

This key sequence are made from the local machine of course, not seen any in the monitor.

1-CTRL C
2-logo
3-and two return

After that , motif is ok .

Some Idea?

[Volker Halle · Accepted solution]

William,

on which terminal do you enter these 3 commands ? Graphics screen or serial console ?

What's the console setting (>>> SHOW CONSOLE or WRITE SYS$OUTPUT F$GETENV("CONSOLE") ) ?

OPA0: may not be logged in or allocated to any process, if MOTIF is to be started. Once the system is up - and BEFORE you enter those 3 commands - what does SHOW DEV/FULL OPA0: report (if you login via another terminal or the network) ?

Volker.

[WilliamSmith11]

In the graphic console , I only do that sequence of key and appear the motif .

W.S

[Arch_Muthiah]

Hi,

I guess you have to set some DECW parameters to specify your graphics devices in sys$manager:decw$private_server_setup.com

If you have not done this so far, please do this. Make sure you have copied sys$manager:decw$private_server_setup.template file and remaned as sys$manager:decw$private_server_setup.com

Udates this file to add or change the desired setup options in either of two sections (Cluster Common or Standalone Workstation) in the server startup file according to your env setup.

the params are:

DECW$DEVICE --- very important parameter allows to identify the graphics device you have.
DECW$PRIMARY_DEVICE,
DECW$SERVER_SCREENS,
DECW$MONITOR_DENSITY,
DECW$SEVER_DEFAULT_VISUAL_CLASS

Now restart decwindow by
$ @SYS$MANAGER:DECW$STARTUP RESTART

Archunan

[Volker Halle]

William,

after OpenVMS completes it's startup, the console terminal (OPA0:), which seems to be the graphics screen in your case, is NOT LOGGED in. The STARTUP process normally finishes with a LOGOUT message on OPA0:. If you can or need to type CTRL/C and LOGOUT, this indicates, that some interactive user is logged in on OPA0: or some process has a channel assigned to OPA0:, this prevents DECwindows from starting.

You need to find out, which process owns OPA0: after startup is finished. Login to the system over the network and issue the command SHOW DEV OPA0:/FULL and show us the output of that command.

Or - after typing CTRL/C - type a SHOW PROCESS and see which user is logged in on OPA0:

Volker.