[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decwindows

Title:	DECWINDOWS
Notice:	DECwindows Motif V1.2-4 SSB kits: note 5519
Moderator:	GRIM::MESSENGER

Created:	Wed Nov 28 1990
Last Modified:	Fri Jun 06 1997
Last Successful Update:	Fri Jun 06 1997
Number of topics:	5861
Total number of notes:	24081

5808.0. "DISPLAY DEVICE BUSTED???" by DELNI::AULENBACK () Tue Mar 18 1997 11:23

    
    
    
    
    
    
    
    Hi Here's the problem.
    
    
    After running this file because of not being able to get 
    the command $SET DISPLAY/CREATE/NODE=NODENAME/TRANSPORT=DECNET
    to work, I've been TAILORing on DECWindows and TAILORing off
    DECWINDOWS 2-3times and also installed the latest DECwindows MOTIF
    1.2-4 with out any change!
    
    And sysgen parameter WINDOW_SYSTEM = 1
    
    WOOF$ @SYS$COMMON:[SYSUPD]DECW$VERSIONS.COM;1
    
    DECwindows ident is                     DW V1.2-4960311
    DECwindows server ident is              DW V6.2-950419
    DECwindows transport ident is           DECWINDOWS V5.4
    DECwindows xlib ident is                DW V1.2-4960311
    DECwindows OSF/Motif Toolkit ident is   DW V1.2-4960311
    DECwindows apps ident is                DW V1.2-4960312
    DECwindows programming ident is         DW V1.2-4960311
    DECwindows apps ident is                DW V1.2-4960312
    DECwindows apps ident is                DW V1.2-4960312
    DECwindows programming ident is         DW V1.2-4960311
    WOOF>
    
    
    Then I did the above command on system LKGVTX 6.2 that owe, by the way
    can't
    do a $set display/create/node=virmen  ! With an error no such device
    available.
    
    LKGVTX_SYSTEM:>@SYS$COMMON:[SYSUPD]DECW$VERSIONS.COM;1
    DECwindows ident is                     DW V1.2-3941205
    DECwindows server ident is              DW V6.2-950419
    DECwindows transport ident is           DW V6.2-950419
    DECwindows xlib ident is                DW V1.2-3941205
    DECwindows OSF/Motif Toolkit ident is   DW V1.2-3941205
    DECwindows apps ident is                DW V1.2-3941206
    DECwindows programming ident is         DW V1.2-3941205
    LKGVTX_SYSTEM:>
    
    See the DECwindows transport ident is the right version for LKGVTX, yet
    it still screwed up when trying to run a SET
    DISPLAY/CREATE/NODE=VIRMEN/TRANSPORT=DECNET for LKGVTX!
    
    If it's not the TRANSPORT version or the O.S. being both VMS06.2 what's
    the next logical step in finding the problem! 
    
    Thanks in Advance, with this problem.
    
    Ralph L. Aulenback
    226-5520
    DELNI::AULENBACK
    [email protected]

T.R	Title	User	Personal Name	Date	Lines
5808.1		TRNADO::BREAU		`Tue Mar 18 1997 13:56`	8
	> DECwindows transport ident is DECWINDOWS V5.4 This is a stub version on the DECwindows transport. Delete the DECW$TRANSPORT_COMMON.EXE in SYS$LIBRARY and try to use DECW$TAILOR again to restore that file. I believe there is a problem with DECW$TAILOR. /bob
5808.2	Directory R2TTMA$DIA1:[000000]	DELNI::AULENBACK		`Tue Mar 18 1997 15:00`	67
	I'm finished doing the DECW$TAILOR on command. Here is the result of the DECW$TAILOR back on! This is now about the 5th time in doing this! Here is my answer to the DECW$TAILOR on question in the end, after the users log off eventually I'll be able to reboot the machine. here is the tail end of the DECW$TAILOR on..! BACKUP-S-CREATED, created SYS$SYSDEVICE:[VMS$COMMON.SYSFONT.DECW.100DPI]TERMINA L_NARROW18_100DPI.DECW$FONT;1 %BACKUP-S-CREATED, created SYS$SYSDEVICE:[VMS$COMMON.SYSFONT.DECW.100DPI]TERMINA L_NARROW_DECTECH18_100DPI.DECW$FONT;1 %BACKUP-S-CREATED, created SYS$SYSDEVICE:[VMS$COMMON.SYSFONT.DECW.100DPI]TERMINA L_WIDE18_100DPI.DECW$FONT;1 %BACKUP-S-CREATED, created SYS$SYSDEVICE:[VMS$COMMON.SYSFONT.DECW.100DPI]TERMINA L_WIDE_DECTECH18_100DPI.DECW$FONT;1 %BACKUP-F-OPENIN, error opening _R2TTMA$DIA1:[000000]DECW062.G; as input -RMS-E-FNF, file not found %BACKUP-F-OPENIN, error opening _R2TTMA$DIA1:[000000]DECW062.G; as input -RMS-E-FNF, file not found %BACKUP-F-OPENIN, error opening _R2TTMA$DIA1:[000000]DECW062.G; as input -RMS-E-FNF, file not found %BACKUP-F-OPENIN, error opening _R2TTMA$DIA1:[000000]DECW062.G; as input -RMS-E-FNF, file not found %BACKUP-F-OPENIN, error opening _R2TTMA$DIA1:[000000]DECW062.H; as input -RMS-E-FNF, file not found %BACKUP-F-OPENIN, error opening _R2TTMA$DIA1:[000000]DECW062.H; as input -RMS-E-FNF, file not found %BACKUP-F-OPENIN, error opening _R2TTMA$DIA1:[000000]DECW062.H; as input -RMS-E-FNF, file not found Tailor-ON completed successfully ... 18-MAR-1997 14:49:27.98 SHUTDOWN -- Perform an Orderly System Shutdown on node WOOF Do you really want to shutdown node WOOF [NO]? NO %RMS-E-FNF, file not found %RMS-F-ISI, invalid internal stream identifier (ISI) value Tell me, do you think the above looks good with the RMS-F-ISI! Oh there seems to be only these savesets for DECW062..! >These are the ones right! DECW062.C;1 DECW062.D;1 DECW062.E;1 DECW062.F;1 Thanks, again.. Ralh
5808.3		GRIM::MESSENGER	Bob Messenger	`Tue Mar 18 1997 16:53`	15
	Re: .0 > Then I did the above command on system LKGVTX 6.2 that owe, by the way > can't > do a $set display/create/node=virmen ! With an error no such device > available. Where did you see the "no such device" error: when you entered the "set display" command or when you tried to run a program such as "ICO"? What output do you get from these commands: $ show device ws $ show device g -- Bob
5808.4		TRNADO::BREAU		`Tue Mar 18 1997 17:20`	10
	> DECW062.C;1 DECW062.D;1 DECW062.E;1 DECW062.F;1 These are the correct savesets for the DECwindows server. The .G and .H savesets were not included so the "file not found" isn't a problem for those files. Is there a server log file we can look at? /bob
5808.5		DELNI::AULENBACK		`Wed Mar 19 1997 07:50`	20
	Hi Bob, I get the NO SUCH DEVICE AVAILABLE right after doing the command IE: SET DISPLAY/CREATE/NODE=NODENAME %SYSTEM-W-NOSUCHDEV, no such device available !!!!Error!!!line.. LKGVTX_SYSTEM:>sho dev ws %SYSTEM-W-NOSUCHDEV, no such device available LKGVTX_SYSTEM:>sho dev g %SYSTEM-W-NOSUCHDEV, no such device available The above is the result of the commands you asked me to try.! I'm going to check on the ERROR log. I know in systartup_vms.com I have it going to a startup error log will that be good enough.. Thanks Ralph.
5808.6		DELNI::AULENBACK		`Wed Mar 19 1997 10:17`	11
	Bob, It' wouldn't have anything to do with there not being a monitor on the system would it? I'm thinking it wouldn't due to the fact that the previous version of VMS5.5-2 allowed them to do eXcursion and $SET DISPLAY/CREATE/NODE=NODENAME before the UPGRADE to VMS062.! What do you think? Ralph
5808.7		DELNI::AULENBACK		`Wed Mar 19 1997 11:38`	38
	Here is the latest on the tailor on of DECWINDOW062 from CD and not bulova. It still error, when I said no not to shutdown WOOF.! It came back with the following. 19-MAR-1997 11:11:37.97 SHUTDOWN -- Perform an Orderly System Shutdown on node WOOF Do you really want to shutdown node WOOF [NO]? %RMS-E-FNF, file not found %RMS-F-ISI, invalid internal stream identifier (ISI) value Then I ran this file again to see if the TRANSPORT got setup correct again.! No it's got no TRANPORT at all! WOOF> @DECW$VERSIONS.COM;1 DECwindows ident is DW V1.2-4960311 DECwindows server ident is DW V6.2-950419 DECwindows transport ident is not installed DECwindows xlib ident is DW V1.2-4960311 DECwindows OSF/Motif Toolkit ident is DW V1.2-4960311 DECwindows apps ident is DW V1.2-4960312 DECwindows programming ident is DW V1.2-4960311 Transport is not installed.. P.S. Again does it having a VT320 for a console have anything to do with it? Ralph
5808.8		GRIM::MESSENGER	Bob Messenger	`Wed Mar 19 1997 16:04`	6
	The fact that the WS device doesn't exist (and now the transport doesn't exist either) means that DECwindows base support isn't installed properly, i.e. DECW$TAILOR didn't do its job properly for some reason. The fact that you've got a VT320 for a console shouldn't matter. -- Bob
