From:	CRDGW2::CRDGW2::MRGATE::"SMTP::CRVAX.SRI.COM::RELAY-INFO-VAX" 17-MAR-1992 17:15:55.58
To:	ARISIA::EVERHART
CC:	
Subj:	Re: DECwindows login background problem

From:	RELAY-INFO-VAX@CRVAX.SRI.COM@SMTP@CRDGW2
To:	Everhart@Arisia@MRGATE

Received:  by crdgw1.ge.com (5.57/GE 1.123)
	 id AA08131; Tue, 17 Mar 92 16:23:39 EST
Received: From GRUBNIK.TGV.COM by CRVAX.SRI.COM with TCP; Tue, 17 MAR 92 13:18:43 PST
Date:    Tue, 17 Mar 1992 13:16:36 -0800 (PST)
From: MAHAN@Grubnik.TGV.COM
Message-Id: <920317131636.172@Grubnik.TGV.COM>
Subject: Re: DECwindows login background problem
To: DAVIS%MISX02@KINGSTON.ARPC.ALCAN.CA(Stuart Davis), info-vax@sri.com
X-Vmsmail-To: SMTP%"DAVIS%MISX02@KINGSTON.ARPC.ALCAN.CA (Stuart Davis)"

In article <01GHR3MB6ZKW000DQY@KINGSTON.ARPC.ALCAN.CA> you write:
#
	[omitted]
#
#The first one is that when the process is activated (presumably bu the 
#DECwindows login process) there doesn't seem to be any sort of DISPLAY parameter 
#set, and thus all X programs bomb.  I've been able to work-around this just to 
#get it working by adding a SET DISPLAY/CREATE/NODE=0, but this limits the use of 
#the routine to the local Head-end and precludes the use of it with X-terminals.  
#Not quite what I wanted.
#

It works here, we have two VS4000/60 running VMS 5.5 and DECwindows v2.0.
Our backgrounds are done using two programs, one to display our logo and
another to display the background.  If this is being started by defining
the system logical name DECW$LOGIN_BACKGROUND then it has to have a display
defined for it.  Make sure it is defined /system/exec.  Also, place some
debug code inside to do a show log decw$display and send that output to
a file.  If it doesn't have one then call Digital because something is
broken.


#
#Next comes a problem with the display of the GIF file using the XV GIF viewer.  
#Now I know that I can display the file when this program is called interactively 
#- so this can't be the problem.  When this call is in the COM file which the 
#DECW$LOGIN_BACKGROUND logical is set to, it bombs with an error:
#	"couldn't malloc imagedata"
#
#Now I assume that it's trying to grab some virtual memory which it can't get 
#enough of (some sort of PGFLQUOTA thing?).  Looking at the process, it's running 
#as SYSTEM, but with the NETMBX and TMPMBX privs.  I assume that this process is 
#somehow activated by the DECwindows login process.
#

Correct, LOGINOUT.EXE starts it up doing a $CREPRC.  When you display the
image are you running as SYSTEM?

#
#I have tried using smaller GIF files (and I mean VERY small - 50 blocks) and it 
#works - nothing above this seems to.  The file I need to display for this 
#application is over 1000 blocks long, so there's a ways to go yet!
#

Generally this means that your quota is way down.  Check SYSTEM uaf entry for
process quotas.

--
Patrick L. Mahan

--- TGV Window Washer ------------------------------- Mahan@TGV.COM ---------

Be wary of strong drink.  It can make you shoot		- Lazarus Long
at tax collectors -- and miss.				  From the Notebooks of
							  Lazarus Long