SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
Motif ALPDWMW02_U3012 Alpha Motif V1.2-3 Worldwide Support ECO Summary

NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. The name of the compressed file will be kit_name-dcx_vaxexe for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha. Once the file is copied to your system, it can be expanded by typing RUN compressed_file. The resultant file will be the OpenVMS saveset or PCSI installation file which can be used to install the ECO. *Motif] ALPDWMW02_U3012 Alpha Motif V1.2-3 (Worldwide Support) ECO Summary Copyright (c) Digital Equipment Corporation 1996, 1998. All rights reserved. PRODUCTS: DECwindows Motif[R] V1.2-3 OpenVMS User Interface/Cesky DECwindows Motif[R] V1.2-3 OpenVMS User Interface/Magyar DECwindows Motif[R] V1.2-3 OpenVMS User Interface/Polski DECwindows Motif[R] V1.2-3 OpenVMS User Interface/Russkij DECwindows Motif[R] V1.2-3 OpenVMS User Interface/Slovensky DECwindows Motif[R]/Hangul V1.2-3 for OpenVMS DECwindows Motif[R]/Hanyu V1.2-3 for OpenVMS Alpha DECwindows Motif[R]/Hanzi V1.2-3 for OpenVMS Alpha DECwindows Motif[R]/Hebrew V1.2-3 for OpenVMS Alpha DECwindows Motif[R]/Japanese V1.2-3 for OpenVMS Alpha DECwindows Motif[R]/Thai V1.2-3 for OpenVMS Alpha COMPONENTS: Calendar Print Screen Paint CDA Viewer Login Xm Library 1.2.3 DXm Library 1.2.3 Xt Intrinsics Library R5 Xlib OP/SYS: DIGITAL OpenVMS Alpha V1.5 and Higher SOURCE: Digital Equipment Corporation ECO INFORMATION: ECO Kit Name: ALPDWMW02_U3012 ECO Kits Superseded by This ECO Kit: ALPDWMW01_U3012 ECO Kit Approximate Size: 24498 Blocks Kit Applies To: DECwindows Motif V1.2-3 System/Cluster Reboot Necessary: See INSTALLATION NOTES Below RELATIONSHIP BETWEEN THE DWMW02_U3012 AND MOTF08_U3012 KITS: The DWMW02_U3012 kits (VAXDWMW02_U3012 and ALPDWMW02_U3012) contain only a subset of the bug fixes in the MOTF08_U3012 kits (VAXMOTF08_U3012 and ALPMOTF08_U3012). DWMW01_U3012 includes the same bug fixes as MOTF08_U3012 for Xlib, the Xt, Xm, Mrm and DXm toolkits and DECW$LOGINOUT.EXE, and it includes Year 2000 fixes for several applications. MOTF08_U3012 should only be installed on systems that are not running the DECwindows Motif V1.2-3 Worldwide Support kit, and DWMW02_U3012 should only be installed on systems that are running the DECwindows Motif V1.2-3 Worldwide Support kit. The Worldwide Support kit is part of the following DECwindows Motif language variants, so users of these language variants should install DWMW02_U3012: Hanzi Hangul Hanyu Thai Japanese Russian Czech Hungarian Polish Slovak Users of the following language variants, as well as U.S./English users, should install MOTF08_U3012: German French Italian Swedish Spanish Hebrew Installing DWMW02_U3012 on a U.S. system or installing MOTF08_U3012 on a Worldwide system can result in some serious problems. The V1.2-3 variants listed above) consist of the V1.2-3 libraries and V1.2 applications. The V1.2-3 applications have not been tested in the worldwide environment and may not work correctly. One known problem is that DECterm wont start due to the presence of the image DECW$DXMAIMSHR.EXE (the Asian Input Method). Since MOTF08_U3012 installs V1.2-3 applications on the system disk, installing MOTF08_U3012 on a system running the V1.2-3 Worldwide Support kit (i.e. with an Asian or East European language) results in an unsupported configuration which may not work correctly. That is why Engineering is providing the DWMW02_U3012 patch kit: it allows DECwindows Motif Worldwide customers to install the Xlib and toolkit images from MOTF08_U3012 (plus additional internationalization and Year 2000 fixes) without also installing the MOTF08_U3012 applications and programming support files. DWMW02_U3012 also includes the DECW$LOGINOUT.EXE image from MOTF08_U3012 in order to allow users to log in on OpenVMS V7.1 systems. Since V7.1 was an unreleased version of OpenVMS at the time the DWMW01_U3012 and MOTF07_U3012 kits were released the login fix is mentioned in the kits submission forms but not in the cover letters or release notes. ECO KIT SUMMARY: An ECO kit exists for DECwindows Motif V1.2-3. This kit addresses the following problems: Problems Addressed in the VAXDWMW02_U3012 Kit: NOTE: The problems will be fixed in the next release of DECwindows Motif after V1.2-4. Calendar Problems: o In DECwindows Motif V1.2-4, DECW$CALENDAR currently accepts a two digit year in its interchange format. However, the two digit year will not work in the year 2000 and beyond. This problem is corrected in the remedial kit by interpreting two digit years as being in the range 1970-2069. DECW$CALENDAR always use a four digit year when writing in the interchange format. Two digit years can only arise if interfacing Calendar with other programs. Print Screen Problems: o When DECW$PRINTSCREEN generates a PostScript file it writes introductory comments to this file. After the end of 1999, the date written to the file will be wrong. For example, the year 2000 would be output as "19100". Paint Problems: o When DECW$PAINT generates a PostScript file it writes introductory comments to this file. After the end of 1999, the date written to the file will be wrong. For example, the year 2000 would be output as "19100". CDA Viewer Problems: o When converting DTIF files to DDIF and the current year is 2000 or later, the year is written incorrectly to the DDIF file. The first two digits of the year are always written as 19. DXM Library Problems: o Creating a grey-scale colormix widget would cause an ACCVIO. o Using the help widget, the visit topic option would always display a window with left to right text display. The text direction should have been inherited from the help widget. o With the DXmCSText widget, replacement of text could fail and sound the bell instead. The problem would occur if the text field was at the maximum length and some of it had been selected for replacement. o If parts of the print widget were suppressed the display would be poorly formatted and unusable. o Using the CtrlosfDown and CtrlosfUp keys to move up or down an Svn widget display would not leave the location correctly defined. This could cause various errors when an operation was subsequently executed. XM Library Problems: o With a vertical scale widget the position of the slider can be miscalculated and displayed below the end of the scale. The problem occurs only when the label is long or uses a large font. o Various problems could be observed when using drag and drop between windows on different screens of a multi-headed configuration. These problems would occur when the root window or color maps were configured differently on the two screens. o Use of pixmaps could result in memory leaks within a client application. o If the orientation of a scrollbar widget was changed, the thickness of it was not recalculated. Since the thickness can depend upon the orientation, the scrollbar would be incorrectly displayed. o When a text widget is destroyed, there is a small, unavoidable, memory leak in the client application. o XmStringGetCurrentCharSet used a default locale found by translating the logical name "XNL$LANG". Everywhere else in DECwindows Motif 1.2-3, the default locale is found by translating the logical name "LANG". The remedial kit uses "LANG" for the default locale. o If a scrolled window is created and the text direction for the window is changed then the vertical scrollbar should be moved to the other side of the window. This was not happening. Problems Addressed in the ALPDWMW01_U3012 Kit: NOTE: These problems will be fixed in the next release of DECwindows Motif after V1.2-3. Login Problems: o In DECwindows Motif V1.2-3, the DECW$LOGIN.LOG file does not include the DECwindows version number, the date and time that the log file was created, the error status returned from an XOpenDisplay failure, or a message stating that the display was successfully opened. This additional information is written to DECW$LOGIN.LOG in the remedial kit. The DECW$LOGIN.LOG file can be created by adding the following global symbol definition to SYS$MANAGER:DECW$PRIVATE_APPS_SETUP.COM and then restarting DECwindows: $ DECW$LOGINLOG == "SYS$MANAGER:DECW$LOGIN.LOG" o In DECwindows Motif V1.2-3, misleading error messages can be written to DECW$LOGIN.LOG after an exception. For example, after the user enters a bad password the following error messages are written to SYS$OUTPUT: User authorization failure error detected: non-translatable VMS error code: 0x186D4, VMS message: %RMS-F-SYN, file specification syntax error The "file specification syntax error" message has nothing to do with the actual problem, which is a user authorization failure. o In DECwindows Motif V1.2-3, remote logins often fail when the server and client are running different versions of OpenVMS, and if the DECW$LOGIN.LOG file is enabled the error message "[_XDispatchEvent - entered in reply state]" is written to the log file. For example, the remote login will fail if the client system is an Alpha system running DECwindows Motif V1.2-3 and OpenVMS Alpha V6.1 and the X11 display server is a VAXstation running OpenVMS VAX V6.1, but it would succeed if the client system were running OpenVMS Alpha V1.5. o In DECwindows Motif V1.2-3, there is a problem with "detached login failure" being periodically broadcast to the console after an unsuccessful login attempt. This is because the DECW$LOGINOUT process is restarting after it exits, even if the NORESTART flag is set in the WSA device, and because WSA devices are not being deleted. After the kit is installed, DECW$LOGINOUT will not restart if the NORESTART flag is set, and it will delete WSA devices when they are no longer needed. To prevent DECW$LOGINOUT from deleting its WSA device before exiting, define the logical name DECW$LOGIN_PRESERVE_WSA in LNM$SYSTEM_TABLE with a value of TRUE. Xm Library 1.2.3 Problems: o In DECwindows Motif V1.2-3, the XmText and XmScrolledText widgets highlight the wrong area of text when the mouse is dragged inside the text widget in the Japanese locale. When a mouse button is clicked, the insertion point is set at the wrong place. o In previous versions of DECwindows Motif, a user could activate an option menu using either the mouse or the keyboard "space" bar and then to select one of the options by using either the mouse or the keyboard. In DECwindows Motif V1.2-3, if the option menu is activated with the keyboard, the user cannot select an option using the mouse. o In DECwindows Motif V1.2-3, applications can crash when managing and unmanaging nested dialog shells. o In DECwindows Motif V1.2-3, a Motif application will terminate with an access violation if its _MOTIF_DRAG_WINDOW is deleted. In the reported case, the login box failed to come up because a server problem caused this window to be deleted. o In DECwindows Motif V1.2-3, under various conditions, it is possible to get incorrect behavior during Drag and Drop operations on multi-headed workstations. This behavior includes incorrect cursor being displayed, popup indicators shown on the wrong screen, locking the X server, and corrupted drag cursors. It is also possible to get the following error messages: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 72 (X_PutImage) X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 62 (X_CopyArea) o In DECwindows Motif V1.2-3, there is a memory leak when hashing into an occupied space. o In DECwindows Motif V1.2-3, the File Selection Box (FileSB) widget does not return the correct filename when pathMode is set to XmPATH_MODE_RELATIVE and the user enters a directory name without pressing the Apply button. o In DECwindows Motif V1.2-3, a Scrolled List widget's width is not properly adjusted when it is unmanaged using XtSetArg and XtSetValues, and then managing it again. If two Scrolled Lists are created and unmanaged, then resized by calling XtSetArg and one of them is managed again, the changed size is not reflected. o In DECwindows Motif V1.2-3, when the XmNforeground resource of either the XmText or XmTextField widget is toggled rapidly between two colors, a memory leak occurs. o In DECwindows Motif V1.2-3, under certain circumstances, two buttons in a Radio Box widget or gadget can be displayed in a depressed state at the same time. o In DECwindows Motif V1.2-3, there are two leaks in the List widget. In the first, using CopyItems() twice leaks memory because, on the second call, data is really being copied internally. In the second, the List widget's destroy method failed to remove the XmNDestroyCallback list. o In DECwindows Motif V1.2-3, it is not possible to use the return key to open an entry in the SVN widget, such as in Bookreader and in DECwindows Mail. This is inconsistent with previous versions of Motif. o In DECwindows Motif V1.2-3, DXmActivateWidget fails on pushbuttons in a menu. The application displays the following error message: X Toolkit Error: Couldn't find per display information and terminates. o In DECwindows Motif V1.2-3, a busy X server can appear to be hung when a user has attempted to post the Motif Window Manager (mwm) menu by double-clicking on the root window while alternately selecting a menu item from the Session Manager menu. The pointer tracks, but selections are not activated. Stopping and re-starting the window manager 'frees' the X server. o In DECwindows Motif V1.2-3, there is a memory leak in the cvtXmStringToText() function in the Xm library. o In DECwindows Motif V1.2-3, the X server leaks memory due to the Xm library not freeing pixmaps and because of caching problems in the Xm library. o In DECwindows Motif V1.2-3, there was a dramatic performance degradation when managing complex widget hierarchies, compared with previous versions of Motif. o In DECwindows Motif V1.2-3, pressing TAB in a window with only one tab group does not set focus to the "home" widget. o In DECwindows Motif V1.2-3, if an application calls RemoveGrab() to remove a widget while another widget is being destroyed, RemoveGrab() does not re-add the widget being destroyed onto the grab list so that it can later be removed from the grab list correctly. o In DECwindows Motif V1.2-3, some created windows are insensitive to user input. o In DECwindows Motif V1.2-3, there is a memory leak in XtSetValues() for Text widgets. o In DECwindows Motif V1.2-3, on-the-spot input does not operate correctly. o In DECwindows Motif V1.2-3, there is a problem with the Text widget, in that its handling of shifting lines up or down causes memory corruption. o In DECwindows Motif V1.2-3, the XmTextField widget leaks memory when the widget is destroyed. o In DECwindows Motif V1.2-3, an access violation occurs when an application program calls XtVaSetVValues() to set the XmNvalue resource while text is selected in an XmTextField widget. o In DECwindows Motif V1.2-3, when tearing off menus, the title of the newly created Dialog Box contains the name of option, followed by "Tear-off", written in English. For localized applications, this produces a mixture of native and English text in the Dialog Box title. For example, after tearing off the View menu from the French Calendar, the following Dialog Box title is displayed: "Visualisation Tear-off" o In DECwindows Motif V1.2-3, the performance of the string parsing in the XmTextInsert function is very poor for the Japanese and Asian locales. o In DECwindows Motif V1.2-3, when inserting one character in overstrike mode in an XmText or XmTextField widget, two characters are replaced. o In DECwindows Motif V1.2-3, when attempting to cascade to the right by dragging the mouse through a series of cascade buttons, the second cascade button sometimes arms (i.e., becomes depressed) without posting the next pulldown menu. If the cascades are posted by a series of MouseButton1 clicks they are posted correctly. The menu is also posted correctly if the user disarms the cascade by moving the mouse off of the cascade, and then drags the mouse back onto the cascade. o In DECwindows Motif V1.2-3, repeated calls to XmGetPixmap cause a BadValue error in XCopyPlane when the pixmap is updated as a background XmNlabelPixmap in a widget. The error reported is: X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 63 (X_CopyPlane) Value in failed request: 0x200 Serial number of failed request: 92 Current serial number in output stream: 93 o In DECwindows Motif V1.2-3, inserting text into an XmText widget with XmTextInsert does not correctly update the insert cursor position. The insert cursor position stays at its previous location. o In DECwindows Motif V1.2-3, when the user holds down mouse button one (MB1) and drags the pointer through a menu hierarchy, dragging the pointer into a cascade button then causes the associated submenu to be pulled down. If an item is selected in that submenu, and the pointer is dragged through the menu hierarchy with MB1 held down, the submenu can no longer be pulled down when the pointer enters the cascade button. o In DECwindows Motif V1.2-3, horizontal resize of a window forces a resize of the height of XmFrame children. In the following example, the widget hierarchy consists of: XmForm +-------------------+-------------------+ XmRowColumn XmRowColumn XmRowColumn | | | XmPushButton XmFrame XmFrame | | XmDrawingArea XmDrawingArea When the mwm resize handle is grabbed and the Form is expanded horizontally, then the XmFrame (and hence the XmDrawingArea) height decreases unexpectedly. o Several memory leaks in the DECwindows Motif V1.2-3 version of the Xm toolkit are fixed. o If an OpenVMS application running under DECwindows Motif V1.2-3 displays a File Selection Box (FSB) to an X11 display server using the Common Desktop Environment (CDE), the List boxes in the FSB will display incorrect directory and file names. o The remedial kit corrects a performance problem in the XmText widget in DECwindows Motif V1.2-3 when displaying multibyte compound strings. This problem also results in mixed single and double byte strings being displayed incorrectly. DXm Library 1.2.3 Problems: o In DECwindows Motif V1.2-3, when the help widget is displaying two topics of the same length, the first topic comes up in a few seconds. The second topic, however, can take up to two minutes to appear. o In DECwindows Motif V1.2-3, the SVN widget leaves behind parts of the highlight frame when it scrolls down past the bottom entry in a window. o In DECwindows Motif V1.2-3, when directing the SVN widget to other than the default screen (that is, if the display is set to screen 0 with the SET DISPLAY command and the application program's command line directs it to display to screen 0), then the program can fail with the following error: X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 55 (X_CreateGC) o In DECwindows Motif V1.2-3, a memory leak occurs when issuing the following series of routine calls: DXmSvnDisableDisplay followed by DXmSvnInvalidateEntry followed by DXmSvnEnableDisplay. Xt Intrinsics Library R5 Problems: o In DECwindows Motif V1.2-3, there is sometimes a five second delay in creating dialog boxes because the shell widget's geometry manager is waiting for an event that is not received. o colorConvertArgs and screenConvertArg have been added as universal symbols in DECW$XTLIBSHRR5.EXE in the remedial kit. These data structures are described in Section 9.6.4 of the book X Window System Toolkit by Asente and Swick. However, the declarations of these routines in Intrinsic.h has not been enabled for OpenVMS. A program that references these data structures will not run correctly on DECwindows Motif V1.2-3, unless the remedial kit is installed, because the addresses of the data structures within DECW$XTLIBSHRR5.EXE have changed. For this reason, programs wishing to use colorConvertArgs or screenConvertArg should either declare local copies of these data structures, which are very small and have well defined contents, or else find their addresses by calling LIB$FIND_IMAGE_SYMBOL. o _XtperDisplayList has been added as a universal symbol in DECW$XTLIBSHRR5.EXE in the remedial kit. The symbol is available for use by third party products but is unsupported and the contents of this data structure may change in future versions of DECwindows Motif. Because the location of this data structure within DECW$XTLIBSHRR5.EXE was different in previous versions of DECwindows Motif, it should be accessed by calling LIB$FIND_IMAGE_SYMBOL. Xlib Problems: o The locale support in DECwindows Motif V1.2-3 is incompatible with the support in the DEC C Run-Time Library (CRTL), so Xlib is forced to use its own limited subset of locale routines instead of using the locale support in the CRTL. o In DECwindows Motif V1.2-3, when selecting text from a text widget, e.g. in DECwindows Mail, and pasting it into another application, eight bit multinational characters are not copied. o In DECwindows Motif V1.2-3, user defined timeouts are disabled if XFlush is called after the user has disabled AST recognition. o In DECwindows Motif V1.2-3, X$GET_WINDOW_PROPERTY does not load the correct number of bytes into the calling routine's data buffer. o In DECwindows Motif V1.2-3, user defined timeouts are disabled if XFlush is called after the user has disabled AST recognition. o In DECwindows Motif V1.2-3, XReconfigureWMWindow does not trap BadMatch errors. o In DECwindows Motif V1.2-3, if too many displays are opened XOpenDisplay signals a %XLIB-W-MAXOPENDSP error but returns a non-zero value. o In DECwindows Motif V1.2-3, Xlib disables user mode ASTs on Alpha systems, even if they were previously enabled. o In DECwindows Motif V1.2-3, there are a number of Non-C bindings (X$ calls) that do not work properly. Many of them can cause an ACCVIO that is not the fault of the application developer. INSTALLATION NOTES: If you are installing this kit on OpenVMS Alpha V6.2 or later, and did not disable the use of shared linkage sections before starting DECwindows by defining the logical name DECW$IGNORE_SHARED_ADDRESS to TRUE, you will need to reboot the system after installing this kit. If you are not rebooting the system you will need to start the X11 server in order to make use of the fixes within this remedial kit. This can be done by issuing the following command after the installation is complete: @SYS$MANAGER:DECW$STARTUP RESTART [R] Motif, OSF, and OSF/Motif are registered trademarks of the Open



This patch can be found at any of these sites:

Colorado Site
Georgia Site
European Site



Files on this server are as follows:

alpdwmw02_u3012.README
alpdwmw02_u3012.CHKSUM
alpdwmw02_u3012.CVRLET_TXT
alpdwmw02_u3012.a-dcx_axpexe

privacy and legal statement