HP b2600 Administration Manual

Hp b2600: supplementary guide
Hide thumbs Also See for b2600:
Table of Contents

Advertisement

Graphics Administration Guide for HP-UX 10.20. After using this document for a while, please fill out
the Reader Reply form. Or, just e-mail us your comments at
muserlink@fc.hp.com
Graphics Administration Guide for HP-UX 10.20

Advertisement

Table of Contents
loading

Summary of Contents for HP b2600

  • Page 1 Graphics Administration Guide for HP-UX 10.20. After using this document for a while, please fill out the Reader Reply form. Or, just e-mail us your comments at muserlink@fc.hp.com Graphics Administration Guide for HP-UX 10.20...
  • Page 2: Table Of Contents

    ...17 EVICE RIVER IBRARIES HP PEX A OMPILING PPLICATIONS GL A OMPILING PPLICATIONS CHAPTER 3: X WINDOWS: HP-UX 10.20 ...22 ...22 ERVER ONFIGURATION X*screens File...23 Description of the X*screens Configuration File...23 The X*screens File Format...23 Sample X*screens Files...25 ...30 ISCELLANEOUS OPICS Double Buffer Extension (DBE)...30...
  • Page 3 X*devices File ...81 Explicitly Specifying Input Device Use ...82 Explicitly Specifying RS-232 Input Device Use ...82 Specifying hp-HIL Input Device Use by Device File Name ...85 Redefining the hp-HIL Search Path ...86 Stopping the X Window System ...86 NITIALIZING THE...
  • Page 4 ... 147 ECURITY ORMAT INIT ... 151 UNNING ... 151 RANTING CCESS ... 152 IGNALS ... 153 ONTS ... 153 IAGNOSTICS ... 154 ILES ... 154 OTES ... 154 OPYRIGHT ... 154 RIGIN ... 155 Graphics Administration Guide for HP-UX 10.20...
  • Page 5 APPENDIX G: RX HELPER PROGRAM ... 169 ... 169 ... 169 YNOPSIS ... 169 ESCRIPTION ... 169 NSTALLATION ... 170 PTIONS ... 170 ESOURCES ... 170 NVIRONMENT ... 171 OTES ... 171 RIGIN ... 171 Graphics Administration Guide for HP-UX 10.20...
  • Page 6: About This Guide

    About this Guide Graphics Administration Guide: Information for Programmers, System Administrators, and End-Users Copyright © June 1997, June 1998, June 2000 Hewlett-Packard Company HP 9000 Workstations Notices The information contained in this document is subject to change without notice. Hewlett-Packard provides the following material "as is" and makes no warranty of any kind with regard to this manual, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose.
  • Page 7 The manual part number changes when extensive technical changes are incorporated. June 2000. . . Edition 3. This document is valid for HP9000 workstations running HP-UX 10.20 along with the December 1999 Workstation ACE and Quality Pack.
  • Page 8: Preface

    However, some of these aspects were not unique to Starbase, they pertained to graphics operation in general: they applied to all of our APIs. Therefore, those users who had HP-PHIGS would be encountering some of the same graphical questions that were already well-documented in the Starbase documentation.
  • Page 9: Document Conventions

    Conceptual values are in italic type, enclosed in angle brackets. These items are not verbatim values, but are descriptors of the type of item it is, and the user should replace the conceptual item with whatever value is appropriate for the context. Page 9 Graphics Administration Guide for HP-UX 10.20...
  • Page 10: Chapter 1: Pathnames

    "find /opt ...". Also, you can specify just a partial filename; find will locate all files containing a specified substring in their names. The find command has many other options for refining a search; see the reference page for details. Page 10 Graphics Administration Guide for HP-UX 10.20...
  • Page 11: Starbase

    Subsequent sections of this chapter contain the actual pathnames referred to in other HP graphics API documents, such as Starbase, PEX, etc. A particular paragraph might refer to, say, the <demos> directory. Find the API you're looking for. In that section is an alphabetical list of "generic names", the file system path references used in the other documents and with each you will see its actual location in the file system.
  • Page 12: Hp-Phigs

    <phigs> <phigs-demos> <phigs-examples> <phigs-incl> <phigs-lib> <phigs-widget> <screen> <spool> <starbase> <vue-config> <x11> <x11r6> <x11r6-incl> <xconfig> Page 12 Graphics Administration Guide for HP-UX 10.20 HP-PHIGS Location in the file system /usr/lib/X11/app-defaults /opt/graphics/common /dev /opt/graphics/common/lib/nls/msg/C /opt/graphics/phigs /opt/graphics/phigs/demos /opt/graphics/phigs/examples /opt/graphics/phigs/include /opt/graphics/phigs/lib /opt/graphics/phigs/include/Motif1.2 /dev/screen /var/spool...
  • Page 13: Hp Pex

    <pex-fonts> <pex-incl> <pex-lib> <pex-utils> <profile> <rel-notes> <spool> <vhelp> <vue> <x11> <x11-incl> <x11r6> <x11r6-incl> Page 13 Graphics Administration Guide for HP-UX 10.20 HP PEX Location in the file system /usr/lib/X11/app-defaults /opt/graphics/PEX5/examples/cge /opt/graphics/PEX5/utilities/cge /opt/graphics/PEX5/contrib /opt/graphics/PEX5/help5.1 /opt/graphics/PEX5/newconfig/usr/lib/X11/extensions /opt/graphics/PEX5/examples/hp /opt/graphics/PEX5/share/man /opt/graphics/PEX5/lib/nls/msg/C /opt/graphics/PEX5/examples/OReilly /opt/graphics/PEX5 /opt/graphics/PEX5/lbin...
  • Page 14: Chapter 2: Compiling Your Application

    Chapter 2: Compiling Your Application This chapter provides information for compiling your application with either archived or shared libraries for the following Application Programming Interfaces (APIs): Starbase, HP-PHIGS, and HP PEX. Compiling examples are given for C, Fortran, and Pascal.
  • Page 15: Compiling Hp-Phigs Applications

    -L<pathname> -Wl,-L<pathname> For more information on compiling and linking, read the section "PHIGS PLUS Differences Between HP-PHIGS 2.2/2.3 and 3.0" in the chapter "Functional Overview" in the HP-PHIGS Graphics Techniques manual. Page 15 Graphics Administration Guide for HP-UX 10.20...
  • Page 16: Compiling With Archive Libraries

    -L<pathname> -Wl,-L<pathname> For more information on compiling and linking, read the section "PHIGS PLUS Differences Between HP-PHIGS 2.2/2.3 and 3.0" in the chapter "Functional Overview" in the HP-PHIGS Graphics Techniques manual. Page 16 Graphics Administration Guide for HP-UX 10.20...
  • Page 17: Device Driver Libraries

    Integrated Color Graphics 715/33, 715/50, 715/75, Internal Color Graphics (Model 712/60, 712/80, 712/80i, 712/100, 715/64, 715/80, 715/100, 715/100XC, HP VISUALIZE-48[XP] Page 17 Graphics Administration Guide for HP-UX 10.20 CRX Family Output Device (Model 705, 710, 725/50, 725/75) 725/100) HP CRX/GRX...
  • Page 18 HP VISUALIZE-FX2 HP VISUALIZE-FX4 HP VISUALIZE-FX6 HP VISUALIZE-FXE HP VISUALIZE-EG HP VISUALIZE-FX2 HP VISUALIZE-FX4 HP VISUALIZE-FX6 HP VISUALIZE-FXE Page 18 Graphics Administration Guide for HP-UX 10.20 HP VISUALIZE-FX Family Legacy APIs libddhcrx.a or libddhcrx.sl libddvisx.a or libddvisx.sl libddfxe.a or libddfxe.sl OpenGL libddhcrx.sl...
  • Page 19 HP C1600A HP C1601A HP C1602A HP C1620A HP C1625A HP C1627A HP C1629A HP C1631A Page 19 Graphics Administration Guide for HP-UX 10.20 HP-GL Plotters libddhpgl.a libdvio.a or libddhpgl.sl libdvio.sl libddCADplt.a or libddCADplt.sl With HP-GL/2 plug-in cartridge Link Line Options...
  • Page 20 (pixel-major packing orders) Starbase Memory Driver (plane-major packing order) The Personal Visualizer File Format The ".a" version of the VMX driver is bundled with Page 20 Graphics Administration Guide for HP-UX 10.20 Miscellaneous Device Drivers libddvmx.sl libddsox11.a or libddsox11.sl libdddl.a or libdddl.sl libddhpcgm.a...
  • Page 21: Compiling Hp Pex Applications

    Compiling HP PEX Applications HP PEXlib is supported on the Series 700 workstations using shared libraries that must be linked with the application program. Only PEX programs written in C (not FORTRAN or Pascal) are supported. When you compile your PEXlib programs, you must link the application with the PEXlib library libPEX5.
  • Page 22: Chapter 3: X Windows: Hp-Ux 10.20

    Chapter 3: X Windows: HP-UX 10.20 This chapter documents information specific to the HP X server. It describes features unique to HP's X server, provides information on how to configure the X server and includes a list of supported X configurations.
  • Page 23: Screens File

    The block from the "Screen <device_name>" line to the final "<screen_option>" line is referred to as a either a "Screen Entry" or as a "Single Logical Screen entry". As shown above, the X*screens format is Page 23 Graphics Administration Guide for HP-UX 10.20...
  • Page 24: Server Options

    Specifying this server option forces all extensions to be loaded at X server startup. Immediate loading of X extensions is the historical behavior of the HP-UX 10.10 and 10.20 X servers. The 10.20 X Server patches shipped after July, 1997 and all 11.00 versions of the X Server perform delayed loading of the X extensions.
  • Page 25: Sample X*Screens Files

    • This is the minimum legal X*screens file, the "Screen" keyword followed by the screen device. Since no other information is given, the X server will assume default values for other options and settings. Screen /dev/crt Figure 1: Results of Minimal Legal Page 25 Graphics Administration Guide for HP-UX 10.20 File X*screens...
  • Page 26 HCRX-24 is the opaque overlay visual. All 256 colormap entries are opaque and allocable. If an application requires transparency in the default visual, the "Transparent" keyword can be used to select the transparent overlay visual as shown below. Page 26 Graphics Administration Guide for HP-UX 10.20...
  • Page 27 Assuming the first device is associated with the device file "/dev/crt0", the second device is associated with the device file "/dev/crt1", etc. The following examples specify valid Single Logical Screen configurations. Page 27 Graphics Administration Guide for HP-UX 10.20...
  • Page 28 Figure 4: Four Physical Displays, Single Logical Screen (1X4) SingleLogicalScreen 4 1 /dev/crt0 /dev/crt1 /dev/crt2 /dev/crt3 Figure 5: Four Physical Displays, Single Logical Screen (4X1) SingleLogicalScreen 2 2 /dev/crt0 /dev/crt1 /dev/crt2 /dev/crt3 Page 28 Graphics Administration Guide for HP-UX 10.20...
  • Page 29 Single Logical Screen. Below is an example of this: • Screen /dev/crt0 SingleLogicalScreen 1 2 /dev/crt1 /dev/crt2 Figure 7: Three Physical Displays, Screen plus Single Logical Screen (1X2) Page 29 Graphics Administration Guide for HP-UX 10.20...
  • Page 30: Miscellaneous Topics

    Note: MBX (the Multi-Buffering eXtension to X) has not been adopted as an industry standard, as DBE has. Thus, it is recommended that applications that use MBX be ported to DBE usage in preparation for future MBX obsolescence (HP-UX 11.0). For more information about DBE and the API, consult the DBE man pages:...
  • Page 31: Display Power Management Signaling (Dpms)

    The X server features the ability to make use of DPMS on the following graphics devices: • HP VISUALIZE-EG • HCRX-8[Z], HCRX-24[Z] • HP VISUALIZE-8, HP VISUALIZE-24, and HP VISUALIZE-48[XP]. • HP VISUALIZE-FX , HP VISUALIZE-FX • HP VISUALIZE-FX and FX •...
  • Page 32: Mbx

    8-plane buffer; this includes the color graphics device and the overlay planes on the CRX-24[Z], CRX-48Z, HCRX, and HP VISUALIZE family. For these devices, MBX double-buffering is still supported, but the second bank is allocated in virtual memory. Rendering and buffer-swapping in these instances is slower than devices/visuals that support true hardware double- buffering.
  • Page 33: Shared Memory Extension (Mit_Shm)

    Manual by Tom Gaskins, and published by O'Reilly & Associates, Inc. Consult that manual to understand the creation, manipulation, and destruction of MBX buffers. Since MBX is not an industry standard, and will be discontinued on HP-UX 11.0, developers should replace MBX calls with the appropriate DBE calls.
  • Page 34: Shared Memory Transport (Smt)

    • A Display Name of any of the forms listed below are used. ":0.0" is used for simplicity. This behavior is equally applicable for displays such as ":1.0". :0.0 local:0.0 <hostname>:0.0 shmlink:0.0 Page 34 Graphics Administration Guide for HP-UX 10.20...
  • Page 35: Performance Tuning Of Smt

    A display name of the form unix:0.0 will force the use of Unix Domain Sockets (UDS), which is identical to the local transport used before HP-UX 10.20. A display name of the form nn.nn.nn.nn:0.0 (where nn.nn.nn.nn is an IP address) will force the use of Internet Sockets, which is the remote transport normally used, and which can be used locally.
  • Page 36 (and consequently the buffer must fit within the whole region). If these parameters are used, be sure to confirm that they actually cause an improvement in actual usage situations. Incorrect values can degrade performance. Page 36 Graphics Administration Guide for HP-UX 10.20...
  • Page 37: Enabling And Disabling Of Smt

    _XConnectDisplay(..., &dummy); Symptoms include both damaged data and core dumps. (There was an earlier HP Shared Memory Transport, which this one replaces. It used the same parameter, so it may be the case that any such calls have already been fixed.) This problem does not occur in the R6 library.
  • Page 38: Hp Color Recovery

    Access to the Color Recovery capability is transparent when using a 3D graphics API such as Starbase, HP-PHIGS or PEX. If you are producing graphics using Xlib calls, your application must perform some of the necessary processing. The method to access Color Recovery via Xlib is described in a section called "Accessing HP Color Recovery Technology via Xlib"...
  • Page 39: Dynamic Loading

    GetImage behavior is to include the depth-dependant contents of inferior windows (in other words, GetImage requires that IncludeInferiors work properly). As of the 10.10 release, HP has offered a solution to the IncludeInferiors defect. Some customers create their test image archives using XGetImage (which currently returns incorrect data for multi-layer and double-buffered devices).
  • Page 40: Shared Memory Usage With 3D Graphics

    If more shared memory space is needed, graphics shared memory size can be increased. For example, to set it to eight megabytes: ServerOptions GraphicsSharedMemorySize=0x800000 ____________________________________________________________________________________ Note: The value must be in hexadecimal. The new value won't take effect until you restart the X Server. ____________________________________________________________________________________ Page 40 Graphics Administration Guide for HP-UX 10.20...
  • Page 41: Count Transparent In Overlay Visual

    Setting this option will cause the X server to count transparent entries in the number of colormap entries. Examples of Relevant Graphics Devices: CRX-24[Z], CRX-48Z HP VISUALIZE-EG HCRX-8[Z], HCRX-24[Z] HP VISUALIZE-8, HP VISUALIZE-24, and HP VISUALIZE-48[XP] HP VISUALIZE-FX , HP VISUALIZE-FX HP VISUALIZE-FX and FX HP VISUALIZE-FXE...
  • Page 42: Image Text Via Bitmap

    Special device files are used to communicate between the computer and peripheral devices. The X server requires the use of a special device file for each graphics card present in the system. On HP-UX 10.x systems, five special graphics device files are automatically created. The first or primary graphics card, also known as the "console", uses the "/dev/crt"...
  • Page 43: Supportedx Configurations

    A configuration in which a single X server with a mouse and keyboard drives multiple graphics devices (where each display is a different X Screen) concurrently while only allowing the cursor, not windows, to be moved between displays. Page 43 Graphics Administration Guide for HP-UX 10.20 Figure 8: Multi-Screen...
  • Page 44 Multi-Seat A configuration with multiple instantiations of the X server, each with its own mouse, keyboard, and display(s). Multi-seat is not currently supported in any HP-UX 10.* release. Figure 9: Multi-Seat Single Logical Screen A configuration in which a single X server with a single mouse and keyboard drives multiple homogeneous graphics devices concurrently while allowing the displays to emulate a large single screen.
  • Page 45: Multi-Screen Support

    The list of supported multi-display configurations is rather large, and it changes whenever a new graphics device is introduced. Thus, if you are considering a Single Logical Screen or any other multi- display configuration, we recommend consulting your HP Sales Representative and inquiring whether the configuration you have in mind is indeed supported.
  • Page 46 Note: The on-board and "card" versions of the same device can be considered identical; for example, you could use an on-board HP VISUALIZE-EG graphics device and an HP VISUALIZE-EG graphics card, and still consider them identical devices, thus permitting a 1X2 SLS or a 2X1 SLS.
  • Page 47 3D Acceleration and Single Logical Screen Currently, SLS does not take advantage of 3D acceleration (e.g. CRX-24Z). 3D applications (from any supported HP 3D API) will continue to run with SLS; However, 3D performance with SLS will be much slower than it is without SLS.
  • Page 48: Distributed Single Logical Screen (Sls/D)

    This behavior is the result of HP VUE's naive assumption that it is running against one large screen; it centers these windows accordingly. If you are using the default HP VUE key bindings, you can easily reposition the Front Panel so that it is completely contained within one physical screen: With the input focus on the Front Panel, press With the Front Panel menu posted and the "Move"...
  • Page 49 Note: The use of "0" for the master is very important. If you change this number, CDE will not run properly unless you also make the necessary changes to have CDE run to a non-default screen location. ____________________________________________________________________________________ Then, to configure the logical screen as follows: Page 49 Graphics Administration Guide for HP-UX 10.20 Figure 11: Logical Screen Configuration...
  • Page 50 Up to 64 displays can be configured as a Distributed Single Logical Screen with the following restrictions: • All SLS/d slave systems must be running HP-UX 10.20 with the January 1999 periodic patch or a subsequent HP-UX 10.20 patch; • All SLS/d slave displays must be using the same graphics display device;...
  • Page 51: Integrated Color Graphics Device-Dependent Information

    Application C uses a third colormap. If applications A, B, and C are all executed simultaneously on a Model 712, application A would look correct. Either application B or C would have Page 51 Graphics Administration Guide for HP-UX 10.20...
  • Page 52: Accessing Hp Color Recovery Technology Via Xlib

    Access to the Color Recovery capability is transparent when using a 3D graphics API such as Starbase, HP-PHIGS or PEX. If you are producing graphics using Xlib calls, your application must perform some of the necessary processing. At server startup (if Color Recovery is not disabled in the X*screens file), the following properties are defined and placed on the root window: •...
  • Page 53 /* Check for overflow or underflow on red value */ if (red > 0xff) red = 0xff; if (red < 0x00) red = 0x00; /* Generate the green dither value */ green += dither_green[y_dither_table][x_dither_table]; Page 53 Graphics Administration Guide for HP-UX 10.20 and Y ) of the pixel.
  • Page 54: Internal Color Graphics, Internal Grayscale Graphics, Crx, Grx, And Dual-Crx Device-Dependent Information

    DBE and MBX software double-buffering (Internal GrayScale Graphics) The "layer" and "transparent" default visual options are not supported. Supported Screen Options The following Screen Options are supported: • SwapBuffersOnVBlank • 3BitCenterColor (Internal Color Graphics only) • EnableIncludeInferiorsFix Page 54 Graphics Administration Guide for HP-UX 10.20...
  • Page 55: Crx-24[Z] Device-Dependent Information

    • Clients attempting to allocate 256 entries do not have their request granted. • Clients requesting (via XAllocNamedColor) the rgb.txt value of "Transparent" are not returned entry 255. This default behavior can be changed by setting the CountTransparentInOverlayVisual screen option. Page 55 Graphics Administration Guide for HP-UX 10.20...
  • Page 56: Crx-48Z Device-Dependent Information

    (that is, show the image planes). This may have the following two consequences for X11 applications running in the overlay planes (the default visual): • Clients attempting to allocate 256 entries do not have their request granted. Page 56 Graphics Administration Guide for HP-UX 10.20...
  • Page 57: Hcrx And Hp Visualize Device-Dependent Information

    HCRX-8 device when in double-buffer mode. See below for a description of these modes. For shorthand notation, from this point on in the document, HP VISUALIZE-EG will refer to either mode, HP VISUALIZE-EG(8) will refer to 8 plane mode only and HP [Dual] VISUALIZE-EG will refer to double-buffer mode only.
  • Page 58: Supported Visuals

    The HP VISUALIZE-48[XP] is a two-board accelerated device that fills two slots. If you add either the optional texture-mapping memory card or the optional video-out card, it becomes a three-board set that fills three slots. Add both optional cards, and it becomes a four-board set, but it still fills only three slots.
  • Page 59: Supported Screen Options

    DBE and MBX double-buffering • Class TrueColor Depth 24 Layer Image - doesn't support DBE and MBX double-buffering The following visuals are supported on the HP VISUALIZE-48[XP]: • Class PseudoColor Depth 8 Layer Image - supports DBE and MBX hardware double-buffering •...
  • Page 60: Hcrx Configuration Hints

    Double-Buffer mode is compatible with the HCRX-8 device. This mode requires an optional memory daughter card. If the daughter card is installed, selecting this mode will result in eight overlay planes and 16 image planes (the same as HCRX-8 and HP VISUALIZE-8 devices). Double-Buffer mode allows the use of hardware double-buffering.
  • Page 61 For applications that require transparent overlay windows on the HCRX-8[Z], HP VISUALIZE-EG(D) or HP VISUALIZE-8, an optional X server mode is available to allow for overlay transparency, but it is restrictive. In this optional mode, overlay colormaps provide a single entry that can be used to render transparency.
  • Page 62 Overlay Transparency on the HCRX-24[Z], HP VISUALIZE-24, and HP VISUALIZE-48[XP] The HCRX-24[Z], HP VISUALIZE-24, and HP VISUALIZE-48[XP] have two visuals in the overlay planes, both depth-8 PseudoColor. The default overlay visual has 256 entries per colormap and no transparency. The second overlay visual has 255 entries per colormap and supports transparency in the same way as the CRX-24[Z].
  • Page 63 No issues involving transparency exist because of the lack of Overlay planes. HCRX-8[Z], HP [Dual] VISUALIZE-EG and HP VISUALIZE-8: Eight Overlay Planes and Two Depth-8 Banks of Image Planes When the default visual is in the overlay planes (default location) and the screen option...
  • Page 64: Accessing Hp Color Recovery Technology Via Xlib

    Access to the Color Recovery capability is transparent when using a 3D graphics API such as Starbase, HP-PHIGS or PEX. If you are producing graphics using Xlib calls, your application must perform some of the necessary processing. At server startup (if Color Recovery is not disabled in the X*screens file), the _HP_RGB_SMOOTH_MAP_LIST property is defined and placed on the root window.
  • Page 65 /* Determine the dither table entries to use based on the pixel address */ x_dither_table = Xp % 16; /* X Pixel Address MOD 16 */ Page 65 Graphics Administration Guide for HP-UX 10.20...
  • Page 66 (blue > 0xff) blue = 0xff; if (blue < 0x00) blue = 0x00; pixel = ((red & 0xE0) | ((green & 0xE0) >> 3) | ((blue & 0xC0) >> 6)); return(pixel); Page 66 Graphics Administration Guide for HP-UX 10.20...
  • Page 67: Fx 4 And Fx

    • The HP VISUALIZE-FX buffer and 8 hardware colormaps. HP VISUALIZE-FX2/4/6 graphics devices contain 2D hardware acceleration similar to that in other HP VISUALIZE devices as well as 3D acceleration for geometry, lighting, and shading. Optional texture mapping acceleration is also available.
  • Page 68 DBE hardware or software double-buffering The default set of visuals on the HP VISUALIZE-FX mode setting. In non-stereo mode, the following visuals are enabled by default on the HP VISUALIZE-FX VISUALIZE-FX • Class PseudoColor Depth 8 Layer Image- supports DBE hardware double-buffering •...
  • Page 69 In stereo mode, the following visuals are enabled by default on the HP VISUALIZE-FX4 and HP VISUALIZE-FX6: • Class PseudoColor Depth 8 Layer Image - supports DBE hardware double-buffering • Class PseudoColor Depth 8 Layer Overlay - supports DBE software double-buffering •...
  • Page 70: Supported Screen Options

    • ImageTextViaBitMap • EnableIncludeInferiorsFix • Enable12BitPseudoColorVisual • DisableGlxVisuals The following additional screen options are supported on the HP VISUALIZE-FX2, HP VISUALIZE- FX4 (stereo mode) and HP VISUALIZE-FX6 (stereo mode): • Disable12BitDirectColorVisual • Disable12BitTrueColorVisual The following additional screen options are supported on the HP VISUALIZE-FX4 (non-stereo mode) and HP VISUALIZE-FX6 (non-stereo mode): •...
  • Page 71 */ XFree(pVisuals); This program segment is not complete; however, its main purpose is to give an idea of how to find an overlay visual having transparency. Page 71 Graphics Administration Guide for HP-UX 10.20...
  • Page 72 The HP VISUALIZE-FX2/4/6 products are the first set of HP graphics devices that supports the OpenGL extension to X (GLX). If HP OpenGL is installed on an HP VISUALIZE-FX2/4/6 system, then the GLX extension offers new entry points for obtaining more information about X visuals. As part of offering extended visual information, some extra X visuals appear in the X visual list.
  • Page 73: Hp Visualize-Fxe, Fx5 And Fx10 Device-Dependent Information

    Disable 12 Bit Direct Color Visual This section includes information on the HP VISUALIZE-FXE, FX5 and FX10 graphics devices. The HP VISUALIZE-FXE/5/10 has 8 overlay planes, 48 image planes a 24-bit z buffer and 4 hardware colormaps. HP VISUALIZE-FXE/5/10 graphics devices contain 2D hardware acceleration similar to that in other HP VISUALIZE devices, as well as 3D acceleration for lighting, shading and texture mapping.
  • Page 74: Hp Visualize-Fxe/5/10 Configuration Hints

    SERVER_OVERLAY_VISUALS property. Disabling the GLX Visuals The HP VISUALIZE-FXE/5/10 products support the OpenGL extension to X (GLX). If HP OpenGL is installed on anHP VISUALIZE-FXE/5/10 system, then the GLX extension offers new entry points for obtaining more information about X visuals. As part of offering extended visual information, some extra X visuals appear in the X visual list.
  • Page 75: Freedom Series Graphics Device-Dependent Information

    This sections describes support for the Freedom Series from Evans & Sutherland on Hewlett-Packard workstations. ____________________________________________________________________________________ Note: The Freedom Series is no longer supported as of HP-UX 10.20 Workstation ACE (July, 1997); the information below is presented for those who are running previous versions of the operating system. ____________________________________________________________________________________...
  • Page 76 640X512 stereo2 1280X512 640X480 video60 1280X1024 video76 1280X1024 Page 76 Graphics Administration Guide for HP-UX 10.20 Description U.S. composite TV format with CVO* European composite TV format with CVO* Description U.S. composite TV format European composite TV format 60 Hz interlaced...
  • Page 77: Vrx Device-Dependent Information

    In image mode, the X server runs only in the image planes. This is the default on VRX devices. To operate in image mode, the image device file should be specified as the primary screen device. For example: /dev/crt # Image mode Page 77 Graphics Administration Guide for HP-UX 10.20...
  • Page 78 The VRXSecondaryDevice is used for this purpose. For example: /dev/ocrt /dev/crt # default visual lives in overlay planes /dev/crt /dev/ocrt # default visual lives in image planes Page 78 Graphics Administration Guide for HP-UX 10.20...
  • Page 79: Chapter 4: X Windows Configuration Details

    X3.hosts file. Both are referenced by the server when it is started with a /usr/bin/X11/X :3 command. If you use a special X*screens file, you need to set your DISPLAY variable appropriately. For the previous example, it would be set to hostname:3.0. Page 79 Graphics Administration Guide for HP-UX 10.20...
  • Page 80: Using An /Etc/Hosts File

    How the X Server Chooses the Default Keyboard and Pointer The X server can access input devices through any of the above interfaces. Devices that use the hp-HIL interface and devices that use the DIN interface and are compatible with the hp DIN keyboard and mouse can be used by simply plugging them into the computer.
  • Page 81: Devices File

    X keyboard and pointer device. If no explicit specification is made through the X*devices file, the last mouse (the one farthest from the computer on the hp-HIL line) is used as the X pointer and the last keyboard is used as the X keyboard.
  • Page 82: Explicitly Specifying Input Device Use

    X pointer or keyboard. This configuration is done by adding information to the X*devices file. There is one syntax to use for hp-HIL devices, and another syntax for devices that require a device driver to be loaded by the X server (such as RS-232 devices).
  • Page 83 Separate the parts of your entry with tabs or spaces. The position of an input device on the hp-HIL is relative to other devices of the same type. For example if you have two keyboards, a graphics tablet, and a mouse connected, they are referred to as "first keyboard", "second keyboard", "first tablet", and "first mouse".
  • Page 84 The X server interprets "first" to mean "first accessible", so you may not always get the first on the hp-HIL, just the first one not already in use. Selecting Values for X*devices Files...
  • Page 85: Specifying Hp-Hil Input Device Use By Device File Name

    Describes the device. Comments are optional, but if present, must be preceded by a "#". This syntax should be used if more than one X server will be running on the computer, or if non-X programs will be accessing the input devices. It refers to a specific position on the hp-HIL. Page 85...
  • Page 86: Redefining The Hp-Hil Search Path

    Redefining the hp-HIL Search Path The X*devices file can be used to redefine the path searched for hp-HIL devices. By default, the path searched is /dev/hil. The device files are named by appending the numbers "1" through "7" to the path.
  • Page 87: Initializing The Colormap With Xinitcolormap

    "94c4d0" is a color specified in the application running. If this occurs, it means that you have probably reached the limit of colors for your graphics card/display combination. Executing xinitcolormap may solve the problem. For more information about xinitcolormap, refer to its reference page. Page 87 Graphics Administration Guide for HP-UX 10.20...
  • Page 88: Customizing The Mouse And Keyboard

    Button 2 Both buttons simultaneously Button 3 Left button Button 4 Button 5 Page 88 Graphics Administration Guide for HP-UX 10.20 Button on a 3-button Mouse Left button Middle button Right button Left and middle buttons simultaneously Middle and right buttons...
  • Page 89: Going Mouseless With The X*Pointerkeys File

    To go mouseless, you need to have the proper configuration specified in the X*devices file and to have a special configuration file named X*pointerkeys. The default X*pointerkeys file is X0pointerkeys in /usr/lib/X11. Page 89 Graphics Administration Guide for HP-UX 10.20 (2 button mouse) (3 button mouse) 2 button mouse...
  • Page 90 X*pointerkeys file is the file that specifies which keys are used to move the pointer when you use the keyboard as the pointer. The default key assignments are listed in the tables in the following section on customizing the X*pointerkeys file. Page 90 Graphics Administration Guide for HP-UX 10.20...
  • Page 91 You can assign keyboard keys to pointer directions by specifying options in an X*pointerkeys file. The following table lists the pointer movement options, the X*pointerkeys functions that control them, and their default values: Page 91 Graphics Administration Guide for HP-UX 10.20...
  • Page 92 You can assign keyboard keys to mouse button operations by specifying options in a X*pointerkeys file. The following table lists the button operations, the X*pointerkeys functions that control them, and their default values: Page 92 Graphics Administration Guide for HP-UX 10.20 Function Default Key pointer_left_key...
  • Page 93 Moving the puck or stylus into the left or right area will cause the X server to switch to the previous or next screen. Page 93 Graphics Administration Guide for HP-UX 10.20 Function Default Key...
  • Page 94 "B" size tablet, the following lines could be added to the X*pointerkeys file: tablet_subset_xorigin 68 tablet_subset_yorigin 40 tablet_subset_width tablet_subset_height 216 Page 94 Graphics Administration Guide for HP-UX 10.20 Function Default Action button_chording On for devices with two buttons, off for devices with more than...
  • Page 95 10 pixels, you would press the would press the key on the keypad. Page 95 Graphics Administration Guide for HP-UX 10.20 keys, the two key on the keypad. To press mouse button 1 you keys, and the...
  • Page 96 Now, suppose you want to use the arrow keys to operate the pointer, and you also need the arrow keys to control the cursor in an hpterm window. Furthermore, another application uses the shift-arrow key sequence to control its cursor. Page 96 Graphics Administration Guide for HP-UX 10.20 left_extend left_shift control...
  • Page 97: Customizing Keyboard Input

    Displays a brief description of the syntax for modification expressions. -verbose Prints log information as xmodmap executes. Page 97 Graphics Administration Guide for HP-UX 10.20 moves the cursor up in the program you frequently operate. moves the pointer up. Keyboards" for more information on using these keyboards and...
  • Page 98: Specifying Key Remapping Expressions

    (such as Lock = Shift_R and Lock = Shift_L), and you can associate more than one modifier with a key symbol (for example, Control = Caps_Lock and Lock = Caps_Lock). Page 98 Graphics Administration Guide for HP-UX 10.20 Valid xmodmap Expressions Use this expression...
  • Page 99 "unswapper" file into effect by entering the following command line: xmodmap unswapper ____________________________________________________________________________________ On a larger scale, you can change your current keyboard to a Dvorak keyboard by creating a file with the appropriate keyboard mappings. xmodmap .keymap Page 99 Graphics Administration Guide for HP-UX 10.20...
  • Page 100: Using The Keyboards

    Equivalent keys are those keys that are mapped to the same key symbol. One advantage of this mapping is that if a key does not physically exist on a keyboard, its equivalent key symbol can be mapped to some other key through the corresponding keycode. Page 100 Graphics Administration Guide for HP-UX 10.20...
  • Page 101: Default Keyboard Mapping

    When the mapping is changed, the X Server notifies all clients that are executing at that time. Some clients may load the new mapping from the server right away, but others Page 101 Graphics Administration Guide for HP-UX 10.20 Default Key Symbol blank1...
  • Page 102 The xmodmap client can be used to determine the keycode-to-key symbol mapping of existing keys, and it can also be used to assign the key symbol to the desired keycode. These keys use hp specific key symbol names whose correct spelling can be found in the file /usr/lib/X11/XKeysymDB.
  • Page 103: Compatibility Considerations

    PowerShade fileset has been installed on your system. • If your hp-UX 9.x application uses hp VMX and it is designed to send output to an X terminal, you need to have PowerShade installed on your hp-UX 10.x system.
  • Page 104: Re-Installing Powershade

    (product name, device driver and capabilities supported) by executing /opt/graphics/common/bin/graphinfo which is a utility installed with hp-UX. For a detailed description of this utility, see the manpage on graphinfo(1G) in the Starbase Reference Manual. ____________________________________________________________________________________ hp has optimized graphics performance for many typical cases.
  • Page 105: Texture Mapping

    • Starbase DECAL and the texture does not have ALPHA in it. (Starbase) You can also resort to software texturing when you run into texture-memory space limitations or run out of texture IDs. Page 105 Graphics Administration Guide for HP-UX 10.20...
  • Page 106: Hp Pex Graphics Performance

    Frequent changes of modal state, such as: o Frequent switching between two or more active Renderers o Frequent mixing of Xlib and hp PEXlib calls • Redundant or unnecessary setup (e.g. setting attributes that are not relevant to the primitives being drawn) •...
  • Page 107 PEXPolylineSetWithData (multiple sets) • Single short polylines: o PEXPolyline, PEXOCCPolyline Page 107 Graphics Administration Guide for HP-UX 10.20 Window Conditions Factors Affecting Performance: • Window obscured by many other image plane windows • Backing store enabled (on supported...
  • Page 108 • Best: simple text: o PEXText, PEXText2D, PEXEncodedText, PEXEncodedText2D • Fair: annotation text: o PEXAnnotationText, PEXAnnotationText2D Page 108 Graphics Administration Guide for HP-UX 10.20 Polymarker Primitives Factors Affecting Performance: • Color per vertex (PEXColorTypeIndexed, PEXColorTypeRGB) • Color approximation type PEXColorRange...
  • Page 109: Hp-Phigs Graphics Performance

    Frequent changes of modal state, such as: HLHSR mode or ID Colour mapping method Light sources enabled Depth cueing state o Frequent switching between two or more active workstations o Frequent mixing of Xlib and hp- PHIGS calls...
  • Page 110 • Polyline sets with multiple disjoint sets: o pgdp_u14 (C), pu014 (FORTRAN) o Plus those noted above with multiple sets Page 110 Graphics Administration Guide for HP-UX 10.20 Window Conditions Factors Affecting Performance: • Window obscured by other image plane windows •...
  • Page 111 • ptext (C), ptx (FORTRAN) • Fair: annotation text: • panno_text_rel3 (C), patr3 (FORTRAN) panno_text_rel (C), patr (FORTRAN) Page 111 Graphics Administration Guide for HP-UX 10.20 Polymarker Primitives Factors Affecting Performance: • These vertex data: o Indirect colour o RGB colour •...
  • Page 112 • View clipping on • Isotropic modeling matrix (angle- preserving) • shade_mode set to CMAP_FULL Page 112 Graphics Administration Guide for HP-UX 10.20 Optimized vs. Normal 3D Performance Factors Affecting Performance: Rendering Conditions • A total of more than 8 directional and...
  • Page 113 Performance Optimized For: • Best: polyline3d and polyline_with_data3d with or without move/draw flags, many vertices per call Page 113 Graphics Administration Guide for HP-UX 10.20 Window Conditions Factors Affecting Performance: • Window obscured by many other image plane windows • Backing store enabled (on supported...
  • Page 114 Performance Optimized For: • Many markers per polymarker3d or polymarker_with_data3d Performance Optimized For: • Longer strings Page 114 Graphics Administration Guide for HP-UX 10.20 Polymarker Primitives Factors Affecting Performance: • These vertex formats: o RGB/vertex o Indirect color o Intensity •...
  • Page 115: 3D Thread-Safing

    This documentation is not a tutorial on threads programming or multiprocessing application issues. For more, and general, information about the use of POSIX threads, consult the hp-UX documentation set. Further restrictions on use of these APIs in multi-threaded programs are: •...
  • Page 116: Sigalrm Details

    • Alarm signals from timers set in other threads do not have the desired effect (because the graphics signal handler is in place); • Unpredictable results due to concurrent use of the process-wide timer provided by setitimer(2). Page 116 Graphics Administration Guide for HP-UX 10.20...
  • Page 117: Sigchld And The Grm Daemon

    The Graphics Resource Manager Daemon (grmd) is started when the X11 Server is started. In normal operation, a Starbase, hp PEX, or hp-PHIGS application will not start the daemon, and so will not be affected by the SIGCHLD manipulation that occurs as part of that startup (see below). However, if the grmd dies for some reason, the graphics libraries will restart the daemon whenever they need shared memory.
  • Page 118: Sigchld And The Starbase Input Daemon

    The graphics libraries start a daemon process and communicate with that process via sockets in two situations: • For hardware texture mapping on an hp VISUALIZE-48/-48XP display using the Texture Interrupt Manager Daemon (timd). • For hp-PHIGS input using the PHIGS daemon (phg_daemon).
  • Page 119: Why Is Gamma Correction Needed

    Once the brightness and contrast of your monitor are adjusted properly (see below), you can run the gamma correction tool (also described below) to see its effect on the test patterns above. Page 119 Graphics Administration Guide for HP-UX 10.20...
  • Page 120: Monitor Brightness And Contrast

    In a terminal window, go to your home directory and follow these steps: 1. Execute this command: cp /opt/graphics/common/icons/Gamma.* $HOME/.dt/icons/ 2. Select the Applications Icon on the CDE Front Panel. 3. Double click the 4. Double click the Page 120 Graphics Administration Guide for HP-UX 10.20 "Desktop_Apps" button. "Create Action" button.
  • Page 121 Enter /opt/graphics/common/bin/gamma in the "Command When Action is Opened" window. Click "Find Set..." and double click on the .dt/icons directory under your home directory. Select the "Gamma Icon" so your form appears as shown below: Figure 14: Create Action Form Page 121 Graphics Administration Guide for HP-UX 10.20...
  • Page 122 Figure 17: Home Folder after dragging the Gamma Icon to the Install Icon If you would prefer to have the "Gamma Icon" in the Main Panel, double-click the right mouse button. Page 122 Graphics Administration Guide for HP-UX 10.20 Figure 15: Home folder icon 1. Home Folder Icon 2.
  • Page 123: Using The Gamma Correction Tool

    When you press "Select A Window," the cursor changes to a crosshair. Next, move the crosshair into the window you wish to modify and click the left mouse button. You will be able to control the gamma value for the colormap associated with the selected window. Page 123 Graphics Administration Guide for HP-UX 10.20...
  • Page 124: Hp Cde And Hp Vue

    PEX, Starbase, and hp-PHIGS use GRM shared memory for VM double-buffering. If your application is running on a low-end graphics system (for example, an hp 710 or 712), you set the environment variable hp_VM_DOUBLE_BUFFER (or SB_710_VM_DB), and you have several large double-buffered windows open simultaneously, then your application could use up available GRM shared memory.
  • Page 125: Reference Documentation

    You can prevent this problem by changing with Shared Memory size through hp-UX's SAM (System Administration Manager) program. Reference Documentation You may find the following documentation helpful when using hp graphics products: • For Starbase programming • Starbase Reference • Starbase Graphics Techniques •...
  • Page 126: Synopsis

    (xauth and xhost), user preference setting programs (xrdb, xcmsdb, xset, xsetroot, xstdcmap, and xmodmap), a load monitor (xload), clocks (xclock and oclock), a font displayer (xfd), utilities for listing information about fonts, windows, and displays (xlsfonts, xfontsel, xwininfo, xlsclients, xdpyinfo, Page 126 Graphics Administration Guide for HP-UX 10.20...
  • Page 127: Starting Up

    Hewlett-Packard provides a graphical user environment called The Common Desktop Environment (CDE). hp CDE is the user interface, enabling the user to control a workstation by directly manipulating graphic objects instead of typing commands on a command-line prompt. See the CDE User's Guide for complete information on hp CDE.
  • Page 128: Display Names

    X servers listen for connections on a variety of different communications channels (network byte streams, shared memory, etc.). Since there can be more than one way of contacting a given server, the Page 128 Graphics Administration Guide for HP-UX 10.20...
  • Page 129: Access Control

    ____________________________________________________________________________________ Page 129 Graphics Administration Guide for HP-UX 10.20...
  • Page 130: Geometry Specifications

    The bottom edge of the window is to be yoff pixels above the bottom edge of the screen. yoff may be negative, in which case the window's bottom edge will be off the screen. Page 130 Graphics Administration Guide for HP-UX 10.20...
  • Page 131: Window Managers

    The list of places the server looks when trying to find a font is controlled by its font path. Although most installations will choose to have Page 131 Graphics Administration Guide for HP-UX 10.20...
  • Page 132 This will usually list the same font at many different sizes. To see just the base scalable font names, try using one of the following patterns: -*-*-*-*-*-*-0-0-0-0-*-0-*-* -*-*-*-*-*-*-0-0-75-75-*-0-*-* -*-*-*-*-*-*-0-0-100-100-*-0-*-* Page 132 Graphics Administration Guide for HP-UX 10.20...
  • Page 133: Font Server Names

    X server's database. The text form of this database is commonly stored in the file /usr/lib/X11/rgb.txt. A numerical color specification consists of a color space name and a set of values in the following syntax: color_space_name:value/.../value Page 133 Graphics Administration Guide for HP-UX 10.20...
  • Page 134 Xlib before being sent to the X server. The input format for these values is an optional sign, a string of numbers possibly containing a decimal point, and an optional exponent field containing an "E" or "e" followed by a possibly signed integer string. Page 134 Graphics Administration Guide for HP-UX 10.20...
  • Page 135: Keyboards

    NoSymbol, then the group is treated as equivalent to a group in which the first element is the lowercase letter and the second element is the uppercase letter. Page 135 Graphics Administration Guide for HP-UX 10.20...
  • Page 136: Options

    It is usually only used on monochrome displays. This option indicates that the program should not simulate reverse video. This is used to override any defaults since reverse video doesn't always work properly. Page 136 Graphics Administration Guide for HP-UX 10.20...
  • Page 137: Resources

    Elements separated by vertical bar ("|") are alternatives. Braces ("{"..."}") indicate zero or more repetitions of the enclosed elements. Brackets ("["..."]") indicate that the enclosed element is optional. Quotes ("...") are used around literal characters. Page 137 Graphics Administration Guide for HP-UX 10.20...
  • Page 138 "?". An entry with a matching class takes precedence over entries that match using "?". An entry preceded by a tight binding takes precedence over entries preceded by a loose binding. Page 138 Graphics Administration Guide for HP-UX 10.20...
  • Page 139 This resource specifies the color to use for the window border. Most applications using the X Toolkit Intrinsics also have the resource foreground (class Foreground), specifying the color to use for text and graphics within the window. Page 139 Graphics Administration Guide for HP-UX 10.20...
  • Page 140 This is frequently how user-friendly startup scripts merge user-specific defaults into any site-wide defaults. All sites are encouraged to set up convenient ways of automatically loading resources. See the Xlib manual section "Resource Manager Functions" for more information. Page 140 Graphics Administration Guide for HP-UX 10.20 gold 33:48,37:48,45-47:48,64:48 gold...
  • Page 141: Examples

    .Xdefaults file in the user's home directory. This file is then loaded into the RESOURCE_MANAGER property using the xrdb program: *StringConversionWarnings: on To have conversion messages printed for just a particular application, the appropriate instance name can be placed before the asterisk: xterm*StringConversionWarnings: on Page 141 Graphics Administration Guide for HP-UX 10.20...
  • Page 142: See Also

    Consortium), Stephen Gildea (MIT X Consortium), Susan Hardy (MIT X Consortium), Jay Hersh (MIT X Consortium), Keith Packard (MIT X Consortium), David Sternlicht (MIT X Consortium), Bob Scheifler (MIT X Consortium), and Ralph Swick (Digital/MIT Project Athena). Page 142 Graphics Administration Guide for HP-UX 10.20...
  • Page 143: Appendix B: X Server Reference Page

    DISPLAY environment variable is set to "local:*" or ":*" where "*" is the number of the display. Currently, SMT is not enabled by default. Please see /etc/X11/X0screens and/or /usr/lib/X11/Xserver/info/screens/hp for more information about SMT. When the server starts up, it takes over the display. If you are running on a workstation whose console is the display, you cannot log into the console while the server is running.
  • Page 144: Options

    Sets the search path for fonts. This path is a comma-separated list of directories which the server searches for font databases. -help Prints a usage message. Causes all remaining command-line arguments to be ignored. Page 144 Graphics Administration Guide for HP-UX 10.20...
  • Page 145 Sets video-off screen-saver preference. The screen will be blanked to save the screen. Forces the default backing-store of all windows to be WhenMapped; a less expensive way of getting backing-store to apply to all windows. Page 145 Graphics Administration Guide for HP-UX 10.20...
  • Page 146 This option sets the value of that private data (not that it's very private, being on the command line and all. . .). -displayID <display-id> Yet another XDMCP specific value, this one allows the display manager to identify each display so that it can locate the shared key. Page 146 Graphics Administration Guide for HP-UX 10.20...
  • Page 147: Security File Format

    Once past the <version line>, lines that do not match the above syntax are ignored. <comment lines> are ignored. Page 147 Graphics Administration Guide for HP-UX 10.20 ::= <version line> <other line> * ::= <string/v> 'n' ::= <comment> | <access rule> | <site policy> | <blank line>...
  • Page 148 BadAtom error with the atom set to the property name. Error is the default action for all properties, including those not listed in the security policy file. Page 148 Graphics Administration Guide for HP-UX 10.20 r, or r and d if delete=True r and w...
  • Page 149 # Allow read of WM_CLASS, but only for windows with WM_NAME. # This might be more restrictive than necessary, but demonstrates # the <required property> facility, and is also an attempt to Page 149 Graphics Administration Guide for HP-UX 10.20 root ar iw root ar iw root ar iw...
  • Page 150 # Allow deletion of Woo-Hoo if window also has property OhBoy with value # ending in "son". Reads and writes will cause an error. property Woo-Hoo OhBoy = "*son" ad Page 150 Graphics Administration Guide for HP-UX 10.20 WM_NAME ar WM_NAME ar root ar root ar...
  • Page 151: Running From Init

    See the Xau manual Page 151 Graphics Administration Guide for HP-UX 10.20 -n login -L ttyqf -- :0 TAB3...
  • Page 152: Signals

    SIGUSR1 to its parent process after it has set up the various connection schemes. Xdm uses this feature to recognize when connecting to the server is possible. Page 152 Graphics Administration Guide for HP-UX 10.20 All hosts being allowed (access control disabled) All hosts being restricted (access control enabled) Access control enabled;...
  • Page 153: Fonts

    <port-number> is the tcp address that the font server is listening at (typically 7000). Diagnostics Too numerous to list them all. If run from CDE, errors are logged in the file /var/dt/Xerrors. Page 153 Graphics Administration Guide for HP-UX 10.20...
  • Page 154: Files

    RGB values. Copyright Copyright 1996, 1998 The Open Group Copyright 1984-1992 Massachusetts Institute of Technology Copyright 1992 Hewlett Packard Company See X(1) for a full statement of rights and permissions. Origin MIT Distribution Page 154 Graphics Administration Guide for HP-UX 10.20...
  • Page 155: See Also

    See Also dtlogin(1), bdftopcf(1), fs(1), getty(1M), gettydefs(4), gwindstop(1), hpterm(1), init(1M), inittab(4), mkfontdir(1), rgb(1), stmkdirs(1), x11start(1), xauth(1) clock(1), xfd(1), xhost(1), xinit(1), xinitcolormap(1), xload(1), xmodmap(1), xrefresh(1), xseethru(1), xset(1), xsetroot(1), xterm(1), xwcreate(1), xwd(1), xwdestroy(1), xwininfo(1), xwud(1) Page 155 Graphics Administration Guide for HP-UX 10.20...
  • Page 156: Appendix C: Low Bandwidth X Proxy

    .Xauthority file contain entries with valid keys associated with the network ID of the proxy. lbxproxy does not get involved with how these entries are added to the .Xauthority file. The user is responsible for setting it up. Page 156 Graphics Administration Guide for HP-UX 10.20...
  • Page 157 -reconnect option will cause lbxproxy to just reset instead (see -reset above) and attempt to reconnect to the server. Causes all remaining arguments to be ignored. -nolbx Disables all LBX optimizations. -nocomp Disables stream compression. -nodelta Disables delta request substitutions. -notags Disables usage of tags. Page 157 Graphics Administration Guide for HP-UX 10.20...
  • Page 158 -cheaterrors option allows lbxproxy to violate X protocol rules with respect to errors. Use at your own risk. -cheatevents The -cheatevents option allows lbxproxy to violate X protocol rules with respect to events as well as errors. Use at your own risk. Page 158 Graphics Administration Guide for HP-UX 10.20...
  • Page 159: Atom Control

    A client must be on the same host as lbxproxy for the client to be authorized to connect to the server. If a client is not on the same host as lbxproxy, the client will not be authorized to connect to the server. Origin The Open Group See Also proxymngr(1), xfindproxy(1) Page 159 Graphics Administration Guide for HP-UX 10.20...
  • Page 160: Appendix D: Rx Netscape Navigator Plug-In

    Generally you simply need to remove or comment out the line you may have previously added in your mailcap file to use the RX helper program. Otherwise the plugin will not be enabled. (The usual comment character for mailcap is #.) Page 160 Graphics Administration Guide for HP-UX 10.20...
  • Page 161: Resources

    The web servers from which remote applications should be run as trusted clients. The default is to run remote applications as untrusted clients. The resource value is a list of address mask/value pairs, as previously described. Page 161 Graphics Administration Guide for HP-UX 10.20 RX Plugin Suffixes Enabled...
  • Page 162: Environment

    However, if the plugin does not get destroyed properly, which happens when Netscape Navigator dies unexpectedly, the print authorization key will never get revoked. Origin The Open Group See Also xrx(1), lbxproxy(1), proxymngr(1) Page 162 Graphics Administration Guide for HP-UX 10.20...
  • Page 163: Appendix E: Proxy Manager Service

    Sets the maximum number of retries made by the proxy manager to find an unmanaged proxy. The default is 3. -verbose Causes various debugging and tracing records to be displayed as requests are received and proxies are started. Page 163 Graphics Administration Guide for HP-UX 10.20...
  • Page 164: Proxy Manager Config File

    If desired, <command-to-start-proxy> can be used to start a proxy on a remote machine. The specifics of the remote execution method used to do this is not specified here. Page 164 Graphics Administration Guide for HP-UX 10.20...
  • Page 165: Example

    The proxy manager listen port should be configurable. -timeout and -retries are not implemented in proxymngr. proxymngr does not utilize the "options" and "host" fields in the proxy management protocol GetProxyAddr request. Page 165 Graphics Administration Guide for HP-UX 10.20...
  • Page 166: Origin

    Origin The Open Group See Also xfindproxy(1), lbxproxy(1) Page 166 Graphics Administration Guide for HP-UX 10.20...
  • Page 167: Appendix F: Locate Proxy Services

    The semantics of the options are specific to each proxy server and are not defined here. In the event that xfindproxy locates an already existing proxy, the options will be passed, but the semantics of how the proxy uses these options are undefined. Page 167 Graphics Administration Guide for HP-UX 10.20...
  • Page 168: Origin

    X display address of the proxy (e.g, "info.x.org:63"). If xfindproxy is unsuccessful in obtaining a proxy address, it will print an error to stderr. Origin The Open Group See Also proxymngr(1), lbxproxy(1) Page 168 Graphics Administration Guide for HP-UX 10.20...
  • Page 169: Appendix G: Rx Helper Program

    However, you may need to refer to your web browser's documentation for exact instructions on configuring helper applications. Once correctly configured, your browser will activate the helper program whenever you retrieve any document of the MIME type application/x-rx. Page 169 Graphics Administration Guide for HP-UX 10.20...
  • Page 170: Options

    X Print server address to use. If the server address is not specified as part of XPRINTER, <xrx> uses the first one specified through the variable XPSERVERLIST when it is set. When it is not xrx Page 170 Graphics Administration Guide for HP-UX 10.20...
  • Page 171: Notes

    (that is when its video key expires). However, if the helper program dies unexpectedly the print authorization key will never get revoked. Origin The Open Group See Also libxrx(1), lbxproxy(1), proxymngr(1) Page 171 Graphics Administration Guide for HP-UX 10.20...

Table of Contents