Chapter 1
About This Release

ptx/XWM V4.5.0 is the DYNIX/ptx® implementation of X Window SystemTM X11R6.4 and OSF/Motif® V2.1.10. It replaces all previous ptx/WINDOWS products.


Software Compatibility

ptx/XWM V4.5.0 requires that the following products be installed:

ptx/XWM applications can be used with any of the following X display servers:


Standards Compliance

ptx/XWM complies with the following standards:


X11R5 and Motif 1.2 Compatibility Environment

When compiling, linking, or running new applications, the new ptx/XWM X11R6 libraries are used by default. The older X11R5 and Motif 1.2 libraries are provided for runtime compatibility with older binaries. If you need to link exclusively with the older X11R5 and Motif 1.2 libraries, they are provided in /usr/X11R5/lib.

You do not need to make any changes to your environment to do the following:


ATTENTION

The -Wc,+abi-socket option can no longer be used to create a .o file.



Link an Old Object File With X11R5 Libraries

The cc option -L/usr/X11R5/lib is used to link old object files compiled using ptx/WINDOWS V4.2.x or V4.4.x with the old X11R5 and Motif 1.2 libraries.

To continue linking with old ABI+ libraries using -Wc,+abi-socket, set the environment variable __SEQUENT_CC__ to -L/usr/X11R5/lib.


ATTENTION

Do not compile new *.o object files using ptx/XWM V4.5.0 (X11R6.4 and Motif 2.1) header files and then use -L/usr/X11R5/lib to link the new binary with older ptx/WINDOWS V4.4.1 (X11R5 and Motif 1.2) libraries. The resulting binary can produce unpredictable results and is not supported. You may see warnings or errors when attempting to create this link, but such warnings and errors are not guaranteed. The -L/usr/X11R5/lib option should be used only when linking old *.o object files compiled with ptx/WINDOWS V4.2.x or V4.4.x.


The -L/usr/X11R5/lib option can be specified either on the cc command line or with the _SEQUENT_CC_ environment variable.

The valid cc command-line options are as follows:

-L/usr/X11R5/lib -Wc,+abi-socket
-L/usr/X11R5/lib -Wc,+bsd-socket

The environment variable is set as follows (the examples are for the C shell):

setenv _SEQUENT_CC_     "-L/usr/X11R5/lib -Wc,+abi-socket"
setenv _SEQUENT_CC_ "-L/usr/X11R5/lib -Wc,+bsd-socket"

We recommend that you use one of the above pairs of options/environment variables (either ABI or BSD) for linking because they use one of the following files if a compile is attempted:

Because the cc option pair specified in these files defines an illegal socket version to force a compiler error, the command-line options and environment variables described above are recommended over the single default option (-L/usr/X11R5/lib) or environment variable (setenv LD_LIBRARY_PATH /usr/X11R5/lib).

Regardless of which option/environment variable pair is used to link old (or new) *.o object files to create a binary, it is often useful to use ldd to determine to which shared libraries your binary is dynamically linking at run time:

ldd binary_name


Software Installation

Refer to the DYNIX/ptx and Layered Products Software Installation Release Notes for information about installing ptx/XWM. If ptx/WINDOWS is currently installed on your system, be sure to review the upgrade issues, described under "ptx/XWM" in Chapter 2 of the DYNIX/ptx and Layered Products Software Installation Release Notes, before you begin the installation.


Contents of the V4.5.0 Release

ptx/XWM consists of two products:

ptx/XWM
X Window System version X11R6.4 and Motif version 2.1.10 software. This software is supported by Customer Service.
ptx/XWM Contributed
Software contributed by outside developers or gleaned from the network. This unsupported software is provided as a convenience to the user.

ptx/XWM-Specific Changes to X11R6 and Motif 2.1


xdm and xterm

ptx/XWM continues to use the versions of xdm and xterm that were provided with ptx/WINDOWS V4.4.1. These versions have been customized to work properly on NUMA-Q® and Symmetry® systems.

The following xdm features were added in the X11R6 release and are not supported in ptx/XWM:

In a future release, both xdm and xterm will be replaced with X11R6 versions that include the ptx/XWM customizations.


Changes to Files and Utilities

Many files and utilities have been modified in Motif 2.1 and X11R6, as described later in these release notes. Following are some additional changes that you should be aware of:


New Icons

A new icon directory, /usr/include/X11/icons, is now available.


-DSVR4 Required for User Code

When you compile source code that includes the ptx/XWM X11 and Motif header files, you must define -DSVR4.


Changes Between X11R5 and X11R6

