Conference bulova::decwindows

Re: .0

Since this is an ACCVIO in a client library it probably doesn't have
anything to do with the fact that the graphics card is an S3Trio.

>The system is running OpenVMS V6.2-1H2. The PC maps to DECW$XMLIBSHR12 + 1B725C.

This is in the module DRAGBS, which is part of the toolkit's drag and drop
support.

>1. Is the S3TRIO supported on an Alphaserver 2100A? (If there are multiple
> types of S3TRIO, how do I tell which type my customer has?)

Yes, the S3TRIO is supported on the AlphaServer 2100A.  As it happens I've
just taken over support for the driver and DDX.  The card can have 2 MB or
1 MB of memory, which you can tell by seeing how many memory chips are
plugged into it -- not that this should matter for the problem you're
seeing.

>2. I can't find any mention of this board in the Open3D SPD. What component 
>supplies the driver for this board? The system uses SYS$GQSDRIVER.

SYS$GQSDRIVER and DECW$SERVER_DDX_S3.EXE are shipped as part of OpenVMS's
DECwindows server support.

>3. The customer claims that this used to work, until the system hung once and
>they were forced to crash it. Does anyone have an idea how to get it working 
>again?

One thing to try is to disable the DECwindows client's use of shared
linkage support.  Add this logical name definition to
SYS$STARTUP:SYSTARTUP_VMS.COM and reboot the system:

	$ define decw$ignore_share_address true

I'm not sure whether this will fix the problem, but your accvio reminds me
of a problem I worked on a year or so ago where defining this logical name
did fix the problem.  It seems to me that installing the ALPMOTF07_U3012
kit should have fixed that earlier problem, though.  Still, I think
disabling shared address linkage is worth trying.

Before doing the reboot you should also add this symbol definition to
SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM (if the command procedure doesn't
exist create it from SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.TEMPLATE):

	$ decw$loginlog == "sys$manager:decw$login.log"

This will create a log file containing the complete traceback for the
login accvio.  Once the dialog box popup up with the accvio message, click
on the OK button so the login process can exit and close the log file.
Post the log file as a reply to this note.

				-- Bob

The customer now says that at the time of the reboot he changed two things:
1. he defined decw$ignore_share_address to true
2. he autogened to increase global pages

The autogen was necessary because he had been getting messages from Perfectdisk
(a defragger) that there not insufficient global pages on the system. (He tells
me now.) He also says (now) that the problem with the logon screen started at
about the same time that he began getting the message from Perfectdisk.

I have asked him to check in SYS$UPDATE:VMSINSTAL.HISTORY to verify that the 
ALPMOTF patch was installed sucessfully.

As you see, I don't know at this point whether the problem was solved by the
decw$ignore_share_address parameter, or due to a low value of GBLPAGES.

Arthur

Defining decw$ignore_share_address to true makes DECwindows use up more
memory and run slower, so have the customer try removing this definition
and see if the problem comes back.

				-- Bob

The customer finally had an opportunity to reboot without the 
decw$ignore_share_address. The problem did not recur. Apparently, the 
problem was caused by a low value of GBLPAGES all the time.

Thank you for your help. 

Regards,
Arthur

I've changed the title of the note to reflect the actual problem and
solution (rather than "Problem with S3Trio and AlphaServer 2100A").

				-- Bob