Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services Software Patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS73_GRAPHICS-V0100 PowerStorm 300/350 Graphics V7.3 ECO Summary
TITLE: OpenVMS VMS73_GRAPHICS-V0100 PowerStorm 300/350 Graphics V7.3 ECO Summary

New Kit Date:       15-JUN-2002
Modification Date:  Not Applicable
Modification Type:  NEW KIT
 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
 
       For OpenVMS savesets, the name of the compressed saveset
       file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or
       kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS
       saveset is copied to your system, expand the compressed
       saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe.
 
       For PCSI files, once the PCSI file is copied to your system,
       rename the PCSI file to kitname.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
 

 
Copyright (c) Compaq Computer Corporation 2002.  All rights reserved.

OP/SYS:     OpenVMS Alpha

COMPONENT:  Graphics

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:  VMS73_GRAPHICS-V0100
                    DEC-AXPVMS-VMS73_GRAPHICS-V0100--4.PCSI
     ECO Kits Superseded by This ECO Kit: None
     ECO Kit Approximate Size:  51840 Blocks
     Kit Applies To:  OpenVMS Alpha V7.3
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_2
                            2 - To be installed on all systems running
                                the listed version(s) of OpenVMS and
                                using the following feature(s):

         One of the following graphics controllers:

      	   	  o  ELSA Gloria Synergy (SN-PBXGK-BB)
    		  o  JIB graphics controller (3X-DEPVD-AA)
    		  o  Trifecta (3X-DEPVZ-AA)
   		  o  PowerStorm 3D30 (SN-PBXGB-AA)
   		  o  PowerStorm 4D20 (SN-PBXGB-CA)
   		  o  3Dlabs Oxygen VX1 (SN-PBXGF-AB)
   		  o  PowerStorm 300 (SN-PBXGD-AD)
                  o  PowerStorm 350 (SN-PBXGD-AE)

     Kit Dependencies:

       The following remedial kit(s), or later, must be installed BEFORE
       installation of this, or any required kit:

         VMS73_UPDATE-V0100

       In order to receive all the corrections listed in this
       kit, the following remedial kits should also be installed:

         None

ECO KIT SUMMARY:

An ECO kit exists for PowerStorm 300/350 Graphics Controller support on
OpenVMS Alpha V7.3.

NEW FUNCTIONALITY ADDED IN THE VMS73_GRAPHICS-V0100 KIT:

  o  This document contains the release  notes  for  PowerStorm  300/350
     Graphics  Support  Version  2.0  for OpenVMS.  Specific information
     about this support can be found  in  the  P300_350_V2_README  file.
     This file is available in the following formats:

        File                         Format
        -------------------          ------------------
      
        P300_350_V2_README.TXT           Text
        P300_350_V2_README.PDF           Acrobat Reader  
        P300_350_V2_README.HTML          HTML
        P300_350_V2_README_CONTENTS.HTML HTML


     These files can be found at SYS$COMMON:[SYSHLP]


  O  New ELSA GLoria Synergy DDX image

     A new device dependent  X  server  image  is  provided  to  improve
     performance  on  EV6 (21264) based platforms containing ELSA GLoria
     Synergy     graphics      modules.       A      new      procedure,
     SYS$MANAGER:DECW$DEVICE_CONFIG_P2.COM,  is  executed  automatically
     during DECwindows startup.  The new procedure will, on  appropriate
     platforms,  define  a logical name that will redirect the server to
     use the new P2 device  dependent  X  code,  DECW$SERVER_DDX_P2.EXE.
     DECW$SERVER_DDX_GZ.EXE  will continue to be used on older platforms
     containing ELSA GLoria Synergy graphics modules.

     Image(s) Affected: [SYSLIB]DECW$SERVER_DDX_P2.EXE


