HP (Hewlett-Packard) HP-UX manuel d'utilisation

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171

Aller à la page of

Un bon manuel d’utilisation

Les règles imposent au revendeur l'obligation de fournir à l'acheteur, avec des marchandises, le manuel d’utilisation HP (Hewlett-Packard) HP-UX. Le manque du manuel d’utilisation ou les informations incorrectes fournies au consommateur sont à la base d'une plainte pour non-conformité du dispositif avec le contrat. Conformément à la loi, l’inclusion du manuel d’utilisation sous une forme autre que le papier est autorisée, ce qui est souvent utilisé récemment, en incluant la forme graphique ou électronique du manuel HP (Hewlett-Packard) HP-UX ou les vidéos d'instruction pour les utilisateurs. La condition est son caractère lisible et compréhensible.

Qu'est ce que le manuel d’utilisation?

Le mot vient du latin "Instructio", à savoir organiser. Ainsi, le manuel d’utilisation HP (Hewlett-Packard) HP-UX décrit les étapes de la procédure. Le but du manuel d’utilisation est d’instruire, de faciliter le démarrage, l'utilisation de l'équipement ou l'exécution des actions spécifiques. Le manuel d’utilisation est une collection d'informations sur l'objet/service, une indice.

Malheureusement, peu d'utilisateurs prennent le temps de lire le manuel d’utilisation, et un bon manuel permet non seulement d’apprendre à connaître un certain nombre de fonctionnalités supplémentaires du dispositif acheté, mais aussi éviter la majorité des défaillances.

Donc, ce qui devrait contenir le manuel parfait?

Tout d'abord, le manuel d’utilisation HP (Hewlett-Packard) HP-UX devrait contenir:
- informations sur les caractéristiques techniques du dispositif HP (Hewlett-Packard) HP-UX
- nom du fabricant et année de fabrication HP (Hewlett-Packard) HP-UX
- instructions d'utilisation, de réglage et d’entretien de l'équipement HP (Hewlett-Packard) HP-UX
- signes de sécurité et attestations confirmant la conformité avec les normes pertinentes

Pourquoi nous ne lisons pas les manuels d’utilisation?

Habituellement, cela est dû au manque de temps et de certitude quant à la fonctionnalité spécifique de l'équipement acheté. Malheureusement, la connexion et le démarrage HP (Hewlett-Packard) HP-UX ne suffisent pas. Le manuel d’utilisation contient un certain nombre de lignes directrices concernant les fonctionnalités spécifiques, la sécurité, les méthodes d'entretien (même les moyens qui doivent être utilisés), les défauts possibles HP (Hewlett-Packard) HP-UX et les moyens de résoudre des problèmes communs lors de l'utilisation. Enfin, le manuel contient les coordonnées du service HP (Hewlett-Packard) en l'absence de l'efficacité des solutions proposées. Actuellement, les manuels d’utilisation sous la forme d'animations intéressantes et de vidéos pédagogiques qui sont meilleurs que la brochure, sont très populaires. Ce type de manuel permet à l'utilisateur de voir toute la vidéo d'instruction sans sauter les spécifications et les descriptions techniques compliquées HP (Hewlett-Packard) HP-UX, comme c’est le cas pour la version papier.

Pourquoi lire le manuel d’utilisation?

Tout d'abord, il contient la réponse sur la structure, les possibilités du dispositif HP (Hewlett-Packard) HP-UX, l'utilisation de divers accessoires et une gamme d'informations pour profiter pleinement de toutes les fonctionnalités et commodités.

Après un achat réussi de l’équipement/dispositif, prenez un moment pour vous familiariser avec toutes les parties du manuel d'utilisation HP (Hewlett-Packard) HP-UX. À l'heure actuelle, ils sont soigneusement préparés et traduits pour qu'ils soient non seulement compréhensibles pour les utilisateurs, mais pour qu’ils remplissent leur fonction de base de l'information et d’aide.