5808.9		DELNI::AULENBACK		`Thu Mar 20 1997 08:53`	8
	Hi Bob, My co-worker has suggested I re-install VMS062. He was reading a note of yours back from 25-oct-1995. Note number 5279.4 Is that going to be my only choice available now? Ralph
5808.10	Brute-Force	XDELTA::HOFFMAN	Steve, OpenVMS Engineering	`Thu Mar 20 1997 14:39`	11
	: -< DISPLAY DEVICE BUSTED??? >- Looks more like the tailoring is broken, or the system was inexplicably broken to start with... Reinstall OpenVMS VAX V6.2 with the DECwindows support, and reinstall DECwindows Motif, apply the DECwindows Motif patches, and try this again. (This brute-force approach is likely faster than trying to figure out exactly what happened here.)
5808.11		DELNI::AULENBACK		`Fri Mar 21 1997 14:10`	17
	Thanks, That's good news, for me! I less install to do tomorrow afternoon. My mistake, I was already planning on the re-install of VMS062, DECWINDOWS_62, and DecWINDOWS Motif 1.2 Please advise: Motif 1.2 ? Motif 1.2-3 ? Motif 1.2-4 ? This note is almost history.. Thanks for you help Steve and Bob..
5808.12		GRIM::MESSENGER	Bob Messenger	`Fri Mar 21 1997 14:57`	4
	I'd suggest installing DECwindows Motif V1.2-4 since it's the latest and greatest. There should be no problem running it on OpenVMS V6.2. -- Bob
5808.13		DELNI::AULENBACK		`Fri Mar 21 1997 15:17`	5
	Thanks Will Do... The case is closed.. Thanks for the help guys.. Ralph