GENERAL GRAPHICS PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT

  o  Attempts to use the MIT-SHM Shared Memory Extension fail  with
     the following error:

     X Error of failed request:  BadAccess (attempt to access private
     resource denied)
     Major opcode of failed request:  131 (MIT-SHM)
     Minor opcode of failed request:  1 (X_ShmAttach)
     Serial number of failed request:  11
     Current serial number in output stream:  12


          Images Affected: [SYSLIB]DECW$SERVER_DIX.EXE


  o  In OpenVMS V7.3,  the  default  decwindows  transport  can  be
     specified         via         the         logical         name
     DECW$SETDISPLAY_DEFAULT_TRANSPORT.  However, any  SET  DISPLAY
     commands   will  now  change  the  transport  to  the  default
     transport,  not  the  transport  previously  specified.    For
     example,

     $ show display

        Device:    WSA24:  [super]
        Node:      NODE1
        Transport: DECNET
        Server:    0
        Screen:    0

     $ show log DECW$SETDISPLAY_DEFAULT_TRANSPORT
         "DECW$SETDISPLAY_DEFAULT_TRANSPORT" = 
                                    "tcpip" (LNM$SYSTEM_TABLE)
     $ set displ/node=NODE2
     $ show display
         
	  Device:    WSA24:  [super]
          Node:      NODE2
          Transport: tcpip
          Server:    0
          Screen:    0

     $ set display/screen=1
     $ show display

           Device:    WSA24:  [super]
           Node:      NODE1
           Transport: tcpip
           Server:    0
           Screen:    1

     The   DECW$SETDISPLAY_DEFAULT_TRANSPORT   default    transport
     setting  should  only  be  used with the "$set display/create"
     qualifier.

          Images Affected:  [SYSEXE]DECW$SETSHODIS.EXE


  o  Under some  circumstances  the  DECwindows  server  can  abort
     during  startup.  The SYS$MANAGER:DECW$SERVER_0_ERROR.LOG file
     contains  the  error  message  "failed  to   initialize   core
     devices".

          Images Affected:  [SYSLIB]DECW$SERVER_DIX.EXE

  o  When drawing connected line segments with the line  width  set
     to 1, the pixel at the join point between two line segments is
     not drawn in some cases.

          Images Affected:  [SYSLIB]DECW$SERVER_DIX.EXE


  o  The system may crash with an SSRVEXCEPT or  PGFIPLHI  bugcheck
     on  SMP  systems  when  terminating client processes which are
     connected using the local transport.

          Images Affected:  [SYSLIB]DECW$TRANSPORT_LOCAL.EXE


ELSA PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT:

  o  When  an  X/Motif  application  issues  an  XDrawRectangle  or
     XDrawRectangles  request  with  a  negative  x coordinate, the
     coordinate is incorrectly treated as a large positive  number,
     resulting in spurious lines being drawn on the screen.

          Images Affected:  [SYSLIB]DECW$SERVER_DDX_GZ.EXE


  o  If the DECwindows server  is  started  with  the  pixel  depth
     (DECW$SERVER_PIXEL_DEPTH  logical  name) set to 16, the server
     will crash.  This problem is seen with the ELSA Gloria Synergy
     graphics  controller  (SN-PBXGK-BB), only when using the older
     DECW$SERVER_DDX_GZ.EXE server image.

          Images Affected:  [SYSLIB]DECW$SERVER_DDX_GZ.EXE


  o  When  using  the  ELSA  Gloria  Synergy  graphics   controller
     (SN-PBXGK-BB)  in  8 bit mode, the DECwindows server can crash
     when copying data from the screen to a pixmap.  This  is  most
     often  seen  when  performing  a drag-and-drop operation.  The
     server can crash in several different locations  depending  on
     the  timing  of  the  operation.   Another symptom of the same
     problem is that the server can return spurious BadAlloc errors
     (server resources exhausted).

          Images Affected:  [SYSLIB]DECW$SERVER_DDX_GZ.EXE


  o  There are screen  corruption  problems  when  using  the  ELSA
     Gloria Synergy graphics controller (SN-PBXGK-BB):

       o  Spurious  horizontal  lines  are  displayed  when  drawing
          diagonal lines in 8 bit mode.

       o  When dragging a window on the screen with "display  window
          contents  during move" enabled and the screen backdrop set
          to Background, remnants of the window are left  behind  on
          the backdrop.


          Images Affected:  [SYSLIB]DECW$SERVER_DDX_P2.EXE


  o  When  using  the  ELSA  Gloria  Synergy  graphics   controller
     (SN-PBXGK-BB)  and  running  applications which write a lot of
     data to the screen  (such  as  rapidly  scrolling  text  in  a
     DECterm window), the system clock loses time.

          Images Affected: [SYS$LDR]SYS$GZDRIVER.EXE
                           [SYS$LDR]SYS$GZVDRIVER.EXE


  o  User messages enabled in  the  console  variable  BOOT_OSFLAGS
     (bit<17> = 1) or on the console BOOT command line (e.g., >>> B
     -FL 0,20000) may cause a system crash or  hang  while  booting
     with an ELSA GLoria Synergy graphics controller (SN-PBXGK-BB),
     a  JIB  graphics  controller  (3X-DEPVD-AA),  or  a   Trifecta
     graphics controller (3X-DEPVZ-AA), especially on an SMP system
     with the console variable CONSOLE set to SERIAL.

          Images Affected: [SYS$LDR]SYS$GZDRIVER.EXE


  o  Some monitors like the Compaq P75 & P700, fail to  synchronize
     when the Trifecta graphics controller (3X-DEPVZ-AA) or the JIB
     graphics controller (3X-DEPVD-AA) attempts to put  the  screen
     into  standby  mode.   The  problem  manifests itself with the
     screen going partly black; you may see a partial  display  and
     the screen may blink and/or click.

          Images Affected:  [SYS$LDR]SYS$GZDRIVER.EXE
                            [SYS$LDR]SYS$GZVDRIVER.EXE