Table des matières du manuel d’utilisation

  • Page 1

    Graphics Administration Guide for HP-UX 10.20. After using this docu ment for a while, please f ill 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

    ABOUT THIS GUIDE ............................................................................................................... ............................................... 6 PREFACE ...................................................................................................................................................................[...]

  • Page 3

    Supported Visuals .............................................................................................................. .............................................. 51 Supported Scre en Options ....................................................................................................... .........................................[...]

  • Page 4

    R E -I NSTALLING P OWER S HADE ............................................................................................................................... ............. 104 3D G RAPHICS P ERFORMANCE ............................................................................................................................... ............... 104[...]

  • Page 5

    APPENDIX C: LOW BANDWIDTH X PROXY .............................................................................................. ................. 156 N AME ............................................................................................................................... ................................................... 156 S YNOPSIS[...]

  • Page 6

    About this Guide Graphics Administration Guide: Information for Programmers, System Adm inistrators, and End-Users Copyright © June 1997, June 1998, June 2000 Hewlet t-Packard Company HP 9000 Workstations Notices The information contained in this document is subject to change without notice. Hewlett-Packard provides the f ollowi ng material "[...]

  • Page 7

    Printing History New editions of this manual will incorporate all ma terial upd ated since the previous edition. Update packages may be issued between editions and cont ain repla c ement and additional pa ges to be merged into the manual by the us er. Each updated page will be indicated by a revision date at the bottom of the page. A vertical bar i[...]

  • Page 8

    Preface Why This Document? This document was created to fill a need that bec ame evident as Hewlett-Packard began to of fer multiple Application Programmer Interfaces (APIs). The situation was this : As HP created one API, say, Starbase, particular aspects of gra phical operation were noted and dili gently explained in the Starbase documentation. H[...]

  • Page 9

    Document Conventions Below is a list of the typographical conventions used in this document: mknod /usr/include Verbatim computer literals are in computer font. Text in this st yle is letter-for-letter verbatim and, depending on the context, should be typed in exactly as specified, or is named exactly as specified. In every case... Emphasized words[...]

  • Page 10

    Chapter 1: Pathnames This chapter contains information on locating files th at reside at som e locati on in the file system. Using “whence” There are two main m ethods of findi ng files, assuming you know the name of the file you're looking for. The first method is to use the Korn-shell command whence, which tells you where commands reside[...]

  • Page 11

    Subsequent sections of this chapte r contain the actual pa thnames referred to in other HP graphics API documents, such as Starbase, PEX, etc. A pa rticular paragraph mi ght 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 ref[...]

  • Page 12

    HP-PHIGS Generic Name Location in the file system <app-defaults> /usr/lib/X11/app-defaults <common> /opt/graphics/common <dev> /dev <nls> /opt/graphics/common/lib/nls/m sg/C <phigs> /opt/graphics/phigs <phigs-demos> /opt/graphics/phigs/demos <phigs-examples> /opt/graphics/phigs/examples <phigs-incl> /[...]

  • Page 13

    HP PEX Generic Name Location in the file system <app-defaults> /usr/lib/X11/app-defaults <cge-examples> /opt/graphics/PEX5/examples/cge <cge-utils> /opt/graphics/PEX5/utilities/cge <contrib> /opt/graphics/PEX5/contrib <err-help> /opt/graphics/PEX5/help5.1 <extensions> /opt/graphics/PEX5/newconf ig/usr/lib/X11/ext[...]

  • Page 14

    Chapter 2: Compiling Y our Application This chapter provides information for compiling your appl ication with either archiv ed or shared libraries for the following Application Programming Interfaces (APIs): Starb ase, HP-PHIGS, and HP PEX. Compiling examples are given for C, Fortran, and Pascal. The actual pathnames of the conceptu al (< ita li[...]

  • Page 15

    By default, the linker program ld(1) looks for a shared library driver first and then the archive library driver if a shared library was not found. By using "-Wl,-a,archive" (o r exporting the LDOP TS variable), the -l option will refer o nly to archive drivers. Because the archive library libhpgfx1 .a references functionality in libXext.[...]

  • Page 16

    Compiling with Ar chive Libraries If you are using archived libra ries, you need to include your device's driver library. ___________________________________________________________________________________ Note : Shared libraries are used by de fault unless you specify that you want to use archived libraries (by specifying "-Wl,-a,archive[...]

  • Page 17

    Device Driver Libraries The following tables list the device driver librar ies that should be used with particular devices. CRX Family Output Device Link Line Options Integrated Color Graphics (Model 705, 710, 715/33, 715/50, 715/75, 725/50, 725/75) Internal Color Graphics (Model 712/60, 712/80, 712/80i, 712/100, 715/64, 715/80, 715/100, 715/100XC,[...]

  • Page 18

    HP VISUALIZE-FX Family Output Device Link Line Options Legacy APIs HP VISUALIZE-EG libddhcrx.a or libddhcrx.sl HP VISUALIZE-FX2 HP VISUALIZE-FX4 HP VISUALIZE-FX6 libddvisx.a or libddvisx.sl HP VISUALIZE-FXE libddfxe.a or libddfxe.sl OpenGL HP VISUALIZE-EG libddhcrx.sl HP VISUALIZE-FX2 HP VISUALIZE-FX4 HP VISUALIZE-FX6 libddvisxgl.sl libddvmd.sl HP [...]

  • Page 19

    HP-GL Plotters Output Device Link Line Options HP 7440A HP 7470A HP 7475A HP 7550A HP 7570A HP 7575A HP 7576A HP 7580A/B HP 7585B HP 7586B HP 7595A HP 7596A HP 9111A HP C1600A HP C1601A libddhpgl.a libdvio.a or libddhpgl.sl libdvio.sl HP 7510A HP 7550A HP 7570A HP 7575A HP 7576A HP 7580B 1 HP 7585B 1 HP 7586B HP 7595A/B HP 7596A/B HP 7599A HP C1600[...]

  • Page 20

    Miscellaneous Device Drivers Output Device Link Line Options Remote Rendering: Xlib Pixmap (VMX) libddvmx.sl 1 Remote Rendering: Xlib 2D protocol (SOX) libddsox11.a or libddsox11.sl Display List libdddl.a or libdddl.sl Computer Graphics Metafile (CGM) File Format libddhpcgm.a or libddhpcgm.sl Starbase Memory Driver (pixel-major packing orders) libd[...]

  • Page 21

    Compiling HP PEX Applications HP PEXlib is supported on the Series 700 workstations using shared libraries th at must be linked w ith 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 PE Xlib library libPEX5. __________________[...]

  • Page 22

    Chapter 3: X Windows: HP-UX 10.20 This chapter documents information specific to the HP X server. It describes feat ures unique to HP's X server, provides information on how to configure the X server and includ es a list of supported X configurations. For each supported graphics device, device-dependent configuration information is provided. I[...]

  • Page 23

    absent. When only one graphics screen is present, SAM will treat this screen as though it is always configured. Preselecting both configured and unconfigured scre ens will result in only the first two screen menu options being active. X*screens File For manual changes, please refer to the sam ple files in the /etc/X11/ directory. Three f iles of pa[...]

  • Page 24

    composed of an optional block specifying device-i ndependent server options followed by one or more either Screen or Single Logical Screen entr ies (maximum of four graphics devices). The minimum X*screens file is a lin e with the k eyword " Screen " followed by a screen device file. For example: Screen /dev/crt Server Options For more in[...]

  • Page 25

    Layer <Image> | <Overlay> Specify the layer of the default visual. Transparent Specify that a visual with an application-accessibl e transp arent entry in the default colo rmap be used. Specifications in the "Def aultVisual" section, except for "Depth", are ignored on VRX devices. See the "ScreenOptions" se[...]

  • Page 26

    • This is the minimum specification for a two-sc reen configuration. The maxim um number of screens supported on the X server is four. Here , the displays associated with /dev/crt0 and /dev/crt1 are referred to as "<hos t>:0 .0" and "<host>:0.1", respectively. Screen /dev/crt0 Screen /dev/crt1 Figure 2: Two Physica[...]

  • Page 27

    Screen /dev/crt DefaultVisual Transparent The display diagram would be the same as that of the "Results of Minim al Legal X*screens File" configuration, above. • This sample X*screens file could be used on a system with a HCRX-8 graphics device. By default on the HCRX-8, the overlay visual does not have a transparent entry available to [...]

  • Page 28

    SingleLogicalScreen 1 4 /dev/crt0 /dev/crt1 /dev /c rt2 /dev/crt3 Figure 4: Four Physical Displ ays, Single Logical Screen (1X4) SingleLogicalScreen 4 1 /dev/crt0 /dev/crt1 /dev/crt2 /dev/crt3 Figure 5: Four Physical Displ ays, Single Logical Screen (4X1) SingleLogicalScreen 2 2 /dev/crt0 /dev/crt1 /dev/crt2 /dev/crt3 Graphics Administrati on Guide[...]

  • Page 29

    Figure 6: Four Physical Displ ays, Single Logical Screen (2X2) • It is possible to include a Screen Entry and an SLS Screen Entry in the same X*screens File. This creates a situation wher e there are two X Screens (e.g. <host>:0.0 and <host>:1.0 ), one of which happens to be a Single Logical Screen. Below is an example of this: • Sc[...]

  • Page 30

    Miscellaneous Topics Double Buffer Extension (DBE) DBE is an extension to the X server that provides a double-buffering Application Programming Interface (API). ____________________________________________________________________________________ Note : MBX (the M ulti- B uffering e X tension to X) has not been adopted as an industry standard, as DB[...]

  • Page 31

    can be deduced from any of the following: the magnit ude of the difference of two perform ance levels, a performance level in isolation, or comparing performance levels from different servers. For more information, refer to the D BE man page on XdbeScreenVisualInfo() . Supported Devices The X server supports DBE on the following devices: • Intern[...]

  • Page 32

    Power-Saving States Defined by VESA Level State DPMS Compliance Requirements State DPMS Compliance Requirements Power Savings Recovery Time 0 Screen Saver Not Applicable None Very Short (<1 sec) 1 Stand-by Optional Minimal Short 2 Suspend Mandatory Substantial Longer 3 Off Mandatory Maximum System Dependent The actual amount of power saved and t[...]

  • Page 33

    to allow for synchronization with ve rtical retrace. To activate this optional X server m ode, set the SwapBuffersOnVBlank Screen Option in the X*sc reens file before the X server is started. ____________________________________________________________________________________ Note: MBX_SWAP_BUFFERS_ON_VBLANK is obsolete with this rele ase. The Swap[...]

  • Page 34

    Supported Devices The X server supports the MIT shared memo ry extension on the following devices: • Internal Color Graphics • Integrated Color Graphics • CRX-24[Z] • CRX-48Z • HCRX-8[Z] • HCRX-24[Z] • HP VISUALIZE-EG • HP VISUALIZE-8 • HP VISUALIZE-24 • HP VISUALIZE-48[XP] • HP VISUALIZE-FX 2 • HP VISUALIZE-FX 4 • HP VISU[...]

  • Page 35

    A display name of the form unix:0.0 will f o rce th e use of Unix Domain Sockets (UD S), which is identical to the local transport used befo re 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 rem ote transport normally used, and which can be used local[...]

  • Page 36

    In either case, the format and m eaning of the fields is the same: <region_size> [, <high_water> [, <buffer_size> ]] with no em bedded blanks, e.g. 32000,16000,5000 32000 0 Although the default is " SMTSizes 0,0,0, " a specification of " SMTSizes 100000,90000,90000 " is optim al in most situations if SMT is des[...]

  • Page 37

    Enabling and Disabling of SMT The special value of 0 for Region Si ze specifies that SMT is to be disabled. Disabling SMT removes it from the Xserver causing it not to be available fo r any transports. Any non- zero Reg ion Size enables SMT on the Xserver. The default Region Size for a di skless Xserver is zero (disablin g SMT from the Xserver) to [...]

  • Page 38

    HP Color Recovery Color Recovery is a technique that generates a better picture by eliminating the graininess caused by traditional dithe ring tech niques. It is available on these graphics devices: • Integrated Color Graphics and plug-in Color Graphics cards • HP VISUALIZE-EG • HCRX-8[Z], HCRX-24[Z] • HP VISUALIZE-8, HP VISUALIZE- 24, and [...]

  • Page 39

    Dynamic Loadin g HP's X server now dynamically loads the appropriate device drivers and extensi ons based on the target graphics display device and the extensions the device driver supports. This feat ure should be transparent to X server users. When possible, the loading of X extensions is deferre d until the first protocol re quest is encoun[...]

  • Page 40

    For example: Screen /dev/crt/ ScreenOptions EnableIncludeInferiorsFix This gives a system administrato r control over when th e fix is active and when it is not. In this way, each site can evaluate whether or not it is beneficial to en able this fix. Shared Memory Usage With 3D Graphics Graphics processes use shared memory to access data pertaining[...]

  • Page 41

    It is also possible to decrease th e size of GRM shared memory. You ma y want to do this if you want to reduce the swap-space requirements of your system and/or you do not intend to run any 3D graphics processes. For example, you could reduce graphics shared mem ory size to 0x100000 (one megabyte). Count Transparent In Overlay Visual In some config[...]

  • Page 42

    Examples of Relevant Graphics Device: Integrated Color Graphics, Color Graphi cs cards, Internal Color Graphics X*screens File Screen Option To Use: 3BitCenterColor Image Text Via BitMap When using the Xlib XDrawImageString() ca ll to draw text, a visual effect may be seen where text appears to flicker as the backgr ound and foreground are drawn in[...]

  • Page 43

    Special device files are created by using SAM (t he System Adm inistration Manager tool): • From SAM's main window, double- click "Peripheral Devices". • From the "Peripheral Devices" window, double-click "Cards". • A window will appear, containing a list of all cards that are in your machine. Once you selec[...]

  • Page 44

    Multi-Seat A configuration with multiple instantiations of the X server, each with its own m ouse, 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 wi th a single mouse and keybo ard drives multiple homogeneous graphics de[...]

  • Page 45

    Figure 10: Single Logical Screen ____________________________________________________________________________________ Note: Different monitor resolu tions are not suppor ted with the multi-display conf igurations unless stated otherwise in the table below. ____________________________________________________________________________________ Multi-Sc[...]

  • 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 VISU ALIZE-EG graphics device and an HP VISUALIZE-EG graphics card, and still consider them identical devices , thus perm itting[...]

  • Page 47

    ____________________________________________________________________________________ Note: DHA (Direct Hardware Access) is not supported in a window that spans multiple screens. This means, for example, that while graphics is suppor ted to a window spanning two or more screens, accelerated graphics is not. "Spanning," in this co ntex t, i[...]

  • Page 48

    This behavior is the result of HP VUE's naive assum ption that it is running against o ne large screen; it centers these windows accordingly. If you are using the default HP VUE key bindings, you can easily reposition the Fron t Panel so that it is completely contained within on e physical screen: 1. With the input focus on the Front Panel, pr[...]

  • Page 49

    For example, to configure SLS/d slave X servers on hpslsd1 , hpslsd2 , hpslsd3 , and hpslsd4 , do the following as root : • Copy each system's /etc/X11/X0screens file to /etc/X11/X50screens (the use of "50" as the display name is an SLS/d convention only; you can choose any number from 0-99 that m eets your needs). Unless you'[...]

  • Page 50

    Edit the /etc/X11/X0screens file and enter: SingleLogicalScreen 1 4 hpslsd1:50 hpslsd3:50 hpslsd4:50 hpslsd2:50 Then, on the master system, make sure that SLSd_d aem on is running and enter in it state 4 (e.g., as root: /etc/init 4). You will notice all of the slave X servers starting in turn, then finally when the m aster initializes, you will see[...]

  • Page 51

    Integrated Color Graphics D evice-Dependent Information This sections includes in formation on Integr ated Color Graphics and Co lor Graphics cards. Supported Visuals For color displays: • Class PseudoColor Depth 8 - supports DBE and MBX so ftware double-buffering • Class TrueColor Depth 8 - supports DBE and MBX so ftware double-buffering For g[...]

  • Page 52

    a technicolor effect, the applica tion whose colorm ap was last downl oaded in the hardware colormap would look correct. Accessing HP Color Recove ry Technology via Xlib Color Recovery is a technique to generate a better picture by attempting to elim inate the graininess caused by dithering. Access to the Color Recovery capab ility is transparent w[...]

  • Page 53

    A pixel to be dithered is sent to the routine provi ded in this example. The values of the variables RedValue, GreenValue, and BlueValue are generated by an application. In th is example, the color values are assumed to be in the range 0..255. The given routine receives the color values and the X and Y window address (X p and Y p ) of the pixel. Th[...]

  • Page 54

    /* Check for overflow or underflow on green value */ if (green > 0xff) green = 0xff; if (green < 0x00) green = 0x00; /* Generate the blue dither value */ blue += (dither_blue[y_dith er_table][x_dither _table]<<1); /* Check for overflow or underflow on blue value */ if (blue > 0xff) blue = 0xff; if (blue < 0x00) blue = 0x00; /* Gen[...]

  • Page 55

    • CRX-24[Z] Device-Dependent Information Supported Visuals The following visuals are supported: • Class PseudoColor Depth 8 Layer Image - supports DBE and MBX hardware double-buffering • Class PseudoColor Depth 8 Layer Overlay - supports DBE and MBX so ftware double-buffering • Class DirectColor Depth 12 Layer Im age - supports DBE and MBX [...]

  • Page 56

    When this option is enabled, the X se rver does the following: • Specifies that the overlay visual has 256 entries. • Creates the default colormap with entry 255 pr e-allocated to Transparent. A client calling XAllocNamedColor for entry Transparent in the default colorm ap will be returned entry 255. • For all other colormaps, return s all 25[...]

  • Page 57

    • Clients requesting (via XAllocNamedColor) the r gb.txt value of Transparent are not returned entry 255. This default behavior can be changed by setting the CountTransparentInOverlayVisual screen option. When this option is enabled, the X se rver does the following: • Specifies that the overlay visual has 256 entries. • Creates the default c[...]

  • Page 58

    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 optiona l cards, and it becomes a four-board set, but it st ill f ills only thr ee slots. In any case, it has eight o[...]

  • Page 59

    • Class DirectColor Depth 12 Layer Im age - supports DBE and MBX hardware double-buffering • Class TrueColor Depth 12 Layer Image - supports DBE and MBX hardware double-buffering • Class DirectColor Depth 24 Layer Im age - doesn't support DBE and MBX double-buffering • Class TrueColor Depth 24 Layer Image - doesn't support DBE and[...]

  • Page 60

    The modes are set from the Boot-Admin at bootup tim e by selecting from the menu of options a configuration that supports double-buffer or not. From that point on (without reboo ting) the server will use the selected mode. Eight-plane mode is compatible with the Integra te d Color Graphics device. It has eight image planes and uses only software do[...]

  • Page 61

    To obtain hardware double-buffering, find a visual in the image planes. The best m ethod is to find all the depth-8 PseudoColor visuals returned by XGetVisualInfo and then eliminate the visuals that are reported in the SERVER_OVERLAY_VISUALS property (discussed below). If you have an application that assumes the defau lt visual has fast double-buff[...]

  • 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 VISUAL IZE-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 [...]

  • Page 63

    { /* Since the Atom exis ts, request the property's contents. */ bytesAfter = 0; numLongs = ( nVisuals * si zeof(OverlayVisualPropertyRec) + 3 ) / 4; XGetWindowProperty(di splay, RootWindow(display, screen), overlayVisualsAtom, 0, numLongs, False, AnyPropertyType, &act ualType, &actualFormat, &numLongs, &bytesAfter, &pOverl[...]

  • Page 64

    installed in the hardware, plus one other hardware co lormap available to applic ations. The im age planes contain two hardware colormaps each usable by applications. When the default visual is in the image planes an d the screen option EnableOv erlayTransparency is not set, the overlay planes contain a si ngle hardware colormap availab le to appli[...]

  • Page 65

    _HP_RGB_SMOOTH_MAP_LIST is a list of colormaps that are asso ciated with window visual IDs that support Color Recovery. When the XGe tRGBColormaps routine searches th is list for a colormap with a visual ID that matches your window's visual ID and it finds one, your application knows that your visual supports Color Recovery, and uses that colo[...]

  • Page 66

    y_dither_table = Yp % 2; /* Y Pixel Address MOD 2 */ /* Start with the initial valu es as supplied by th e calling routine * / red = RedValue; green = GreenValue; blue = BlueValue; /* Generate the red dither value */ if (red >= 48) /* 48 is a constant required by this routine */ red=red-16; else red=red/2+8; red += dither_red[y_d ither_table] [x[...]

  • Page 67

    HP VISUALIZE-FX (FX 2 , FX 4 and FX 6 ) Device-Dependent Information This section includes information on the HP VISUALIZE-FX 2 , HP VISUALIZE-FX 4 and HP VISUALIZE-FX 6 graphics devices: • The HP VISUALIZE-FX 2 has 8 overlay planes, 24 image planes, a 24-bit Z buffer and 8 hardware colormaps. • The HP VISUALIZE-FX 4 has 8 overlay planes, 48 im[...]

  • Page 68

    The following visuals are enabled by default on the HP VISUALIZE-FX 2 : • Class PseudoColor Depth 8 Layer Image- supports DBE hardware double-buffering • Class PseudoColor Depth 8 Layer Overlay- supports DBE software double-buffering • Class PseudoColor Depth 8 Layer Overlay Transparent- supports DBE software double-buffering • Class TrueCo[...]

  • Page 69

    In stereo mode, the following visuals are enab le d 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 • Class PseudoColor Depth 8 Layer Overlay Transparent – supports DBE [...]

  • Page 70

    Supported Screen Options The following Screen Options are supported: • CountTransparentInOverlayVisual • ImageTextViaBitMap • EnableIncludeInferiorsFix • Enable12BitPseudoColorVisual • DisableGlxVisuals The following additional screen options are supp orted on the HP VISUALIZE-FX2, HP VISUALIZE- FX4 (stereo mode) and HP VISUALIZE-FX6 (ste[...]

  • Page 71

    } OverlayVisualPropertyRec; OverlayVisualPropertyRec *pOverlayVisuals, *pOVis; XVisualInfo getVis; XVisualInfo *pVisuals; Atom overlayVisualsAtom, actualT ype; ... /* Get the visuals for this screen and allocate. */ getVis.screen = screen; pVisuals = XGetVisua lInfo(display, VisualScreenMask, &getVis, &nVisuals); pOverlayVisuals = (O verlay[...]

  • Page 72

    Disabling the GLX Visuals The HP VISUALIZE-FX2/4/6 products are the first set of HP gra phics devices that supports the OpenGL extension to X (GLX). If HP OpenGL is in stalled on an HP VISUAL IZE-FX2/4/6 system, then the GLX extension offers new entry points for obtaini ng more information about X visuals. As part of offering extended visual inform[...]

  • Page 73

    HP VISUALIZE-FXE, FX5 and FX10 Device-Dependent Information Disable 12 Bit Direct Color Visual This section includes information on the HP VI SUALIZE-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 de vices contain 2D hardw[...]

  • Page 74

    Supported Screen Options The following screen options are supported: • CountTransparentInOverlayVisual • ImageTextViaBitMap • EnableIncludeInferiorsFix • DisableGlxVisuals HP VISUALIZE-FXE/5/10 Conf igurati on Hints Overlay Visuals and Overlay Transparency HP VISUALIZE-FXE/5/10 devices have two visuals in the overlay planes, bot h depth-8 P[...]

  • Page 75

    HP VISUALIZE-FXE/5/10 Colormaps HP VISUALIZE-FXE/5/10 devices ha ve a total of 4 hardware colo rmaps. 2 of the colormaps are dedicated to the overlay planes. The remaining 2 colormaps are dedicated to the image planes. Of the 2 overlay colormaps, one is permanently re served for the default co lormap. The other overlay colormap is available to appl[...]

  • Page 76

    Supported Screen Options The following Screen Options are supported: • FreedomVideoFormat Freedom Video Formats Freedom Series graphics devices ha ve the ability to support several di fferent video formats. The default format is 1280X1024 @ 75 Hz VESA timing. Other supported video formats m ay be selected by using the FreedomVideoFormat screen op[...]

  • Page 77

    VRX Device-Dependent Information This section includes information on the Persona lVRX (PVRX) and TurboVRX (TVRX) graphics devices. ____________________________________________________________________________________ Note: The PersonalVRX and the TurboVRX are no longer supported as of the February, 1999 10.20 Xserver cumulative patch; the inform at[...]

  • Page 78

    In overlay mode, the X server runs only in the overlay planes. Since onl y 3 or 4 planes are available in the overlay planes on VRX devices, the number of colo rs is very lim ited. To operate in overlay mode, the overlay device file should be specified as the primary screen device. For exam ple: /dev/ocrt # Overlay mode using 3 overlay planes or /d[...]

  • Page 79

    Chapter 4: X Windows Configuration Det ails This chapter discusses several details concerning th e configuration of X hosts, colormaps, mouse, and keyboard. Making an X*.hosts File The /etc/X0.hosts file is an ASCII te xt file containing th e hostnam es of each remote host perm itted to access your local server. • If you are running as a stand-al[...]

  • Page 80

    ____________________________________________________________________________________ Note: The number in an Xnscreens file does not nece ssarily refer to a physi cal screen num ber; any meaning implied by the number is for the user to define. There are no semantics applied to the num ber except that the Xnscreens files are used when X is started on[...]

  • Page 81

    hp-HIL input devices can plug into other hp-HIL devices, with up to seven input devices connected together. If there are no DIN input devices connected, and there are multile hp-HIL in put devices, the following algorithm is used to choose an X keyboard and pointer device. 1. If no explicit specification is made through the X*devices file, the last[...]

  • Page 82

    Explicitly Specifying Input Device Use The X server can be explicitly configured to use a sp ecific input device as the X poin ter or X key board, or merge the data from an input device with that fr om the X pointer or keyboar d. This configuration is done by adding information to the X*devices file. Ther e is one syntax to use for hp-HIL devices, [...]

  • Page 83

    The following example specifies a Spatial System Sp aceball® connected to the serial port associated with device file /dev/tty0p0 as the X pointer: Begin_Device_Description Name spaceball.1 Path /dev/tty0p0 Use pointer End_Device_Description More examples of input device specificati ons for RS-232 input devices are in the /usr/newconfig/etc/X11/X0[...]

  • Page 84

    This syntax should not be used if more than one X server will be run on the same computer, or if non-X programs will be directly accessing input devices. Th e X serve r 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*d[...]

  • Page 85

    If you had a more complicated configuration, such as two graphics tablets, two keyboards, and a barcode reader, your X*devices file could look like this: • first tablet pointer The p ointer • second tablet other Merged with the pointer • first keyboard other Merged with the keyboard • second keyboard keyboard The keyboard • first barcode [...]

  • Page 86

    Redefining the hp-H IL 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/hi l. The device files are nam ed by appending the numbers "1" throug h "7" to the path. The path is redefined by adding an entry to the X*devices file with the following form[...]

  • Page 87

    Initializing the Colormap with xinitcolormap The xinitcolormap client initializes the X colormap. Specific X colormap entries (pixel value s) are made to correspond to specifie d colors. An initialized co lorm ap is required by applications that assume a predefined colormap (for example, many a pplications that use Starbase graphics). xinitcolormap[...]

  • Page 88

    Customizing the Mouse and Keyboard This section describes the fo llowing custom izations: • Changing mouse button actions. • The xmodmap client. • Going mouseless. • Customizing keyboard input. Changing Mouse Button Actions Normally, the mouse pointer buttons are mapped as follows: Default Mouse Button Mapping Button Number Button on a 2-bu[...]

  • Page 89

    The xmodmap utility can be used to change m o use button mappings. The syntax for changing m ouse button mappings with xmodmap is: xmodmap {-e "pointer = {default | number [number...] }" | -pp} -e Specifies a remapping expression. Valid expres sions are covered in "Custom izing Keyboard Input". default Set mouse keys back to def[...]

  • Page 90

    The X*pointerkeys file lets you specify: • The keys that move the pointer. • The keys that act as pointer buttons. • The increments for movement of the pointer. • The key sequence that resets X11. • The pixel threshold that must be exceeded before the server switches screens. • That button chording is enabled or disabled. • That butto[...]

  • Page 91

    Creating a Custom X*pointerkeys File You need to modify the existing X0pointerkeys file only if one or more of the following statem ents are true: • You want to use the keyboard for a pointer. • You want to change the pointer keys from their default configuration. • You use the X0screens file to configure your display. You need to create a cu[...]

  • Page 92

    ointer Movement Functions Movement Option Function Default Key Move the pointer to the le ft. pointer_left_key keypad_1 Move the pointer to the right. pointer_right_key keypad_3 Move the pointer up. pointer_up_key keypad_5 Move the pointer down. pointer_down_key keypad_2 Add a modifier key to the pointer direction keys. pointer_key_mod1 (no default[...]

  • Page 93

    Button Operation Functions Button Operation Function Default Key Perform button 1 operations pointer_button1_key keypad_* Perform button 2 operations pointer_button2_key keypad_/ Perform button 3 operations pointer_button3_key keypad_+ Perform button 4 operations pointer_button4_key keypad_- Perform button 5 operations pointer_button5_key keypad_7 [...]

  • Page 94

    Button Chording Option Function Default Action Turn button chording off or on button_chord ing On for devices with two buttons, off for devices with more than two buttons Button chording refers to the gene ration of a button-press by pressi ng two other buttons . If you have a two-button mouse, you can generate Button 3 by pre ssing both buttons to[...]

  • Page 95

    You can also use the X*pointerkeys file to co ntrol screen switching behavior in multi-screen configurations. See the example X*pointerkeys file in /usr/lib/X11 for an exam ple of this functionality. ____________________________________________________________________________________ Note: The sample X*pointerkeys file is pla ced in /usr/lib/X11 at[...]

  • Page 96

    However, suppose you wanted to move only one pixe l to the left. Although the default value of pointer_mod2_amt is one pixel, no key is assigned to th e modifier for that amount. Thus, you would need to edit the X0pointerkeys file (or create an X*pointerkeys ) to in clude a line a ssigning one of the modifier keys to pointer_amt_mod2 . The followin[...]

  • Page 97

    The easiest way to solve this dilemma is to call in another m odifier. The following lines illustrate this. Compare them to the previous exam ple. ###pointer function key pointer_key_mod1 left_shift pointer_key_mod2 left_extend pointer_left_key cursor_left pointer_right_key cursor_right pointer_up_key cursor_up pointer_down_key cursor_down In this [...]

  • Page 98

    -quiet Turns off verbose logging. This is the default. -n Lists changes to key mappings withou t actually making those changes. -e <expression> Specifies a remapping expre ssion to be executed. -pm, -p Prints the current modifier map to the st andard output. This is the default. -pk Prints the current keymap tabl e to the standard output. -pp[...]

  • Page 99

    For example, on a PC-style keyboard, you can press to print a lower case "d", to print a capital "D", to pr int something else, and to print still something els e. The xmodmap client gives you the power to change the mean ing of any key at any tim e or to install a whole new key map for your keyboard. Examples Suppose you freque[...]

  • Page 100

    Printing a Key Map The -pk option prints a list of the key mappings for the current keyboard. xmodmap –pk The list contains the keycode and up to four 2-part columns. The firs t column contains unm odified key values, the second column contai ns shifted key values, the th ird column contains meta ( ) key values, and the fourth column contains shi[...]

  • Page 101

    Default Keyboard Ma ppi ng The default keyboard mapping supplied with the X Window environment maps the C1429 keyboard to the same key symbols that are used for the 46021 ke yboard. T his allows existing X client programs that expect to receive input from a 46021 ke yboard to be used with either keyboard. However, the result is that some keys on th[...]

  • Page 102

    may have to be restarted in order to recognize th e new mapping. For m ore information about using the xmodmap client, see the xmodmap man page. C1429 Keyboard Execute the following command to change the ma pping of the keys shown above to m atch the engravings on the C1429 keycaps. /usr/bin/X11/xmodmap /usr/lib/X11/XPCmodmap 46021 Keyboard Execute[...]

  • Page 103

    Chapter 5 PowerShade: Enhanced 3D Rendering in Software PowerShade is software that a llows lighting, shading, and hidden-surface removal. It offers the capability for both surface rende ring and volumetric renderin g. (Volumetric renderin g is ava ilable on supported devices only.) PowerShade is not supported on the GRX or on a ny grayscale versio[...]

  • Page 104

    Re-Installing PowerShade PowerShade comes bundled with the hp-UX operating system, but in case you ever need to re-install it, do the following: 1. Follow the instructions in the hp-UX manual Managing hp-UX Software with SD-UX to install software (us ing the /usr/sbin/swinstall process). 2. Select the PowerShade product for installation. 3D Graphic[...]

  • Page 105

    Other features are availa ble (listed as "Factors A ffecting Perf orm ance:") but should be used with discretion as performance is sign ificantly slower if even one of these features is used. ____________________________________________________________________________________ Note: The following tables were complete and accurate as of the[...]

  • Page 106

    hp PEX Graphics Performance Optimized vs. Normal 3D Performance Rendering Conditions Performance Optimized For: Factors Affecting Performance: • Light sources: o Best: up to 8 directional light sources, plus ambient o Good: a mixture of up to 8 directional and positio nal light sources, plus ambient • Directional eyepoint (this is the default i[...]

  • Page 107

    Window Conditions Performance Optimized For: Factors Affecting Performance: • Window unobscured or obscured only by overlay windows • Window obscured by many other image plane windows • Backing store enabled (on supported devices) FillArea Primitives Performance Optimized For: Factors Affecting Performance: • Best: shared vertex prim itives[...]

  • Page 108

    Polymarker Primitives Performance Optimized For: Factors Affecting Performance: • Many markers per call: o PEXMarkers , PEXOCCMarkers , PEXhpMarkersWithData • Color per vertex ( PEXColorTypeIndexed , PEXColorTypeRGB ) • Color approximation type PEXColorRange Text Primitives Performance Optimized For: Factors Affecting Performance: • Longer [...]

  • Page 109

    hp-PHIGS Graphics Performance Optimized vs. Normal 3D Performanc e Performance Optimized For: Factors Affecting Performance: Rendering Conditions • Light Sources: o Best: up to 8 directional light sources, plus ambient o Good: a mixture of up to 8 directional and positio nal light sources, plus ambient • Directional eyepoint, set via: o pescape[...]

  • Page 110

    Window Conditions Performance Optimized For: Factors Affecting Performance: • Window unobscured or obscured only by overlay windows • Window obscured by other image plane windows • Backing store enabled (on supported devices) Fill Area Set Primitives Performance Optimized For: Factors Affecting Performance: • Best: shared vertex prim itives[...]

  • Page 111

    Polymarker Primitives Performance Optimized For: Factors Affecting Performance: • Many markers per call: o ppolymarker3 (C), ppm3 (FORTRAN) o ppolymarker (C), ppm (FORTRAN) • These vertex data: o Indirect colour o RGB colour • Pseudo colour mapping method Text Primitives Performance Optimized For: Factors Affecting Performance: • Longer str[...]

  • Page 112

    Starbase Graphics Performance Optimized vs. Normal 3D Performance Performance Optimized For: Factors Affecting Performance: Rendering Conditions • Best: up to 8 directional light sources, plus ambient • Good: a mixture of up to 8 directional and positional light sources, plus ambient • Directional eyepoint set with view_point • Back face cu[...]

  • Page 113

    Window Conditions Performance Optimized For: Factors Affecting Performance: • Window unobscured or obscured only by overlay windows • Window obscured by many other image plane windows • Backing store enabled (on supported devices) Polygon Primitives Performance Optimized For: Factors Affecting Performance: • Best: shared vertex prim itives [...]

  • Page 114

    Polymarker Primitives Performance Optimized For: Factors Affecting Performance: • Many markers per polymarker3d or polymarker_with_data3d • These vertex formats: o RGB/vertex o Indirect color o Intensity • shade_mode set to CMAP_MONOTONIC Text Primitives Performance Optimized For: Factors Affecting Performance: • Longer strings • Polygona[...]

  • Page 115

    Chapter 6: Miscellaneous Topics 3D Thread-Safing General Information For hp-UX release 10.30 and later, Hewlett-Pack ard's 3D graphics APIs are supported in m ulti-threaded applications (using POSIX threads). However, these li braries are thread-restricted and can be accessed only from a single dedic ated thread of a m ulti-threaded program . [...]

  • Page 116

    Other Threads-Related Information 1. All of the 3D graphics func tions are cancellation points. 2. None of the 3D graphics func tions are async-cancel safe. 3. None of the 3D graphics func tions are async-signal safe. 4. None of the 3D graphics functions are fork-saf e, i.e., they cannot be called by a child process after a fork(2) , but before an [...]

  • Page 117

    SIGCHLD and the GRM Daemon The Graphics Resource Manager Daemon ( grmd ) is started when the X11 Se rver is started. In normal operation, a Starbase, hp PEX, or hp-PHIGS applicat ion will not start the da emon, and so will no t be affected by the SIGCHLD manipulation th at occurs as part of that startup (see below). However, if the grmd dies for so[...]

  • Page 118

    SIGCHLD and the Star base Input Daemon The Starbase input daemon is star ted whenever tracking or event m onitoring is enabled. W hen tracking and event monitoring are turned off or when the out put device is closed, St arbase term inates the daemon, using this process: 1. Set the SIGCHLD action to SIG_DFL , saving the old action. 2. Send a message[...]

  • Page 119

    Why Is Gamma Co rrection N eeded? The intensity of light generated by a conventional monitor is non-linear with respect to the signal applied. The intensity output is approximately equal to the applied voltag e rais ed to a power. This power is referred to as the gamma of the monitor. State d mathematically, intensity = voltage gamma For example, t[...]

  • Page 120

    Monitor Brightness and Cont rast Often, the brightness control on a mo nitor is boosted to compensate fo r im ages that look dim due to a lack of gamma correction. Before applying gamm a corr ection, the monitor brightness should be adjusted so a blank screen looks black in t ypical viewing conditions. Next, display a picture that is predominantly [...]

  • Page 121

    Use the following steps to fill in the "Create Action" form . 1. Enter Gamma in the "Action Name" window. 2. Enter /opt/graphics/common/ bin/gamma in the "Command When Action is Opened" window. 3. Click "Find Set..." and double click on the .dt/icons director y under your home directory. 4. Select the "G[...]

  • Page 122

    Once you have filled in the "Create Actions" form, se lect "Save" from the File m enu and follow these steps: 1. Click the Home Folder Icon on the CDE Front Panel, and click the up-arrow above the "Home Folder Icon" to display the sub-menu. Figure 15: Home folder icon 1. Home Folder Icon 2. Arrow for displaying the “[...]

  • Page 123

    Using the Gamma Correction Tool Figure 18: Gamma Correction Tool Gamma Value Slider The gamma value represents a power, so a value of 1.0 is the sam e as no gamma correction. Although the actual measured gamma value of most m onitors is over 2.0, a gamm a value of 1.7 is recommended since most applications have hist orically compensated for a lack [...]

  • Page 124

    If the colormap used by the sel ected window is also used by othe r windows, their appearance will change along with the actual window you selected. If the only colormap used by the selected window is the default co lormap, then you will need to check the "Modify Default Colormap" box as well. Modifyi ng the default colorm ap will change [...]

  • Page 125

    You can prevent this problem by changing with Shared Mem ory size through hp-UX's SAM (System Administration Manager) program. Reference Documentation You may find the following documentation he lpful when using hp graphics products: • For Starbase programming • Starbase Reference • Starbase Graphics Techniques • hp-UX Starbase Device [...]

  • Page 126

    Appendix A: X Reference Page Synopsis The X Window System is a network-transparent window system developed at MIT which runs on a wide range of computing and graphics machines. It should be relatively straight forward to build the MIT software distribution on most ANSI C-compliant and POSIX-co mpliant s ystems. Commercial implementations are also a[...]

  • Page 127

    and xprop ), a diagnostic for seeing what ev ents are generated and when ( xev ), screen image manipulation utilities ( xwd, xwud, xpr , and xmag ), and various demos ( xeyes, ico, xgc, x11perf, etc.). Hewlett-Packard provides a graphical user envi ronment called The Common Desktop Environment (CDE). hp CDE is the user interface, enabling the user [...]

  • Page 128

    Display Names From the user's perspective, every X server has a display name of the form: hostname:displaynumber.screennumber This information is used by the application to dete rmine how it should connect to the server and which screen it should use by default (on d i splays with multiple monitors ): hostname The hostname specifies the name o[...]

  • Page 129

    hostname part of the display name is used to determ in e the type of channel (als o called a transport layer) to be used. X servers generally suppor t the following types of connections: local The hostname part of the display name should be the em pty string. For example: ":0", ":1", or ":0.1" . The most efficient loca[...]

  • Page 130

    Geometry Specifications One of the advantages of using window systems instea d of hardwired term inals is that applications don't have to be restricted to a particular size or lo cation on the screen. Althoug h the layout of windows on a display is controlled by the window manager that the user is running (des cribed below), most X programs ac[...]

  • Page 131

    Offsets must be given as pairs; in other words, in order to specify either xoff or yoff both m ust be present. Windows can be placed in the four corners of the screen using th e following specifications: • +0+0 (the upper left-hand corner) • -0+0 (the upper right-hand corner) • -0-0 (the lower right-hand corner) • +0-0 (the lower left-hand [...]

  • Page 132

    the server start up with all of the commonly used font directories in th e font path, the font path can be changed at any time with the xset program. However, it is importan t to remember that the director y names are on the server's m achine, not on the applic ation's. Usually, fonts used by X servers and font servers can be found in sub[...]

  • Page 133

    To convert one of the resulting nam es into a font at a specific size, replace one of the first two zeros with a nonzero value. The field containing the first zero is for the p ixel size; replace it with a specific he ight in pixels to name a font at that size. Alternatively, the field containing the second zero is for the point size; replace it wi[...]

  • Page 134

    An RGB Device specification is identif ied by the prefix "rgb:" and has the following syntax: rgb:red/green/blue where red, green, and blue are encoded as h, hh, hhh, or hhhh, and h represents a single hexadecimal digit. ___________________________________________________________________________ Note : “h” indicates the value scaled i[...]

  • Page 135

    The standard device-independent string specifications hav e the following syntax: CIE XYZ:X/Y/Z (none, 1, none) CIEuvY:u/v/Y ( .6, .6, 1) CIExyY:x/y/Y ( .75, .85, 1) CIELab:L/a/b (100, none, none) CIELuv:L/u/v (100, none, none) TekHVC:H/V/C (360, 100, 100) All of the values (C, H, V, X, Y, Z, a, b, u, v, y, x) are floating-point values. Some of the[...]

  • Page 136

    Switching between groups is controlled by the keys ym named "Mode Switch", by attaching that keysym to some key and attaching that key to any one of the m odifiers Mod1 through Mod5. This modifier is called the group modifier . Group 1 is used when the group modifier is off, and Group 2 is used when the group modifier is on. Within a grou[...]

  • Page 137

    -selectionTimeout This option specifies the timeout in milliseconds within which two communicating ap plications must respond to one another for a selection request. -synchronous This option indicates that requests to the X se rver should be sent s ynchronously, instead of asynchronously. Since Xlib norm ally buffers requests to the server, errors [...]

  • Page 138

    IncludeFile lines are interpreted by replacing the line with the contents of the specified file. The word "include" must be in lo wercase. The filename is inte rpreted relative to the dire ctory of the file in which the line occurs (for example, if the filename contains no directory or contai ns a relative directory specification). If a R[...]

  • Page 139

    Programs based on the X Tookit Intrinsics obtain res ources from the following sources (other programs usually support some subset of these sources): RESOURCE_MANAGER root window property Any global resources that should be available to clients on all mach ines should be stored in the RESOURCE_MANAGER property on the root window of the first screen[...]

  • Page 140

    By combining class and instance specifications, app lication preferences can be set quickly and easily. Users of color displays will frequently want to set Background and Foreground clas ses to particular defaults. Specific color instances such as text cursor s can then be overridden w ithout having to define all of the related resources. For examp[...]

  • Page 141

    Examples The following is a collection of sample comm and lines for some of the more frequently used commands. For more information on a particular command, please refer to that command' s manual page. $ xrdb $HOME/.Xdefaults $ xmodmap -e "keysym BackSpace = Delete" $ mkfontdir /usr/local/lib/X11/otherfonts $ xset fp+ /usr/local/lib/[...]

  • Page 142

    See Also bdftopcf(1), bitmap(1), fs(1) , hpterm(1) mkfontdir( 1), mwm(1), xauth(1) , xcloc k(1), xcmsdb(1), xfd(1) , xhost(1), xinitcolor(1), xload(1), xlsfonts(1) , xmodmap( 1), xpr(1) , xprop(1), xrdb(1) , xrefresh(1), xset(1), xsetroot(1), xterm(1) , xwd(1), xwin info(1), xwud(1 ), Xserver(1), Xlib - C Language X Interface, and X Toolkit Intrins[...]

  • Page 143

    Appendix B: X Server Reference Page Name X: X Window System server Synopsis :displaynumber [-option] <ttyname> Description "X" is the generic name for the window system server. It is started by the dtlogin program which is typically run by init(1M) . Alternatively, it may be started from the xinit(1) program, which is called by x11s[...]

  • Page 144

    Options The following options can be given on the command line to the X server. -a <number> Sets pointer acceleration (i.e., the ratio of how much is reported to how much the user actually moved the pointer). -audit <level> Sets the audit trail level. The default level is 1, m eaning only connection rejections are reported. Level 2 addi[...]

  • Page 145

    -logo Turns on the X Window System logo display in the screen-saver. There is currently no way to change this from a client. You also need to specify -v to enable the logo to appear. nologo Turns off the X Window System logo display in th e screen-saver. There is currently no way to change this from a client. -p <minutes> Sets screen-saver pa[...]

  • Page 146

    You can also have the X server connect to xdm(1) or dtlogin(1X) using XDMCP . Although this is not typically useful as it doesn't a llow xdm to manage the server process, it can be used to debug XDMCP implementations, and serves as a sample im plementation of the server side of XDMCP . The following options control the behavior of XDMCP . -que[...]

  • Page 147

    Security File Format The syntax of the security policy file is as follows . Notation: "*" means zero or m ore occurrences of the preceding element, and "+" m eans one or more occurre nces. T o interpret xxx/yyy, ignore the text after the /; it is used to distin guish between instances of xxx in the next section. <policy file&[...]

  • Page 148

    <sitepolicy> lines are currently igno red. They are intended to specif y the site policies u sed by the XC- QUERY-SECURITY-1 authorization method. <access rule> lines specify how the server should react to untrusted client request s that affect the X Window property named <property/ar> . The rest of this section descri bes the int[...]

  • Page 149

    An <action> applies to all <operations> that fo llow it, until the next <action> is encountered. Thus, " irwad " means "ignore read and write, allow delete." GetProperty and RotateProperties may do multiple ope rations (r and d, or r and w). If different a ctions apply to the operations, the most seve re action[...]

  • Page 150

    # say "top level windows only." property WM_CLASS WM_NAME ar # These next three let xlsclients work untrusted. Think carefully # before including these; giving away the client machine name and command # may be exposing too much. property WM_STATE WM_NAME ar property WM_CLIENT_MACHINE WM_NAME ar property WM_COMMAND WM_NAME ar # To let untr[...]

  • Page 151

    Running From INIT Though X will usually be run by dtlogin from init, it is possible to run X directly from init. For information about running X from dtlogin , see the dtlogin man page. To run X directly from init , it is necessary to modify /etc /inittab and /etc/gettydefs . Detailed inf ormation on these files may be obtained from the inittab(4) [...]

  • Page 152

    page for a description of the binary format of this file. Maintenance of this f ile, and distribution of its contents to remote sites for use the re is left as an exercise for the reader. The sample server also uses a host-based access c ontrol list for decid ing whether or not to accept connections from clients on a particular machine. Th is lis t[...]

  • Page 153

    Fonts Fonts are usually stored as individual files in directories. Th e list of directories in which the server looks when trying to open a font is cont rolled by the font pat h. Although most sites will choose to have the server start up with the appr opriate font path (using the -fp option mentioned above), it can be overridden using the xset pro[...]

  • Page 154

    Files /etc/inittab Script for the init process /etc/gettydefs Speed and terminal settings used by getty /etc/X*.hosts Initial access control list /usr/lib/X11/fonts Top level font directory /usr/lib/X11/rgb.txt Color datab ase /usr/lib/X11/rgb.pag Color database /usr/lib/X11/rgb.dir Color database /usr/spool/sockets/X11/* IPC mechanism socket /var/[...]

  • Page 155

    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[...]

  • Page 156

    Appendix C: Low BandWid th X Proxy Name lbxproxy: Low BandWidth X proxy Synopsis lbxproxy [:<display>] [<option>] Description Applications that would like to take advantage of the Low Bandwidth extension to X (LBX) must make their connections to an lbxproxy . These applications don't need to know anything about LBX, they simply con[...]

  • Page 157

    The lbxproxy program has various options, all of which are optional. If :<display> is specified, the proxy will use the given display port when listening for connections. The display port is an offset from port 6000, identical to the way in which regular X display connections are specified. If no port is specifi ed on the command line option,[...]

  • Page 158

    -nogfx Disables reencoding of graphi cs requests (not including image-related requests). -noimage Disables image compression. -nosquish Disables squishing of X events. - nointernsc Disables short circuiting of InternAtom requests. -noatomsfile Disables reading of the atoms control file. See th e section on "Atom Control" for m ore details[...]

  • Page 159

    Atom Control At startup, lbxproxy "pre-interns" a configurable list of atoms. This allows lbxproxy to intern a group of atoms in a single round trip and immediat ely store the results in its cache. While running, lbxproxy uses heuristics to decide when to delay sending window property data to the server. The heuristics depend on the size [...]

  • Page 160

    Appendix D: RX Net scape Navigator Plug-in Name libxrx : RX Netscape Navigator Plugin Description The RX Plugin may be used with Netscape Navigator (3.0 or later) to interpret docum ents in the RX MIME type format and start remote applications. The RX Plugin reads an RX document, from which it gets th e list of services the application wan ts to us[...]

  • Page 161

    If you are already running Netscape Navigator, you need to exit and restart it after copying the plugin library so the new plugin will be found. Once this is done you can check that Navig ator has successfully loaded the plugin by checking the About Plugins page from the Help menu. This should show something like: RX Plugin File name: /usr/local /l[...]

  • Page 162

    Environment If the RX document requests X-UI-LBX service and the default X serv er does not advertise the LBX extension, the RX Plugin will look for the env ironment variable XREALDISPLAY to get a second address for your X server and look for the LBX ex tension there. When r unning your browser through lbxproxy you will need to set XREALDISPLAY to [...]

  • Page 163

    Appendix E: Proxy Manager Service Name proxymngr : Proxy Manager Service Synopsis proxymngr [-config <filename>] [-timeout <seconds>] [-retries <#>-verbose] Description The proxy manager ( proxymngr ) is responsible for re solving requests from xfindproxy (and other sim ilar clients), starting new proxies when appropriate, and kee[...]

  • Page 164

    Proxy Manager Config File The proxy manager maintains a local configuration file describing the proxy services available. T his configuration file is installed in /etc/X11/proxymngr/pmconfig during the in stallation of proxymngr . The location of the configuration f ile can be overwritten using th e -config command line option. Aside from lines sta[...]

  • Page 165

    Example Here is a sample configuration file: ! proxy manager config file ! ! Each line has the format: ! managed ! or ! unmanaged ! lbx managed /usr/bin/X11/lbxproxy -display dispName:0.0 :1 ! Proxy Manager Details When the proxy manager gets a request from xfindproxy (or another similar client ), its course of action will depend on the <service[...]

  • Page 166

    Origin The Open Group See Also xfindproxy(1), lbxproxy(1) Graphics Administrati on Guide for HP-UX 10.20 Page 166[...]

  • Page 167

    Appendix F: Locate Proxy Services Name xfindproxy : Locate Proxy Services Synopsis xfindproxy -manager <managerAddr > -name <serviceN ame> -server <serverAddr> [-auth] [-host <hostAddr>] [-options <opts>] Description xfindproxy is a program used to locate available proxy services. It utilizes the Proxy Management Proto[...]

  • Page 168

    If xfindproxy is successful in obtaining a proxy address, it will print it to stdout. The format of the proxy address is specific to the proxy serv ice being used. For example, for a proxy service of "LBX", the proxy address would be the X display addr ess of the proxy (e.g, "info.x.org:63"). If xfindproxy is unsuccessful in obt[...]

  • Page 169

    Appendix G: RX Helper Program Name xrx : RX Helper Program Synopsis xrx [-<toolkitoption> . . .]<filename> Description The helper program may be used with any W eb brow ser to interpret docu ments in the RX MIME type format and start remote applications. xrx reads in the RX document specified by its <filename> , from which it gets[...]

  • Page 170

    Options The xrx helper program accepts all of the standa rd X Toolkit co mmand line options such as: -xrm <resourcestring> This option specifies a resource stri ng to be used. There may be seve ral instances of this option on the command line. Resources The application class name of the < xrx> program is Xrx and it understands the follo[...]

  • Page 171

    then tries to use the video server as the print server. If the p rinter na me is not specified via XPRINTER , < xrx> looks for it in the variab les PDPRINTER , then LPDEST , and finally PRINTER , Notes When an authorization key is created for a remote application to use the X Print service, the he lper program has to create the key with an in[...]