X11R6 includes the following new features and implementation changes:

For details about these changes, see Chapter 2.


Changes Between Motif 1.2 and Motif 2.1

Motif 2.1 contains the following new features and changes:

For details about these changes, see Chapter 3.


Port Application Source Code to Motif 2.1

Table 1-1 lists source incompatibilities that exist between Motif 1.2 and Motif 2.1. When porting source code to Motif 2.1, you must replace or remove the Motif 1.2 header files specified in the table.

Table 1-1. Motif Source Incompatibilities

Motif 1.2

Motif 2.1 Replacement

#include <Xm/ColorObj.h>

#include <Xm/ColorObjP.h>

#include <Xm/CutPasteP.h>

#include <Xm/CutPaste.h>

#include <Xm/Editres.h>

Obsolete; remove and attempt to compile

#include <Xm/WorldP.h>

Obsolete; remove and attempt to compile

#include <Xm/RCUtilsP.h>

#include <Xm/RCLayoutP.h> or #include <Xm/RCMenuP.h>



Fixed Problems

Over 800 bugs that existed in X11R5 have been fixed in the X11R6 through X11R6.4 releases.

Over 500 bugs that existed in Motif 1.2.5 have been fixed in Motif 2.1.10.


Open Problems

xman's Search Function Sometimes Fails (36418)

When you are searching for man pages with multiple topics, the Manual Page selection on the xman Options menu does not find the man page if it is not the main topic.

The Apropos selection on the xman Options menu lists all topics that share the man page. For example, the commands bitmap, bmtoa, and atobm share a man page. The main topic of the page (the topic listed in the title line) is bitmap. If atobm is entered as the search string, Manual Page does not find the man page. Apropos works correctly.

Workaround: Use Apropos to find the main topic for the man page. Then use that topic for a new search using Manual Page.

system.mwmrc Can Produce Errors (15450, 36362)

The built-in bindings and the default /usr/lib/X11/system.mwmrc file bind the f.maximize action to function key F10. On X terminals with fewer than ten function keys, the following error message appears when mwm is started:

mwm: Invalid accelerator specification on line 7
     of specification string

Workaround: Change the system.mwmrc file to map f.maximize to a key that appears on all X terminal keyboards.

mwm Death Can Result in No Keyboard Focus (37935)

When mwm is killed or dies unexpectedly, it is possible that no window will have the keyboard focus.

Workaround: To get the focus in an xterm window, move the mouse pointer to that window and press Ctrl-mouse_button-1. This brings up the xterm Main Options menu. Select Secure Keyboard from this menu to get the keyboard focus. After restarting the window manager, release the keyboard focus from that window by again selecting Secure Keyboard from the Main Options menu in that window. Or, to stop mwm without losing focus, type one of the following commands:

$ kill SIGINT mwm_pid
$ kill -1 mwm_pid

Reverse Video Problem in Toolkit Clients (43787)

The man pages for many of the toolkit clients state that when reverse video is turned on, the foreground and background are swapped. This is misleading, because if a color resource is set to something other than the default, it may not be affected by reverse video.

For example, in xterm, if the foreground is set to blue and the background is not explicitly set (the default is white), use of reverse video will result in an xterm with a black background and a blue foreground. The problem occurs no matter how reverse video is turned on (for example, with the -rv or -r command line options, or by setting the reverseVideo resource to "on" in a defaults file).

Workaround: When xterm is displayed, pop up the VT Options menu. With the pointer in the xterm window, press Ctrl-mouse_button-2 and then select the menu item Enable Reverse Video.

Known Bug in NCD Server Makes xdm Time Out (36768)

Typically xdm sends a ping packet every 5 minutes and the timeout period is five minutes. If the TELNET session or the NCD 2.4 setup window is up for more than five minutes, the NCD will not respond to the xdm ping and xdm may close the session. If it is up for more than ten minutes, xdm will close the session.

Workaround: Increase the pingInterval and pingTimeout resources. For more information, refer to the xdm(1) man page. You can also avoid losing an xdm session by setting certain X display server xdm (XDMCP) parameters. For example, for NCD X terminals, use the following parameters:

NCD 2.4:  Dead Session Detection:  Off
NCD 2.4:  Action on Failure:  Persist
NCD 3.1:  What to do when xdm disconnects:  prompt


Documentation

The following documentation is provided with ptx/XWM:

1003-71192-00
ptx/XWM Administration Guide

For a list of recommended books from other publishers and pointers to documentation available on the Internet, refer to the ptx/XWM Administration Guide.