TGA2 (POWERSTORM 4D20/3D30) PROBLEMS IN THE VMS73_GRAPHICS-V0100 KIT:

  o  When  booting  with  a  PowerStorm  3D30  (SN-PBXGB-AA)  or  a
     PowerStorm  4D20  (SN-PBXGB-CA)  graphics  controller  and the
     SYSGEN parameter POOLCHECK enabled, the system may crash  with
     an ACCVIO bugcheck.

          Images Affected:  [SYS$LDR]SYS$GYCDRIVER.EXE

VX1 PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT

  o  Screen corruption problems occur when using the 3Dlabs  Oxygen
     VX1 graphics controller (SN-PBXGF-AB):

       o  Video corruption is produced when dragging  certain  icons
          around the CDE desktop.  For example, after moving an icon
          from the Application Manager window to the  desktop,  each
          subsequent  move  of  the  icon  on  the desktop (backdrop
          required), leaves behind unintended pixels.

       o  With selected backdrops, video corruption is produced when
          dragging  objects  around  the  CDE desktop.  For example,
          when dragging a window around the desktop with the  "GRAY"
          backdrop  selected,  remnants of the left and right window
          borders are left behind on the  desktop  in  the  form  of
          spurious vertical lines.


          Images Affected:  [SYSLIB]DECW$SERVER_DDX_P3.EXE


  o  With the 3Dlabs Oxygen VX1 graphics  controller  (SN-PBXGF-AB)
     and  either  8 or 16 bits per pixel selected, extra pixels may
     be drawn around the edges of objects.

          Images Affected: [SYSLIB]DECW$SERVER_DDX_P3.EXE


  o  With the 3Dlabs Oxygen VX1 graphics controller  (SN-PBXGF-AB),
     the  Monitor  utility  may  show  excessive time in "Interrupt
     State" when the screen saver is active.

          Images Affected:  [SYS$LDR]SYS$GFDRIVER.EXE


