Conference bulova::decw_jan-89_to_nov-90

1072.0. "New System yields no Login Screen" by FLATTP::SLOUGH_DE (Dennis, Salt Lake City Sales Support) Thu Jul 06 1989 18:30

	I've read and re-read all of the notes that are somewhat related
	to LOGIN screen problems.  I haven't, yet, found a solution to my
	problem, nor have I seen a note describing the same situation.

	Here is the situation;  I've installed VMS 5.1-1 and DECwindows
	5.1 on a stand-alone Vaxstation 2000 with 6 MB of memory.  I used
	the kits that are available across the network, (node MPGS).  I
	have never been able to get the login screen up.  DECW$SERVER_0
	is running, apparently ok.  I've logged in across the network and
	interactively run the following commands from DECW$STARTAPPS.COM;

	$ set display /create /permanent /transport=local  decw$startup_device
	$ IF F$trnlnm("decw$default_transport") .nes. "" then -
		set display /transport='F$trnlnm("decw$default_transport")' -
		decw$startup_device
	$ decw$startup_dev = F$trnlnm("decw$startup_device")
	$ define/nolog decw$display 'decw$startup_dev'
	$ RUN sys$system:decw$startlogin
	
	After running these commands I see a _WSAn: process that lasts
	about 2 seconds and goes away without leaving any messages or log
	files. (This test works on my GPX.)

	Before resorting to the above test I ran AUTOGEN as I would with any
	new system.  The DECW$CHECK_PARAMS.COM does not seem to complain.
	Based on what I've read in this conference I AUTOGEN-boosted
	PAGEFILE.SYS to 20000 and GBLPAGES to 25000 (15342 currently unused),
	and GBLSECTIONS to 500 (353 unused).  Still no login screen.
	Any ideas?

	Dennis Slough
	Salt Lake City
    
                          

    Have you tried running any other DECwindows clients besides loginout?
    
    You might try enabling image accounting ($set acc/enable=image) so 
    that you can use the accounting utility to see the exit status on 
    the loginout image. 
    
    If you've done any security tightening measures on your system after
    the DECwindows installation it could produce symptoms like this. For
    instance, if you had protected the xlib shareable image so that
    loginout didn't have execute access to it the WS processes would 
    cycle. 

    
    Thanks for the reply.  Sorry it's taken me so long to respond. 
    (Too many irons in the fire.)  I tried running several other DECwindows
    applications.  Each crashed yielding a similar stack dump and error
    messages.  The critical error message was PAGRDERR which implied
    a disk or file integrity problem.  The System Messages manual suggested
    running the Disk Analyzer (ANALYZE/DISK/READ_CHECK) and sure enough one
    of the messages from that utility indicated a forced error exit,
    file not specified.  Therefore I'm starting from scratch on this
    brand new installation.  Dennis