Operating System - OpenVMS
1752723 Members
5861 Online
108789 Solutions
New Discussion юеВ

Motif can not start correctly in a ES47 with open VMS 8.2

 
SOLVED
Go to solution
WilliamSmith11
Super Advisor

Motif can not start correctly in a ES47 with open VMS 8.2

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?

rperez
3 REPLIES 3
Volker Halle
Honored Contributor
Solution

Re: Motif can not start correctly in a ES47 with open VMS 8.2

see the other thread:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=965286

and please consider to close this one.

Volker.
Arch_Muthiah
Honored Contributor

Re: Motif can not start correctly in a ES47 with open VMS 8.2

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
Regards
Archie
Steven Schweda
Honored Contributor

Re: Motif can not start correctly in a ES47 with open VMS 8.2

Does this guy have a bad answer for _every_
question?

I'm with Volker Halle. Worry about what has
OPA0 busy. Normally, when the system start-up
ends, OPA0 is free. Try to figure out what
you're stopping with that CTRL/C. (I assume
that CTRL/T is not enabled.) Is it something
which is hung, or perhaps just very slow?