P350 PROBLEMS ADDRESSED IN THE VMS73_GRAPHICS-V0100 KIT:

  o  Occasionally  the  DECwindows  server  would  crash  when   an
     application did extensive creation and deletion of 3D contexts
     interspersed  with  extensive  2D  drawing,  including  window
     creation and destruction.

          Images Affected:  [SYSLIB]DECW$SERVER_DIX.EXE
                            [SYSLIB]DECW$OPENGLPEERRI.EXE


  o  Running the Viewperf 6.1.2 MedMCAD test causes an  application
     crash  when using LOCAL transport or a server crash when using
     network transport.

          Images Affected:  [SYSLIB]DECW$SERVER_RIDDGL.EXE
                            [SYSLIB]DECW$OPENGLPEERRI.EXE

  o  When 3D contexts using a  network  connection  are  destroyed,
     their  buffers are not being properly deallocated.  The result
     is that, as applications create and delete 3D  contexts,  over
     time  the  server's  virtual  memory  undergoes  unconstrained
     growth.

          Images Affected: [SYSLIB]DECW$SERVER_DDX_GB.EXE

  o  Certain OpenGL viewing  transformations  result  in  incorrect
     placement of primitives drawn.

          Images Affected:  [SYSLIB]DECW$OPENGLPEERRI.EXE
                            [SYSLIB]DECW$SERVER_RIDDGL.EXE


  o  The following problems are corrected:

       -  Repeated calls to glXMakeCurrent with a network connection
          caused  a slow but steady increase in the server's virtual
          memory space.

       -  Drawing polygons or triangles in GL_LINE  mode  along  the
          bottom  or  right  edge of the OpenGL viewport resulted in
          extra lines being drawn along the edge of the viewport.

       -  When a single OpenGL context was used  to  render  to  two
          different windows, sometimes the display in one window was
          corrupted.

       -  Stippled line strips  with  sub-pixel  segments  were  not
          rendered by OpenGL.

       -  In some instances, the DECwindows server would  hang  when
          rendering certain horizontal lines as filled rectangles.

       -  In some instances, the DECwindows server would  hang  when
          rendering certain polygons.

       -  Drop-down menu items became blank when the mouse was moved
          over a menu tear-off line.

       -  In some instances, pixel corruption  would  occur  when  a
          window was moved over a highlighted item.


          Images Affected:  [SYSLIB]DECW$OPENGLSHR_V11.EXE
                            [SYSLIB]DECW$OPENGL_PROTOCOL_V11.EXE
                            [SYSLIB]DECW$OPENGLPEERRI.EXE
                            [SYSLIB]DECW$SERVER_DDX_GB.EXE
                            [SYSLIB]DECW$SERVER_RIDDGL.EXE
                            [SYSLIB]DECW$SVEXT_GLX_P350.EXE


  o  Some  programs  using  GLUT   (OpenGL   Utility   Toolkit)   -
     specifically the glutIdleFunc function - would loop infinitely
     and/or ignore keyboard/mouse input.

          Images Affected:  [SYSLIB]DECW$OPENGLUTSHR.EXE

  o  XFillRectangle calls with extremely  out-of-range  coordinates
     sometimes  resulted in erroneous drawing artifacts outside the
     window.

          Images Affected: [SYSLIB]DECW$SERVER_DDX_GB.EXE
                           [SYSLIB]DECW$SERVER_RIDDGL.EXE


INSTALLATION NOTES:

The images in this kit will not take effect  until  the  system  is
rebooted.

If you have other nodes in your OpenVMS cluster, they must also  be
rebooted  in  order  to make use of the new image(s).  If it is not
possible or convenient to reboot the entire cluster at this time, a
rolling re-boot may be performed.

INSTALLATION INSTRUCTIONS:

Install this kit with the POLYCENTER Software Installation  utility
by logging into the SYSTEM account, and typing the following at the
DCL prompt:

PRODUCT INSTALL VMS73_GRAPHICS /SOURCE=[location of Kit]

The kit location may be a tape drive, CD, or a disk directory that
contains the kit.

Additional help on installing PCSI kits can be found by typing
HELP PRODUCT INSTALL at the system prompt


SPECIAL INSTALLATION INSTRUCTIONS:

  o  Scripting of Answers to Installation Questions

     During installation,  this  kit  will  ask  and  require  user
     response  to  several  questions.  If you wish to automate the
     installation of this kit and avoid having to provide responses
     to  these  questions,  you must create a DCL command procedure
     that includes the following definitions and commands:

       -  $ DEFINE/SYS NO_ASK$BACKUP TRUE
       -  $ DEFINE/SYS NO_ASK$REBOOT TRUE
       -  Add  the  following  qualifiers  to  the  PRODUCT  INSTALL
          command and add that command to the DCL procedure.

            /PROD=DEC/BASE=AXPVMS/VER=V1.0
       -  De-assign the logicals assigned

     For  example,  a  sample   command   file   to   install   the
     VMS73_GRAPHICS-V0100 kit would be:

     $
     $ DEFINE/SYS NO_ASK$BACKUP TRUE
     $ DEFINE/SYS NO_ASK$REBOOT TRUE
     $!
     $ PROD INSTALL VMS73_GRAPHICS/PROD=DEC/BASE=AXPVMS/VER=V1.0
     $!
     $ DEASSIGN/SYS NO_ASK$BACKUP
     $ DEASSIGN/SYS NO_ASK$REBOOT
     $!
     $ exit

All trademarks are the property of their respective owners.
Files on this server are as follows:
»dec-axpvms-vms73_graphics-v0100--4.README
»dec-axpvms-vms73_graphics-v0100--4.CHKSUM
»dec-axpvms-vms73_graphics-v0100--4.pcsi-dcx_axpexe
»vms73_graphics-v0100.CVRLET_TXT
privacy statement using this site means you accept its terms