X Window System Server Update for OS/2 TCP/IP 2.0 | Version 2.0.4g beta | 15 March 1997 | | !!!!!!!!!!! IMPORTANT NOTICE !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | | PMX has reached end-of-life. This is the last set of PMX | fixes. Use PMX 2.0.4g beta at your own risk. If there | is anything wrong with PMX 2.0.4g beta, it won't get fixed. | | PLEASE BE PREPARED TO BACK OFF PMX 2.0.4G BETA IF NECESSARY. | | The PMXFIXUP PACKAGE on OS2TOOLS now provides a PMXFXP_F.EXE | which can be used to re-install the PMX 2.0.4f beta. | | To re-install PMX 2.0.4f beta: | First enter: PMXFXP_F -o | Then enter: install | | !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! | Summary: This update REQUIRES that PMX 2.0.4 (CSD UN87312) has already been installed. This update is an incremental addition to PMX 2.0.4. It has been done this way to keep down the size of the latest fix files. See below for a list of fixes. WARNING ABOUT VERSIONS If you currently have any version before 2.0.4, or if you have version 2.0.4a, then you must get the CSD UN87312 (version 2.0.4). Note that this CSD will remove any fixes from 2.0.4a, but once you install 2.0.4b or later, you will have the fixes again. WARNING ABOUT INSTALLATION ON TCP/IP VERSIONS BEYOND 3.0 (FOR EXAMPLE, IF YOU ARE INSTALLING ON OS/2 MERLIN) If your version of TCP/IP is higher than 3.0, and either (1) you are installing PMX for the first time and it is the "refresh" version 2.0.4 (with CSD UN87312 included) or (2) you are installing the CSD UN87312, then you will need a fix that is supplied with this package. See the file PN83992.DOC for more information. ---------------------------------------------------------------------- INSTALLATION ---------------------------------------------------------------------- The OS/2 TCP/IP X Window System Server 2.0 must already be installed. Also CSD UN87312 must have been installed (PMX version 2.0.4). This version is an incremental addition to version 2.0.4, and contains all changes to PMX since version 2.0.4. This set of fixes is distributed as two files on the OS2TOOLS conference disk. The files are PMXFIXUP PACKAGE and PMXFIXUP EXEBIN. The package file has instructions on installation. Typically PMXFIXUP EXEBIN is downloaded in binary mode, to be named pmxfixup.exe. It is a self-expanding file, that becomes several files, including the one that you are reading. Typically you will run the install.cmd file to install the fixes. INSTALLATION WARNING! If PMX is running, it must be stopped before doing the update. Also after the update is complete, OS/2 must be shut down and rebooted in order to run PMX. INSTALLATION WITH NO PROMPTS Some users have a need to install with no prompting from the install command. Typically this is when installing to a lot of machines over a network. To install without prompting, run install with one or more of the following options on the install command. Only the options specified will be done. The options may be specified in any order on the command line, but will be done in the order shown below. -installfixes Install PMX fixes, backing up certain files such as fonts.ali or xinit.cmd -deletesnf Delete old *.snf font files in the \tcpip\x11\misc and \tcpip\x11\75dpi directories. -deletejapanese Delete certain Japanese fonts, to save space. -deletekorean Delete certain Korean fonts, to save space. Example: install -deletejapanese -installfixes This installs the fixes, and then deletes the Japanese fonts, if there are any to delete. If there are Korean fonts or old SNF fonts, they are not deleted. ---------------------------------------------------------------------- HARDWARE DEPENDENCIES ---------------------------------------------------------------------- If you experience traps or hangs, very often the source is the video driver. You may need to get the latest video driver for your video adaptor. Some specific examples are given below. In general, you can obtain recent drivers from either the manufacturer of the adaptor, or from IBM. You can ftp on the Internet to software.boulder.ibm.com, user id "anonymous", your network address as the password, and then go to the directory ps/products/os2/drivers/video. If you have a Web browser, use ftp://service.boulder.ibm.com/ps/products/os2/drivers/video as your URL. ATI Mach32 Video Controllers: Various TRAPs have been reported to PMX on OS/2 machines with video cards using the ATI mach32 chipset, during the beta test of UN68122 CSD. These problems were resolved by upgrading the OS/2 device drivers to the latest version available from ATI. Retrieve and apply these files: M32v85.ZIP - "ATI mach32 release 2.4 OS/2 2.11 Display Driver v.85a" ATILDR11.ZIP - "Loader/install code for above device driver." These files can be retrieved from Internet ftp: os2.nmsu.edu (Hobbes) ftp-os2.cdrom.com (Walnut Creek) Compuserve: Go ATITECH Contact ATI Corp for more information, if necessary. A trap in the CIRRUS SVGA device driver has been reported. It happens only when the user chooses pseudocolor with realizable color tables. Instead, the user should use either static color or pseudocolor with pallete manager support. ---------------------------------------------------------------------- PALETTE MANAGER WARNING!!! ---------------------------------------------------------------------- This version of PMX works better with most PM device drivers, in palette manager pseudocolor mode. If you had problems with previous PMX Betas, and were using either the -drawpalcolors or -bbonocolor flags, please DO NOT USE them. They no longer have the effect that they had before. ---------------------------------------------------------------------- Fixes since the release of PMX 2.0 ---------------------------------------------------------------------- | Release 2.0.4g beta - February 15, 1997 | (requires CSD UN87312) | | (1) Defect 18478: Use program specified window size in the Size Hints | window property if the initial window size is too small or too large. | This will fix situations in NetView/6000 where dialog windows appear | with only a small title bar. | | (2) Defect 20569: -palette 129..192 broken on some PM display drivers, | causing incorrect colors in PMX X application windows. PMX now | automatically adjusts the "-palette xxx" settings if it detects | these types of PM device drivers. | | (3) Defect 21234: Prevent PMX thread 1 from overwriting data areas if | there is a program loop in PMMERGE.DLL. This will lead to cleaner | diagnostic information when/if PMX traps. | | (4) Defect 21235: ALLOCATE_LOCAL should use heap memory if stack is full. | This will keep PMX from trapping when zooming in on graphic details | in CAD-CAM type X applications. | | (5) Defect 21236: PMX should have a flag which treats width 1 lines as width 0. | There is a new PMX command line flag "-fastlineW1" which speeds up | ----------- | CAD-CAM type X applications, which typically draw numerous width 1 | lines. Line width 0 lines can be drawn much faster, with perhaps | a slight degradation in the image quality. | | (6) Defect 21362: Fixes / Enhancements to XSCOPE; new -t "terse" flag; | XSCOPE was not printing ChangeProperty requests properly. | Also there is a new "-t" command line flag which provides a much | more compact output format for trace details. | xscope -v3 -- non-compact output of all details | xscope -t -v3 -- trace with moderate amount of detail | xscope -t -v4 -- trace of QueryFontReply font properties | xscope -t -v5 -- compact trace of x,y coords of Poly requests | xscope -t -v6 -- compact trace of QueryFontReply character metrics | and GetKeyboardMappingReply | | (7) Defect 21362: "xfd -fn lutRS10" causes PMX to hang | There was a font "alias loop" in %XFILES%\75dpi\fonts.ali. | | (8) Defect 22532: "fakereparent" should default to ON instead of OFF. | A number of X application toolkits assume the presence of an X-based | Window Manager that will reparent a top-level window at MapWindow | time. The X app waits for a ReparentNotify event before continuing. | PMX will now send this ReparentNotify event by default. If this | event causes problems with other X apps, there is a new | "-fakereparentoff" flag which halts the sending of ReparentNotify. | | (9) Defect 24318: "Trap in VGA 16 color mode when IBMS332.DLL is present." | PMX now uses OS2.INI instead of the presence of IBMS332.DLL to | determine if an S3 driver is currently being used. | | (10) Defect 18609: "combo.dll missing when viewing PMX.INF." | On Merlin (OS/2 version 4.0), the TCP/IP base does not include | combo.dll; PMXFIXUP now installs a combo.dll. ---------------------------------------------------------------------- Release 2.0.4f beta - September 9, 1996 (requires CSD UN87312) (1) Defect 15120: No undo of button swap of 2 and 3 in Merlin. (2) Defect 15234: Incorrect log path in notebook causes misleading message about -logpath operand. (3) Defect 15753: Program around bug in WinSetWindowPos mainly affecting iconify and restore of client window icons. (4) Defect 16906: Sometimes focus did not go to the top X window when another window went away. ---------------------------------------------------------------------- Release 2.0.4e beta - July 11, 1996 (requires CSD UN87312) (1) Defect 13280: Windows have corrupted regions on OS/2 Merlin Beta. (2) APAR PN85920: Visualizer 1.2 color not remembered correctly. (3) APAR PN86586: Child title incorrectly used in parent window. ---------------------------------------------------------------------- Release 2.0.4d beta - May 28, 1996 (requires CSD UN87312) (1) Defect 13251: Fix to protect against WM_HINTS or WM_NORMAL_HINTS property that is not the right size, or has zero length data. (2) APAR PN81511: Capslock/Shiftlock keys and lights not in sync for a German keyboard. This fix requires three things: Warp Fixpak 6 or higher must be installed, a German keyboard or one that acts similarly must be in use, and PMX must have the -shiftunlockcapslock command line flag. If you use this flag without the other two requirements, the capslock state and the capslock light may become unsynchronized. (3) APAR PN82580: Trap D while drawing wide arcs, finally fixed. (4) APAR PN83992: SYS3175 trap installing CSD/Refresh on unknown SYSLEVEL.TCP. (No code change to PMX, just to PMXXT.EXE which is used during install of GA code.) (5) APAR PN84227: Update of icon title while not iconic, changed the window title instead. (6) Defect R104731: HUGE cut/paste using CLIPBOARD selection traps PMX. ---------------------------------------------------------------------- Release 2.0.4c beta - April 2, 1996 (requires CSD UN87312) (1) R104731 Fixed some cut/paste traps with very large sizes. (2) 10367 Fixed an error popup that happens sometimes when closing windows. (3) 10468 Added validity check when highlighting window. This fixed an error popup. (4) 11136 Added -force2buttons flag, to get around Thinkpad 750P pen bug, where it reports 3 buttons even if there are only 2 for the mouse. If you really have a 3-button mouse installed, it will work, but if you have a two button mouse or just the pen or trackpoint and the built-in buttons on the keyboard, then PM reporting 3 buttons will prevent PMX from properly simulating the middle button by pressing the two button simultaneously. Use the -force2buttons parameter with the PMX or XINIT command. We think the bug only happens if the pen drivers are installed, but have not verified this. (5) Added -2buttontime n command line flag (n is 200 by default), to allow setting of timer to check if the left and right buttons are pushed close enough together to simulate a middle button. (6) APAR PN82680 Trap when using certain fonts from a font server. (7) APAR PN82957 Netview control desk drag problem is fixed. ---------------------------------------------------------------------- Release 2.0.4b beta - March 8, 1996 (requires CSD UN87312) (1) Fixed and enabled window icon support. If applications provide either bitmap or window icons they are automatically supported, provided that X windows iconify to the desktop. They are not supported if they iconify to the minimized window viewer. The windows iconify to the same place that the PMX server window is iconified to. (2) Fixed a problem with Netview mapping an iconic window. The symptom was to see a PM frame but no window painted in the frame, in some instances. (3) PN75550: A fix for the PN75550 fix below. The control desk for Netview did not draw correctly. (4) bitmap cache speedup. Some speedups will happen if bitmaps are used to describe the region to draw in. (5) (APAR PN80478) -sokeepalive flag on the PMX command line turns on the keepalive socket function for PMX sockets. Few users will care about this function. (6) The fixes from 2.0.4a are also in this version, of course. ---------------------------------------------------------------------- Release 2.0.4 - CSD UN87312 - March 6, 1996 The content of this CSD is the same as release 2.0.3q, except for version number and such things as the README.PMX file. ---------------------------------------------------------------------- Release 2.0.4a beta - February 6, 1996 (required CSD UN68122) (1) (APAR PN79902) Fix for "cursor hogging the CPU" problem. (2) (APAR PN80101) PMX corrupts OS/2 window list, finally fixed! (3) (APAR PN75550) "Slow icon" problem (slow CopyPlane, actually). ---------------------------------------------------------------------- Release 2.0.3q beta - November 21, 1995 (1) Fixes for new client icon code introduced in 2.0.3p. (2) Some drawing fixes. (3) Fixes for several traps. (4) More Z order fixes for Netview and Product Manager. (5) Num Lock and Caps Lock state changes now recognized when done while PMX does not have focus. (6) Fixed font compiler error for certain font names. (7) DHCP support is available in this version of PMX, for control of fontpath and XDMCP parameters. ---------------------------------------------------------------------- Release 2.0.3p beta - October 20, 1995 (1) The CapsLock and NumLock X states now gets synchronized with the PM state whenever PMX receives window focus back from PM. PMX no longer loses track of CapsLock and NumLock keyboard state. (2) Fix for an NV6000 problem with separating the Control Desk window on a slow machine. (3) Partial support for client bitmap icons is supplied. There are cases where the default PMX icon will still be displayed instead. This depends upon when the WM_HINTS property is put on the window. Client window icons are not supported yet. ---------------------------------------------------------------------- Release 2.0.3o (This version was skipped to avoid confusion between "o" and "0".) ---------------------------------------------------------------------- Release 2.0.3n test fix (This version has been sent to a few customers.) (1) A fix for "circulate properties" which might help with the circulation of cut buffers. It now works with xcb, so it might fix cut and paste problems with ATK applications. (2) Fix for Netscape animated logo not being shown. (3) New XDMCP page in settings notebook. (4) DHCP enablement for Fontpath and XDMCP flags. (5) The documented "-shape" flag has been implemented. It turns the shape extension off. (6) Fix for the PINE text background problems when it is run in an aixterm window. ---------------------------------------------------------------------- Release 2.0.3m beta - August 17, 1995 (1) A problem was introduced in 2.0.3L with colored cursors on machines with 16 colors. It is fixed in this version. (2) A problem was introduced in 2.0.3L for windows that are initially an icon. The PM window was drawn as if at one location on the screen, while the PM window (after restoring the window from the icon) was at a different location. The result was that the X window was only partly visible inside the PM frame. This is now fixed in this version. ---------------------------------------------------------------------- Release 2.0.3L beta - August 15, 1995 (1) Fix for a z-order problem that was not fixed with 2.0.3j. (2) Added -forcealways and -forcewm flags for backing store. These say to completely ignore the application's backing store request, and set Always or WhenMapped on all windows. The -forcealways option is useful when running PMX over a slow connection, so that windows will rarely need repainting. The -forcewm options is mostly available for completeness, but could be used to evaluate the effects of the WhenMapped backing store option without having to set it in an X application. (3) Fix for client resizing a window while it is iconic (a particular situation with the latest Netview/6000). (4) Fix for tiled borders of menus. An example was the AIXterm menus. (5) More fixes for cut and paste. (6) More possible values for the LANG environment variable are recognized, including XPG4 style of values. (7) Fixes for cursors. Transparent areas are now correct on some display adaptors, and hot spot computation is fixed for some large cursors specified by some X programs, such as Pro Cadam. ---------------------------------------------------------------------- Release 2.0.3k test fix (This version has been sent to a few customers.) ---------------------------------------------------------------------- Release 2.0.3j beta - July 7, 1995 (1) A number of cut-and-paste problems have been fixed. (2) The keyboard page of the configuration notebook now will show the correct language setting based on PMX.INI file settings. This fixes APAR PN72900. (3) It has been determined that a few PM device drivers do not do pattern drawing properly, and this can affect correctness of drawing in a few instances. Use the PMX command line flag "-nopmpatterns" to tell PMX to not use patterns in drawing. (4) Xscope has been fixed to output negative numbers in certain cases. Also a bug in display of sequence numbers has been fixed. (5) Corrected UK and Turkish keyboard files are included. (6) Some fixes have been made in the scanning and displaying of non-English window titles. (7) A fix was made to properly handle negative values passed in the bell request. PMX rejected them when it should not. The fix also corrected three failures of the X test suite. (8) Fixes have been added to the handling of Z order of windows when they are newly displayed. Also some X applications attempted to move their main windows above their dialog boxes for those windows. PMX now prevents this, similarly to the Motif Window Manager. (9) PMX now makes a transient_for window (typically a dialog box) become the top window when it is made visible (mapped). (10) When a non-menu window is made visible (mapped) and it will be given focus by PMX, PMX makes the window become the top window, if PMX is in explicit mode (click to focus mode). The -raiseonmapandfocus command line flag turns this behavior on (default), and -noraiseonmapandfocus turns it off. (11) A new command line flag "-raiseonmap" has been provided to force all non-menu windows to the top when they are first mapped (made visible). The flag "-noraiseonmap" turns this behavior off, and is the default. It is recommended that "-raiseonmap" not be used, especially if you run X applications that normally should be below other windows, such as xfish. The other Z order fixes mentioned above have generally made this flag not necessary. ---------------------------------------------------------------------- Release 2.0.3i beta - June 27, 1995 Release 2.0.3h beta - June 15, 1995 Release 2.0.3g beta - May 18, 1995 (These versions have been sent to a few customers.) ---------------------------------------------------------------------- Release 2.0.3f beta - May 9, 1995 (1) A trap in the configuration notebook was fixed. (2) A change was made so that transient_for (dialog box) windows are not cascaded, but instead are placed exactly where the application puts them. ---------------------------------------------------------------------- Release 2.0.3e beta - April 6, 1995 (versions 2.0.3a to 2.0.3d were only sent to a few persons) (1) Add -nofocusonmap flag. If used, PMX will not set focus on a window when it is mapped, when the convention normally would be to set the focus. (2) Add -nogpiimagetext flag to keep from trapping on MXGA (multipleXGA). (3) Major fix for PMX traps caused by client connections breaking. (4) Fix for Speedo font hangs. (5) Fix for iconic window; unmap did not hide the PM icon. Also fixes to remove unmapped window from window list. (6) Fixed handling of WM_SIZE_HINTS property for minimum and maximum window sizes. (7) Fixed Z order problem. Transient windows are kept in front by default. -wmgrzorderoff gets back old behavior. (8) -auth <.XAuthority-file> and xauth utility now work. xauth.exe is included in this package. A more complete writeup will be made available later. (9) Fix to not bypass GpiImage() by default. Use the -nogpiimagetext flag to bypass GpiImage() hangs (e.g. Cirrus Logic 5426). (10) Fixes for moving and resizing child windows of top level windows. ---------------------------------------------------------------------- Release 2.0.3 - CSD UN68122 - 1995 February 17 Summary for PMX 2.0.3: This update contains Corrective Service Diskettes UN52841, UN60006, and UN68122 for PMX 2.0. It is the same code as CSD UN68122. It contains many fixes since the last CSD, including color support, focus, cut and paste, ... and, native PM font support for dramatic increases in text speed! !!!!!!!!!!!!!!!!!!!!!!!!!! !!! PM Fonts WARNING !!! !!!!!!!!!!!!!!!!!!!!!!!!!! PMX 2.0.3 can use native PM fonts in order to significantly speed up text writing. Installing level 2.0.3 of PMXFIX2 PACKAGE will backup your existing PMX .PCF fonts and install new PMX PM (.XFN) fonts in the \tcpip\x11\misc and \tcpip\x11\75dpi font subdirectories. (So will installation of that version from the official CSD diskettes.) PLEASE READ item (1) of the 2.0.3 notes to understand the IMPLICATIONS of this MAJOR PMX change. For instance, you will need about 3.5 MB of free DASD space for these new fonts. In some cases you may still need the old fonts, if your application asks for a font that PMX has, but scaled to a different size. The slower .PCF fonts can be scaled, but the faster .XFN fonts are not scalable. ADDITIONAL WARNING!!! If you have compiled any of your own X fonts into PM fonts, using previous versions of BDFTOPM previous to PMX 2.0.3, you MUST compile them again, since our version of the PM font format has changed a bit. (1) !!! PMX 2.0.3 ships and uses native PM fonts !!!. Contents of this item: ...................... 1.1 Installation of PMX PM fonts 1.2 New PMX utility commands and programs: 1.2.1 BDFTOPM.EXE 1.2.2 PCFTOPM.EXE 1.2.3 MKFONTDR.EXE 1.2.4 ERASEPCF.CMD 1.2.5 RESETPCF.CMD 1.3 SVGA and ImageAdapter bugs: 1.4 The .XFN PM font format 1.5 Using PM Public Fonts with PMX 1.1 Installation of PMX PM fonts -------------------------------- During the PMXFIX2 installation, your current .PCF fonts in \tcpip\x11\misc and \tcpip\x11\75dpi will be backed up to directories \tcpip\x11\miscPCF and \tcpip\x11\75dpiPCF. NOTE: In order to install PMXFIX2 2.0.3 and have room for the new .XFN fonts, you will need about 3.5 MB of free DASD space on the disk partition containing the \tcpip tree. The new PMX PM fonts have an .XFN filename extension, and will be loaded into \tcpip\x11\misc and \tcpip\x11\75dpi. If the DBCS PMX .PCF fonts are found during the installation, they will be kept in the \tcpip\x11\misc directory, and will still be available to X clients. NOTE: The PMX .XFN format does not handle DBCS fonts; please continue to use .PCF format for these fonts which have more than 256 characters. NOTE: The installation routine does not detect any .PCF fonts that you may have added to the \tcpip\x11\misc or \tcpip\x11\75dpi subdirectories. These additional fonts will be saved in the \tcpip\x11\miscPCF and \tcpip\x11\75dpiPCF subdirectories. It will be best to create a separate font subdirectory for any additional fonts that do not come with PMX so that this problem does not reccur during future PMX updates. You have two choices for re-installing these additional fonts. A) Just copy the additional .PCF fonts: md \tcpip\x11\pvtfonts cd \tcpip\x11\pvtfonts copy \tcpip\x11\miscPCF\private1.pcf copy \tcpip\x11\miscPCF\private2.pcf mkfontdr B) Convert these additional fonts to .XFN format: md \tcpip\x11\pvtfonts cd \tcpip\x11\pvtfonts pcftopm -o private1.xfn \tcpip\x11\miscPCF\private1.pcf pcftopm -o private2.xfn \tcpip\x11\miscPCF\private2.pcf mkfontdr Be sure to open the TCPIPCFG configuration notebook and add the new \tcpip\x11\pvtfonts subdirectory to your PMX font path. WARNING: It is possible to have "missing font" indications with the new fonts, where it did not happen with the old fonts. In some cases, an X application can ask for a specific font but specify that it will be scaled to a different size. The .PCF fonts can be scaled by PMX, but the new .XFN fonts cannot. Thus to satisfy such a request, it will be necessary to still include the miscPCF or 75dpiPCF directories after the misc and 75dpi directories on the font path, or else it will be necessary to include a font server in the font path that can satisfy the request. 1.2 New PMX utility commands and programs: ------------------------------------------ 1.2.1 BDFTOPM.EXE -- converts an ASCII .BDF font into a PM .XFN font: ................. command format: bdftopm -o newfont.xfn newfont.bdf Note that the ".xfn" extension, in lower case letters, is required. bdftopm does not write an .xfn font to stdout, like bdftopcf does. Be sure to move the .bdf font to a different directory than the .xfn font before you run mkfontdr. See the note for mkfontdr below. 1.2.2 PCFTOPM.EXE -- converts an binary .PCF font into a PM .XFN font: ................. command format: pcftopm -o newfont.xfn newfont.pcf Note that the ".xfn" extension, in lower case letters, is required. pcftopm does not write an .xfn font to stdout, like bdftopcf does. 1.2.3 MKFONTDR.EXE -- creates a font directory file (fonts.dir) .................. command format: mkfontdr [font_subdirectory_path] mkfontdr now recognizes .xfn fonts when creating a fonts.dir file in a font subdirectory. The font_subdirectory_path is optional; the default subdirectory is the current directory. NOTE: mkfontdr wants all of the fonts in a subdirectory to be unique. Be sure, after you convert .BDF or .PCF fonts to .XFN format, that you remove those original .BDF or .PCF fonts from the subdirectory before you run mkfontdr. Otherwise, mkfontdr will give an error message about duplicate fonts. A font subdirectory can contain a mix of .XFN and .PCF fonts as long as each font is unique. command format: mkfontdr -pmpublic This is a special form of mkfontdr which creates a fonts.dir file for the publically available PM fonts. The fonts.dir file is stored in the subdirectory pointed to by the ETC environment variable. In order to use these PM public fonts with PMX, use the PMX font path "pmpublic\", eg: on the pmx command line: pmx -fp d:\tcpip\x11\misc,pmpublic\,tcp\aixfontserv:7500 or opening up the TCPICFG configuration notebook, going to the PMX Font page, and entering into the font path field: d:\tcpip\x11\misc,pmpublic\,tcp\aixfontserv:7500 or else using the xset utility after pmx is running: xset +fp pmpublic\ 1.2.4 ERASEPCF.CMD -- Deletes the old .PCF fonts .................. During PMXFIX2 2.0.3 installation, the old .PCF fonts were saved in \tcpip\x11\miscPCF and \tcpip\x11\75dpiPCF. If you are satisfied with the new .XFN fonts on your system and wish to reclaim the disk space taken up by the .PCF fonts, run this erasepcf.cmd. NOTE: A .XFN font file has a smaller size than the corresponding .PCF font file. However, you may need to keep the old fonts. See the warning in section 1.1 above. 1.2.5 RESETPCF.CMD -- Deletes new .XFN fonts and restores .PCF fonts .................. If you encounter problems with the new .XFN fonts and wish to return to the old .PCF fonts, use the resetpcf.cmd. The .XFN fonts installed in \tcpip\x11\misc and \tcpip\x11\75dpi will be erased and the .PCF fonts saved in \tcpip\x11\miscPCF and \tcpip\x11\75dpiPCF will be restored to their original subdirectories. Any DBCS .PCF fonts that were moved during installation will not be erased, but will also be placed back in their original subdirectory. 1.3 SVGA and ImageAdapter bugs: ------------------------------- NOTE: We encountered problems with SVGA and ImageAdapter PM device drivers when using Type 3 PM fonts -- they cause PMX to trap inside a GpiCharStringAt() call. Type 3 PM fonts have individual a-space, b-space, and c-space measurements per character. This types of font may not have been widely used in OS/2, but quite a few X fonts mapped into Type 3 PM fonts. We have reported this problem to OS/2 Video Support in Boca. As a work-around, when we open a Type 3 font on SVGA or ImageAdapter, PMX will treat that font like a .PCF font. The font will work, but will not be any faster than the current .PCF PMX fonts. Type 1 PM fonts, which are fixed width fonts, work OK on all PM device drivers. This means that your aixterm windows will be speeded up on all platforms. All PM fonts seem to work OK on XGA, S3, and 8514 PM device drivers. 1.4 The .XFN PM font format --------------------------- .XFN font files are actually OS/2 DLLs that contain one PM bitmap font resource along with additional resources that describe the original .BDF or .PCF X font. PMX loads each .XFN DLL as a private PM font whenever an X client opens that font. PMX unloads the .XFN DLL after the X client closes the font. One important difference between .XFN and .PCF fonts is that PMX is able to scale .PCF bitmap fonts in order to fulfill some OpenFont requests for non-existent .PCF fonts. Since .XFN fonts are loaded directly into PM, and PM does not support scaling of bitmap fonts, .XFN fonts will not be scaled. If your X application requires scaled fonts, continue to use the necessary .PCF fonts, or else substitute scalable PM Public fonts. 1.5 Using PM Public Fonts with PMX ---------------------------------- OS/2 PM comes with a good variety of bitmap and scalable fonts. Installing word processor or graphics editing packages on OS/2 usually adds more PM Public fonts that can be used by any PM application on your OS/2 system. PMX allows X applications the use of all these PM Public fonts when "pmpublic\" is added to the PMX font path. Since the contents of the PM Public font list is subject to change, PMX creates a fresh list of public fonts each time "pmpublic\" is activated. It does this by running "mkfontdr -pmpublic" as a child process. "mkfontdr -pmpublic" creates a fonts.dir file in the subdirectory pointed to by the ETC environment variable. NOTE: PMX assumes that the ETC environment variable points to a disk subdirectory for which your machine has file creation and file writing permission. "pmpublic\" is not automatically added to your PMX font path during PMXFIX2 installation. PM does not support the font code page ISO8859-1 that many X clients request. PMX solves this problem by translating ISO8859-1 strings to the code page 850 strings that PM can handle. Most PM Public fonts occur two times in the fonts.dir file, once for code page ISO8859-1 and again for code page IBM-850. NOTE: PMX will also use a fonts.ali file if it is found in the same ETC subdirectory with the fonts.dir file for the PM Public fonts. PMX does not ship a fonts.ali file for PM Public fonts. Here is a sample fonts.dir entries made for a PM Public bitmap font: System VIO.pmx -ibmos2-"System VIO"-medium-r-normal--26-160-120-120-c-120-iso8859-1 System VIO.pmx -ibmos2-"System VIO"-medium-r-normal--28-170-120-120-c-120-ibm-850 And an example of entries made for a scalable PM Public font: Helvetica Italic.pmx -adobe-Helvetica-medium-i-normal--0-0-0-0-p-0-ibm-850 Helvetica Italic.pmx -adobe-Helvetica-medium-i-normal--0-0-0-0-p-0-iso8859-1 An example of using this scalable font: ... after pmx has been started xset +fp pmpublic\ xfd -fn -adobe-Helvetica-medium-i-normal--0-2000-75-75-p-0-iso8859-1 ... this will create a big 200 point font in which each character is about 200 pixels high! Note: X requires that a scaled font request contain 14 dashes! Tip: This XFD window will be much larger than your display screen. Use the PM Alt-F7 key sequence and mouse movement in order to move this window around. NOTE: Some scalable PM Public fonts are kerned, which means that the appearance of text cannot be reliably predicted by the X application. (2) Fixes to help information and to configuration notebook. (3) Other minor fixes. ---------------------------------------------------------------------- Release 2.0.2q beta - 1994 December 6 (1) Fix of extraneous text dots seen on SVGA, and related hangs and traps. (2) Fix for IDRAW text ADDITIONAL WARNING!!! If you have compiled any of your own X fonts into PM fonts, using previous versions of BDFTOPM, you MUST compile them again, since our version of the PM font format has changed a bit. ---------------------------------------------------------------------- Release 2.0.2p beta - Interim version not widely distributed. ---------------------------------------------------------------------- Release 2.0.2o beta - Interim version not widely distributed. ---------------------------------------------------------------------- Release 2.0.2n beta - 1994 November 16 (1) A fix was made that affected cut and paste problems and some other less widely reported problems. (2) A bug in painting menus and possibly other things, introduced since 2.0.2i, was fixed. (3) A problem where a window started iconified, then was maximized, then restored, was fixed. (4) A palette manager pseudocolor problem was fixed. ---------------------------------------------------------------------- Release 2.0.2m beta - 1994 November 14 (1) More drawing fixes, some especially affecting S3 and 8514. (2) Fixes for atom handling. (3) Fixes for server resetting. A server reset will occur automatically if you have -resetpmx on the command line of PMX or XINIT, and the last application that was running has ended. The default behavior of PMX is to not reset. (Server resetting typically means that atoms and properties are deleted, and such like.) ---------------------------------------------------------------------- Release 2.0.2L beta - Interim version not widely distributed. ---------------------------------------------------------------------- Release 2.0.2k beta - 1994 November 4 (1) More drawing fixes. (2) Fixes for atom handling. ---------------------------------------------------------------------- Release 2.0.2j beta - Interim version -- Not distributed ---------------------------------------------------------------------- Release 2.0.2i beta - 1994 November 1 (1) Updated ALLFONTS.CMD. The REXX utility ALLFONTS allows the user to convert all BDF and/or PCF fonts in the current directory to XFN fonts (PM Private format). See \tcpip\doc\readme.pmx. (2) Fixes for PM drawing problems when using various Boolean combination functions. ---------------------------------------------------------------------- Release 2.0.2h beta - 1994 October 26 (1) Fixes to use the right drawing routines for VGA and Image Adaptor. (2) Fixes to mkfontdr to work right in FAT file systems. ---------------------------------------------------------------------- Release 2.0.2g beta - 1994 October 24 (1) !!! PMX 2.0.2g ships and uses native PM fonts !!!. The writeup for PM fonts was moved to the 2.0.3 description. (2) GREHOOK.DLL no longer attempts to display a banner during OS/2 boot. This will fix two problems that have been reported: A) The S3 "black cursor" problem; on S3 PM device drivers, the PM cursor is all black right after OS/2 boot. B) Extraneous beeps sounded and garbage characters displayed on the screen during OS/2 boot. (3) PMX keyboard flag "-k 124" has been implemented. The PMX documentation states that "-k 124" can be used to inform PMX that a 124 key Japanese keyboard is being used, but PMX would not accept that flag value. PMX 2.0.2g now will accept "-k 124" as documented. (4) A fix was made for a PMX socket problem whose symptom was that INETD would stop running. (5) Fixes were made to the focus setting behavior of PMX. PMX no longer grabs focus from another (non-PMX) window, when it is started, provided -nocopyright is on the command line, or the configuration notebook is set up to not display the copyright window on PMX startup. When PMX has focus on any of its X windows, if a new window is displayed, focus is transfered to that window according to ICCCM rules. This fixes some focus problems in this area. Also PMX no longer grabs focus from non-X windows when an X application displays a dialog box. (6) The WM_STATE property is put on non-override-redirect windows. This means that a few programs that look for this property in order to find their top level window, will now work. ---------------------------------------------------------------------- Release 2.0.2f beta - Interim version -- Not distributed ---------------------------------------------------------------------- Release 2.0.2e beta - Interim version -- Not distributed ---------------------------------------------------------------------- Release 2.0.2d beta - 1994 August 26 -- Limited distribution (1) Speedups for grayed out text were added. ---------------------------------------------------------------------- Release 2.0.2c beta - 1994 August 23 (1) A fix was added to have a correct time stamp for mouse movements. This may fix some cut and paste problems. (2) The appropriate X cursor is displayed when the pointer is over an X window, even if PMX does not have PM focus. This is closer to the usual behavior of both X and PM programs. ---------------------------------------------------------------------- Release 2.0.2b beta - 1994 August 11 (1) Backing store support is included. It is normally on, but can be turned off with the -bs flag. See the PMX help for information on other flags: -always, -fakebackingstore, and -wm. (2) A rare problem was fixed where mouse clicks were sometimes delivered with very incorrect location information. This affected a few X applications for drag and drop or cut and paste. This version number was distributed to only a few persons. ---------------------------------------------------------------------- Release 2.0.2a beta - 1994 July/August This version number was distributed to only a few persons. ---------------------------------------------------------------------- Release 2.0.1p beta - 1994 July 26 This is a beta version of CSD UN60006 (1) During PMX initialization, PMX no longer hangs the OS/2 system when the following environment variables are not defined: XFILES, ETC, HOSTNAME, PATH, DISPLAY Also, only XFILES and ETC are required for PMX initialization to succeed; the others will be printed in PMX.LOG if they are set in the environment. (2) Fix for background PMX windows which an X client reshapes. An example is "xv *.gif &" when PMX is running in implicit focus mode and the key is hit to cause xv to show the next GIF file. The bug caused the reshaped window to have holes if there were any other PMX windows above it. (3) Code that allows PMX Palette Manager mode to better adapt to the number of default PM desktop colors in newer PM display drivers. (4) Focus loop fix: It was possible to cause PMX focus to continuously cycle among several OpenLook windows when PMX was in implicit focus mode. (5) Icon titles have been corrected. Window titles and icon titles should no longer get mixed. ---------------------------------------------------------------------- Release 2.0.1o beta - 1994 June 27 This is a beta version of CSD UN60006 (1) When running PMX in PseudoColor mode, either -pseudo or -palette, clicking on any non-PMX window will restore the original PM desktop colors so that non-PMX windows should look OK. (2) PMX recognizes "SET VIDEO_DEVICES=VIO_MGA" in config.sys for the Japanese MGA video adapter and automatically uses the correct PM line drawing routines. ---------------------------------------------------------------------- Release 2.0.1n beta - 1994 June 15 This is a beta version of CSD UN60006 (1) More text speedups! This should be noticable in AIXTERM and XTERM windows. (2) Fixed: PolySegment line drawing on ImageAdapters. You should now be able to see the highlighted edges on Motif applications and Info Explorer panels. (3) PseudoColor using Palette Manager should work better on ImageAdapter and SVGA machines. X color cursors should now work OK. (4) Unecessary repainting of windows has been suppressed in Palette Manager PseudColor mode. (5) There is an OS/2 Video APAR PJ14368 opened for the following: There is a PM Palette Manager bug which prevents PMX from changing 4 of the 256 colors when an X application obtains a private PseudoColor colormap. This bug is most noticeable in X image viewing applications, such as XLOADIMAGE. There will be four blue-ish or gray-ish colors present which do not belong in the picture. The only work-around is to run PMX in Realizeable Colortable PseudoColor mode. Code has been added to PMX to automatically detect and use the PM fix, when it is made available by OS/2 PM at a later date. ---------------------------------------------------------------------- Release 2.0.1m beta - 1994 June 8 This is a beta version of CSD UN60006 (1) Fixed: Text and background colors bad when running in 16 color mode. (2) Fixed: Bad colors when running in PMX Palette Manager mode on non-XGA display adapters. (3) EXPERIMENTAL: PMX accepts a "-gpiglyphblt" flag which speeds up shaded or grayed-out text. The results do not look too good on XGA due to a suspected PM device driver problem. We have not yet tested with this flag on other PM device drivers, and would appreciate hearing back on the OS2X FORUM if the resulting shaded text looks OK. This flag may be removed in future versions of PMX Beta. (4) Fixed: CorelDraw causes PMX to trap because it alters a bitmap that is being used as a tiling pattern. ---------------------------------------------------------------------- Release 2.0.1L beta - 1994 June 8 NOTE: This Beta level of PMX was immediately replaced with PMX 2.0.1m beta due to a PMXWAIT problem, and the addition of a fix for CorelDraw(tm). ---------------------------------------------------------------------- Release 2.0.1k beta - 1994 June 1 This is a beta version of CSD UN60006 (1) Fixes are made to text drawing, and somewhat speeded up for solid colors, especially for black and white text. (2) Changes have been made to focus handling. "Transient_for" windows (most dialog boxes) are given focus when mapped. When such a window goes away, focus is given to the top X window. (3) Color problems have been fixed. When PM is in 16 color mode, PMX can no longer incorrectly set pseudocolor mode. (4) On an S3 PM display driver, the PM cursor turns all black after OS/2 boots. The presence of the PMX Graphics Engine Hook causes this. This problem has been reported as OS/2 APAR PJ14277. There is a work-around: Enter a full-screen OS/2 session and then come back to the PM desktop. Evidently this causes the S3 display driver to reset the graphics hardware state, restoring the white areas of the PM cursor. ---------------------------------------------------------------------- Release 2.0.1j beta - 1994 May 23 This is a beta version of CSD UN60006 (1) Fix for windows that are initially iconified. (2) The utility ALLFONTS allows the user to compile all BDF fonts to PCF fonts in the current directory. See \tcpip\doc\readme.pmx. (3) Some drawing problems have been fixed. (4) A fix was made to grabs. Now splitting the control desk off from the main window in NV6000 will work. (5) More validity checking of the X window associated with a PM window is done. (6) If tracing, extension requests will no longer mess up traces and sometimes trap PMX. (7) A problem with Interleaf Worldview was fixed, where the "quit" dialog box popped up if Worldview was given focus. ---------------------------------------------------------------------- Release 2.0.1h beta - 1994 April 26 This is a beta version of CSD UN60006 (1) This has a fix for several color problems in the palette manager support. (2) There is a fix for a trap caused by running the X version of CoralDraw. (3) Installation of PMXFIX2 package was simplified. ---------------------------------------------------------------------- Release 2.0.1g beta - 1994 April 20 This is a beta version of CSD UN60006 (1) PMX PseudoColor has been implemented using PM Palette Manager palettes. The -palettemgr flag has been added for this purpose. The -pseudocolor (-pseudo) flag still causes PMX to run in Realizable Color Table mode. PMX Palette Manager support only works if a Graphics Engine hook DLL (GREHOOK.DLL) is loaded by OS/2 at boot time. Make sure that OS/2 gets rebooted after installing PMFIX2 or the PMX CSD. Also, the Color page of the Configuration notebook has been revised. NOTE: There is a PM Palette Manager bug which prevents PMX from changing 4 of the 256 colors when an X application obtains a private PseudoColor colormap. This bug is most noticeable in X image viewing applications, such as XLOADIMAGE. There will be four blueish or grayish colors present which do not belong in the picture. The fix for this bug is being pursued as an OS/2 PM APAR. NOTE: When running PMX in Palette Manager mode, PMX reserves a section of the PM Palette for X applications. The least number of PM Palette entries that PMX will work with is 129, which leaves a maximum of 63 palette entries available for other PM applications that also use the Palette Manager. This can be a problem for image viewing PM applications that usually need *lots* of palette entries before their images look OK. If you need to view perfect PM images while PMX is running, we recommend that you run PMX in StaticColor mode. (2)PMXRESET utility -- a new utility called PMXRESET has been added to PMX. PMXRESET can be used to reset the PM desktop colors back to their original values in the event that PMX crashes in PseudoColor mode. (3) PMX now only presents one type of color visual to X applications, either StaticColor or PseudoColor, but not both. Previous versions of PMX allowed command line flag combinations such as -static -pseudo or -pseudo -static. This version of PMX only acts on the last color flag entered, so that -pseudo -static, for example, results in PMX running in StaticColor mode. (4) Double-size X cursors are now fixed. (5) The on-line help and the PMX.INF documentation have been reorganized. (6) A number of fixes have been included. APARS PM51433 and PM52079 are fixed by this CSD. ---------------------------------------------------------------------- Release 2.0.1f beta - 1994 March 17 This version had a limited distribution, and various versions of it had fixes for the following problems. (1) A pixmap bug is fixed. (2) PMX now responds to the application message that says to iconify a window. (3) Certain alt-pfkey combinations are available on X application windows, provided that _MOTIF_WM_HINTS properties do not turn them off. They are available only for windows with frames, not menus. The keys that are supported are: key combination function --------------- -------- alt-f4 close the window alt-f5 restore a maximized or iconified window alt-f7 move the window alt-f8 resize the window alt-f9 iconify the window alt-f10 maximize the window (4) PMX now coexists with display adaptors configured to run with more than 256 colors, typically 64k colors (16 bit pixels) or 16m colors (24 bit pixels). PMX will only provide static color visuals in this case, and still only 256 colors. (5) A synthetic ConfigureNotify event sometimes had bad values, affecting a few applications. ---------------------------------------------------------------------- Release 2.0.1e beta - 1994 March 3 (1) The FONTS.ALI file has been fixed in \tcpip\x11\75dpi. It had a number of incorrect references. They included references to andy*, courier*, helvetica*, symbol*, and times* fonts. (2) Certain Motif properties are now used by PMX. The _MOTIF_WM_HINTS property has two fields, functions and decorations, which are used. A typical case is for a Motif application to set this property on a window to remove the minimize or maximize buttons, or to remove the resize border, especially for dialog boxes or tear-off menus. The property should be used by the program, and not by the typical user. It allows the deleting of the following PM frame decorations and their associated window functions. Function Frame Decoration minimize Minimize Button maximize Maximize Button close System Menu Button move Title Bar (only if the above three are also deleted) resize Resize Border (replaced with a dialog window border) resize Border (replaced with a one pixel wide border) _MOTIF_WM_HINTS specifies removing of the decorations from the frame independently of removing the function. For PMX, removing either will remove the other. This may change a bit in subsequent versions of PMX. The Motif programmer is encouraged to specify both. (3) The PMXFIX2 package INSTALL.CMD now allows installation without prompts. (4) A loop problem was fixed, that tended to use all the machine cycles. (5) Display of blanks has been fixed. Sometimes they would display as dots. (6) The alt-pfkey combination on the client window, has been temporarily disabled. It will be available in the next release. ---------------------------------------------------------------------- Release 2.0.1d beta - 1994 February 14 (1) A new flag has been added, -fakeBackingStore. This makes PMX say that it supports backing store (although in fact it still does not). Some applications refuse to run unless this indicator is set, even though they should be able to run without it. (2) Some minor fixes are included, and some changes to what is traced. (3) XINIT.CMD no longer checks for a valid DISPLAY environment variable, but constructs one based on the value of the HOSTNAME environment variable. XINIT.CMD will refuse to run if the HOSTNAME environment variable does not exist. ---------------------------------------------------------------------- Release 2.0.1c beta - 1994 January 21 (1) This basically has much improved handling of Japanese keyboard. For the test cases we could duplicate, we no longer miss characters entered in romaji mode. This did not work in 2.0.1b. ---------------------------------------------------------------------- Release 2.0.1b beta - 1993 December 16 (1) The handling of keys in client windows has been changed so that OS/2 special keys are no longer obeyed, but are passed on to the client. Examples are alt-enter, alt-F4, or alt-F7. We would like to supply a control to allow the old behavior, but do not have one at this time. Not all OS/2 keys are suppressed, for example ctrl-alt-del or ctrl-esc. ---------------------------------------------------------------------- Release 2.0.1a - 1993 December 1 (1) The ja_JP directory should have been accessed instead of ja_JA, for Japanese keyboard support, in the configuration notebook. (2) The alt-hiragana key combination caused dialog boxes to pop up. This has been fixed, but the user is warned that Japanese support is still not completely tested, and there are still some problems. (3) The CSD included many fonts, because two bytes were found to have changed in each such font. However, this package does NOT include those fonts, since we still have found no difference between the new and old versions in use. If you wish to be sure, install the CSD first, and then install PMXFIX2. ---------------------------------------------------------------------- Release 2.0.1 (CSD UN52841) - 1993 November 22 (1) A fixed version of xlib.dll is included. (2) Two Japanese xmodmap keyboard files have been fixed. (3) The README.PMX file is updated to show all changes since PMX 2.0. The APARs fixed by this CSD are mentioned. (4) A number of fonts were found to have changed when recompiled, in two bytes only. Although some tests showed no change in behavior, we took the conservative approach and included such changed fonts. Thus the official CSD requires 3 diskettes. ---------------------------------------------------------------------- Release 2.0.09 beta - 1993 November 12 (1) This version is being thoroughly regression tested, to be released as the first "official" CSD for PMX 2.0. (2) SVGA PM device drivers have problems with certain copy operations, which affected text. We have coded around the problem. (3) A number of fixes were made that mainly affect Motif applications. (4) Fixes were made so that PMX no longer traps in OS2J. (5) The color setting in the configuration notebook now correctly sets the pseudocolor/staticcolor options. This bug was introduced in one of the fixes since PMX 2.0. (6) The capslock and numlock keys interfered with each other. This is now fixed. (7) A problem with the xscope handling of large messages has been corrected. (8) The 8514 PM device driver has problems with patterned area fills. Typically the colors are incorrect. This problem is resolved by OS/2 APAR PJ10633. Contact OS/2 Support for information regarding PJ10633. ---------------------------------------------------------------------- Release 2.0.08 beta - 1993 November 1 (1) A loop could happen sometimes, when maximizing and restoring, in the PMX WM_PAINT message handling. ---------------------------------------------------------------------- Release 2.0.07 beta - 1993 October 22 (1) A problem with expose handling was fixed. Its symptom was a dialog box mentioning WM_PAINT. (2) GpiDrawBits had been used for copying characters to internal pixmaps for fonts, to speed up font operations. Unfortunately, GpiDrawBits is buggy in some PM device drivers, especially SVGA. It was possible to get error messages of various sorts, such as "address out of range." We no longer use GpiDrawBits. (3) A problem with opening fonts in both a 16 bit and 8 bit mode, caused some text to not be displayed, or to be displayed incorrectly. ---------------------------------------------------------------------- Release 2.0.06 beta - 1993 October 15 (1) This fix is basically identical to 2.0.05, except that it was compiled with the C-Set/2++ C compiler, in the hopes that some bugs might have been compiler bugs. Not generally released. ---------------------------------------------------------------------- Release 2.0.05 beta - 1993 October 12 (1) Two color fixes have been added. (2) The PMX.LOG file is now backed up to PMXBACK.LOG automatically. Thus if PMX is restarted after a problem that causes data to be entered in PMX.LOG, the desired data will be in PMXBACK.LOG. (3) A -logfonts command line argument is available. It causes PMX to log font requests. There is also a notebook entry to turn this logging on and off. The main use for this feature is to discover what font requests are being made by an X application that is reporting failures to find fonts. The on-line documentation also discusses what to do in such a situation. (4) Two more fonts from AIX are included, itl14.pcf and itl14_i1.pcf. The latter is renamed to fit in a FAT file system. FONTS.ALI was changed to map incorrect font requests of certain IBM programs to font references with correct point sizes. The fonts involved are all IBM fonts. (Note that AIX does the same thing in its fonts.alias file.) This fixes some instances where fonts can get scaled up many times their usual size because of the incorrect font requests. ---------------------------------------------------------------------- Release 2.0.04 beta - 1993 September 24 (1) There is a major Pseudocolor fix: PM device drivers attempt to share colors by matching RGB values to the color table currently realized into hardware. This was bad news for PMX. Let's say that a PMX X client wanted to have blinking white symbols in its windows. It would make an AllocColorCells X request and PMX would return a reserved pixel value, eg. 0x2c. The client would then do a StoreColors request to set that pixel's value to 0xFFFFFF (white). For other parts of PM, and other PMX clients, the normal pixel value for white is 255 (0xFF). Becuase of PM's RGB sharing logic, every white pixel that gets written from now on will be *translated* to pixel value 0x2c on the screen! Everything looks OK until the X client wants to blink the 0x2c pixel it "owns"... all newly written whites (like pieces of window/desktop backgrounds) will also blink! The PMX fix for this is to ensure that every RGB value is unique, even if it denotes the same color. PMX does this by encoding the 8 bit pixel value inot the lower 2 bits of the Red value, the lower 2 bits of the Green value, and the lower 4 bits of the Blue value. This poison's the PM color sharing algorithm! (2) PMX now recognizes the (IBM Internal Beta version of the) 32-bit Image Adapter and allows pseudocolor for it. (3) All lines in PMX.LOG now end in Carriage-Return + Line-Feed characters. ---------------------------------------------------------------------- Release 2.0.03 beta - 1993 September 23 Xinit.cmd turned out to have a bug or two, and has been fixed. Nothing else has been changed. ---------------------------------------------------------------------- Release 2.0.03 beta - 1993 September 21 (1) The shape extension has been implemented. This especially affects users of the latest version of Netview. The "control desk" is now useable. WARNING: If the non-rectangular window is a top level window, the area between the window and the surrounding PM frame is not written by PMX or the X application, and contains whatever was there before the window was displayed. This makes it appear that the user can click on the items seen in this area, when in fact that is not possible. We expect to make further changes in this area in future versions. (2) Xdmcp, the X display management protocol, is now implemented in PMX, although it has not been thoroughly tested. We will be making further changes in this area, and adding documentation for this feature of X, in a future version. PMX command line options for PMX XDMCP support include: Partially tested: -query host-name contact named host for XDMCP -broadcast broadcast for XDMCP -indirect host-name contact named host for indirect XDMCP Disabled: -once Terminate server after one session Untested so far: -port port-num UDP port number to send messages to -class display-class specify display class to send in manage -cookie xdm-auth-bits specify the magic cookie for XDMCP -displayID display-id manufacturer display ID for request (3) The "permit old bugs" command line option was not documented, and was not turned on by default. This means that certain old applications or applications based upon old toolkits, could have requests rejected by PMX 2.0 because of "junk" in places where the values should be zero. Now PMX will normally ignore such bugs as a default. The "bc" command line option turns off such bug checking, and "-bc" turns it on. There is also a configuration notebook entry for this option. (4) PMX can now access one or more font servers. Any place where a directory can be specified in a font path, you can now specify a font server as well. The font server specification has the form tcp/: where port number is 7000 by default, and must be 7500 for AIX. Example: pmx -fp \tcpip\x11\misc,\tcpip\x11\75dpi,tcp/myaixhost:7500 (5) There was a problem with the handling of "exposes", that could cause the server to terminate. (6) In some cases, it was possible for a single X window to grab the mouse when it should not have. Ctrl-esc could be used to get out of the problem, but it is now fixed. (7) There were problems in the painting of certain windows (dialog box or "transient_for" windows) if such a window had an X border on the top level window. The window manager code now makes the border be zero in width, just like normal windows. (8) XINIT.CMD now pays attention to the language settings in the PMX notebook. (9) If an X application started up iconified, the main title was used instead of the icon title. Now the icon title is used. (10) Resetting the server is now supported, both by the standard X protocol functions, and by a menu item. This causes all X applications to be closed. (11) The font path now can be changed dynamically in the configuration notebook. This is equivalent to using xset to change the font path. (12) xhost.exe did not accept host names as command line arguments! It is fixed now. (13) PMX "hung" or took a very long time to start up, if it used a network name server that was not running. Now, if PMX detects this situation, it uses the \tcpip\etc\host file to resolve host names. ---------------------------------------------------------------------- In the sections below are major remaining known problems and things still not implemented for PMX. ---------------------------------------------------------------------- - Color support For certain versions of the operating system and certain PM device drivers color support is somewhat eratic. The "refresh all clients" command menu option does not always clean up colors. We are working with the OS/2 developers to correct this situation. It is recommended that you use OS/2 2.0 with the latest Service Pack, or OS/2 2.1 with the latest service pack, or Warp with the latest fixpack. - Cursor limitations If an X client creates a cursor using bitmaps that are larger than 32x32, the portion in the lower left corner is used, instead of the portion around the "hot spot". The result may be an incorrect appearing cursor. The user may avoid using cursors created by X applications by starting PMX with the -pmcursor parameter. - Window manager hints Not all "window manager hints" are paid attention to as yet. We do pay attention to most. Mainly missing are colormap conventions, and optional size conventions that control ratios of window width and height. - Unsupported X11R5 Features Only PCF fonts are supported; compressed versions are not, and BDF fonts are not automatically compiled to PCF.