Patch Name: PHSS_11804 Patch Description: s700 9.X PEX 5.1/Starbase Runtime cumulative patch Creation Date: 97/07/25 Post Date: 97/07/28 Hardware Platforms - OS Releases: s700: 9.01 9.03 9.05 9.07 Products: N/A Filesets: STAR-SHLIBS SBDL-SHLIBS STAR-RUN FAFM-SHLIBS PEX5-RUN Automatic Reboot?: No Status: General Release Critical: No Path Name: /hp-ux_patches/s700/9.X/PHSS_11804 Symptoms: PHSS_11804: - Fix for GSLdt10287, SR1653219501 and SR1653219493. PHSS_9234: - Starbase daemon ignores some of the special keys such as the function keys and arrow keys. - Under HP PEX, in the case where PEXBeginRendering was called with HLHSR enabled on a window that was later resized, the software zbuffer could be managed incorrectly, resulting in various kinds of "stitching" during rendering. - Enable starbase inquire_capabilities() to return if hardware texture mapping is supported on Visualize-48. - PHIGS can dump core while rendering polyline elements, if the attribute caching traverser has been specifically disabled. - Some degenerate POLYLINE SET 3 WITH COLOUR (ppls3c, polyline_set3_colr) elements may have their non-degenerate components rendered, where the whole element should be ignored. - Some traversals of structures being edited slowed down in the previous patch. This restores the original performance. - A system hang may occur with VISUALIZE-48 devices when texture mapping using the following large-sized texture maps: 2048 x 512, 4096 x 512, 4096 x 1024, 8192 x 512, 8192 x 1024, and 16384 x 512. (This was supposed to be fixed in previous patch). - Hardware texture mapping performance on VISUALIZE-48 devices deteroriates when second file descriptor (fildes) des is closed. - PHIGS NURB surfaces may render isoparametric curves in the wrong color on VRX-family devices. PHSS_8090: - Enhancement: Device independent way to read RGB values in starbase, similar to OpenGL calls glReadPixels and glDrawPixels which allows getting RGB data easily. - Software texture mapping in highly perspective images appears blurry and distorted. - When picking polylines that contain move/draw flags bogus hits may be reported. - Texture mapping on Visualize-48 hangs system if certain large texture map sizes are used (2048x512 and 4096x1024). - Segmentation violation when inserting PHIGS ISO Fill Area primitives that are non-convex into a structure before a PHIGS Workstation is opened. - PEXOCCTriangles draws triangles with alternating geometric normals, causing incorrect display or non-display of these triangles when face distinguishing is active and interior style is hollow. - Locked structures or structures containing PEXNoop elements may dump core when traversed. - Memory corruption/core dump may occur on VISUALIZE-24 and VISUALIZE-48 using SOFAs. - PHIGS and other applications may hang on Hyper and Visualize devices for certain offscreen windows. - PHIGS Compliant backface lighting could cause core dump on VISUALIZE-24. PHSS_7488: - PEX DRAW_POINTS gescape support. PHSS_7486: - Under certain conditions, one can have bad edging on a trimmed spline. - the hpvmx driver does not always send a configure notify after a window resize. - Starbase sox11 driver does not return function key events. - PEX Nurbs has problems with trimming curves/rendering. - PEX polyline Set may skip a line. - Texture Mapping on a Visualize-48 product with a rectangular texture map will not correctly texture primitives under certain conditions. - PHIGS label performance poor. PHSS_6908: - PEX structures won't be picked if max_paths exceeded. - Missing hatching functionality on PEX API for Visualize-24 and Visualize-48 devices now enabled. PHSS_6906: - Perspective correction for view clipped textured primitives is incorrect. - Font performance is poor when using many fonts, especially across a network. - A polygon containing two or more horizontal colinear edges with opposite direction is now judged as self intersecting and decomposed into trapezoids instead of triangles. - PHIGS traversers are slower than necessary when repeatedly traversing the same structures. - Pex memory leak destroying structures with quadmesh data - Starbase texture mapping does not allow a rectangular texture map. The check for consecutive map levels in tm_load_texels fails for a rectangular texture map. Symptom of Defect? tm_load_texels returns a BAD_DIMS error for nonsquare texture maps. - Duplicate symbols "_hp_dl_link_extra_data" and "_hp_dl_unlink_extra_data" appear during archive linking. - Some PHIGS programs with recursive networks can segment fault during UPDATE WORKSTATION or REDRAW ALL STRUCTURES. Some PHIGS programs that use SET HIGHLIGHTING BETWEEN HANDLES ESCAPE (pue331, pescape_u331) will fail to update workstations properly. - DRAW_POINTS gescape, specifically the CENTER_VECTORS and CENTER_TEXT functionality was ignored on VISUALIZE-24 and VISUALIZE-48 products. This functionality is now enabled. - A variable denoting the xyz offset from the beginning of a vertex list for sofas was uninitialized. This caused some facets in sofas to be sometimes improperly culled. - Missing hatching functionality on PEX & PHIGS APIs for Visualize-24 and Visualize-48 devices. - Need control of caching traverser during heavy editing. - Texture mapping rendered by HCRX family of devices could exhibit bleed through between primitives intersecting in z and possibly result in holes and incomplete spans in the textured primitives. - Starbase texture mapping does not allow a rectangular texture map. - The starbase daemon does not recognize function keys and/or pointer keys when using Starbase through X11. PHSS_6540: - Occasional failures during the loading of an application using PEXlib, with the message that SwapCARD16 and SwapFLOAT are unresolved. - PEX indexed colors were pushed incorrectly during structure traversal and immediate mode. The popped color would be incorrect. - PEXDestroyStructures corrupted the current element location in structures referencing the destroyed structures. Subsequent structure operations based on the current element location would be performed incorrectly PHSS_6538: - Potential memory leak on VISUALIZE 48, VISUALIZE 24, HCRX 8/24 Z, CRX24Z with multiple obscuring windows. - 2-byte kanji fonts were missing in 9.07 - HCRX devices could experience deadlock when the LOCK_DEVICE gescape was used. - PHIGS text could be clipped incorrectly in non-default alignments. - European annotation text can disappear with a non-zero cull height. - When turning the interior style in PEX from texture prespecular to another style, the specular highlights are lost. - Starbase environment mapping was computed with perspective even in a parallel viewing model. hen using Starbase environment mapping and a parallel view model, the texture map would appear skewed on the surface. - On a system with a Visualize-48 card that has the optional texture map card attached, the "timd" process appears to make the average system load of an idle system be 1.0, when the actual average load of the system is idle. - VIZUALIZE-48 clears Z buffer during dbuffer_switch() even when SUPPRESS_CLEAR is specified. - Certain applications hang when opening graphics window on VISUALIZE-24 if the window is completely off screen. - Certain programs may incorrectly generate an illegal instruction and core dump using HCRX8Z or HCRX24Z graphics with archived libraries (libddhcrx.a). - PEXGetZbuffer returns incorrect value on crx48z devices. - Shared memory objects were leaked, or not destroyed correctly; also several memory leaks. - Tablet can return multiple Starbase events for a single trigger, if the cursor is moving. - Primitives can disappear if multiple application data elements are present. - Applications that use SBDL or PHIGS display lists, that link with the -Wl,-z option, and that insert attributes, can dump core (often) with a segmentation violation. - Memory leak in PEXElementSearch. - Some applications using Starbase drivers may fail at startup time with signal 11 due to having older versions of FAFM libraries. PHSS_6244: -Default PEX textures can appear on VISUALIZE-48 with Texture Mapping hardware on programs that previously rendered non default texture mapped images correctly. - Additional PEX functionality for primitives and attributes. Added are specific new functionality, including new primitives, attributes, and renderer controls. The new primitives are TriangleFan, IndexedTriangleStrip, IndexedTriangleFan, IndependentTriangles, IndexedIndependentTriangles, IndexedPolylines, and IndexedMarkers. The new attributes are, UserLineType, UserMarkerGlyph, FaceLightingMode, and HighlightColor. The new Renderer control is WideLineControl. In addition, the color vertex attribute is now supported on Markers. PHSS_6242: - Starbase applications that don't use SBDL will fail to link properly when linked bind-immediate or when linked with archive libraries. - SOFAS with edge_flags in ilist on new VISULAIZE-48 was slower than on the older product CRX48Z. - Multiple textures per primitive could result in the incorrect image being rendered. - On VISULAIZE-48 devices sometimes a quad or triangle will have less specular lighting on it than it should have. Under certain very specific conditions, a vertex that should be rather dim can end up bright white. - block_write does not work with a width of 1 on the CRX24(z). The one pixel wide block write will also write a black pixel (value 0) immediately to the left of the desired pixels. - HCRX8Z, HCRX24Z devices in certain cases may introduce floating point data corruption. Most likely visible in optimized (level +O2 and higher) applications. - An edged polygon may be drawn incorrectly on VISUALIZE- 24 and VISUALIZE-48 devices. It is drawn incorrectly due to an improper check for partial polygons. - The VMX driver can ignore user defined linetypes when rendering to remote X windows. PHSS_6128: Picking in HP APIs (including HP-PHIGS) can return incorrect paths if the source structure or segment has multiple consecutive application data elements PHSS_6020: - If an application repeatedly adds ignored elements (i.e. application data) to a segment, the traversal time for that segment goes higher and higher. This fix detects this phenomenon for some segments (particulary certain PHIGS structures) and shortens the traversal time significantly for these segments. - Several HP-supported PEX escape codes are not listed by PEXGetEnumTypeInfo for enumerated type PEXETEscape. This makes it impossible for applications to determine if the escapes are supported by this route. In particular, the Z- buffer read/write escapes added at HPPEX 5.1v3 are not listed. Also, certain CGE enumerated types such as PEXExtETOC do not list all the HP-supported values. This has been a defect since the 5.1v2 release. - Several memory leaks can be detected in the PEX API code using Purify on a very typical program. The worst leaks, of 512 and 128 bytes, occur one for every time a Renderer is bound to a window it has not been bound to before. PHSS_6018: - If an application repeatedly adds ignored elements (i.e. application data) to a segment, the traversal time for that segment goes higher and higher. This fix detects this phenomenon for some segments (particulary certain PHIGS structures) and shortens the traversal time significantly for these segments. - 1D MIPped textures via software texture mapping can draw incorrect image. Image will look "blotchy" and drastically wrong. - PEX dbe_idiom_centerline behaves incorrectly on Stinger image plns[2,2,0]. - When rendering software texture mapped images on CRX48Z that use texture alpha, pixels appear to be dropped or not rendered. - If user is: - using PEX sofa() or Starbase polyhedron() and texture mapping - and doing a transform on the texture coordinates - and doing facet normal lighting THEN the code will alter the facet normal pointer, resulting in incorrect data being used for facet normal lighting PHSS_5624: - Several prototypes for 5.2 OCC versions of PEX 5.1 attributes were incorrect in the HP-PEX 5.1v3/9.07 header files. To avoid possible future source code incompatibilities should applications attempt to call these functions with the incorrect 5.2 parameter lists, they were declared to be unsupported in the initial release. - Setting up an output command context (OCC) for strided data format, and then using the same OCC with several different PEX Renderers, results in incorrect rendering. - PEXExtSetOfFillAreaSets has lower performance in HP-PEX 5.1v3/9.07 than does either PEXSetOfFillAreaSets or PEXOCCIndexedFillAreaSets, most noticeably on some new graphics devices. - PEXOCCSetValueMask does not correctly handle the special value PEXOCCMAll5_2 in release 5.1v3/9.07 of HP-PEX. - In HP-PEX 5.1v3/9.07, most PEX 5.1 area primitives are texture mapped if the interior style is PEXExtInteriorStyleTexture when they are drawn. However, PEXFillArea is not consistently texture-mapped with the most-recently-set texturing setup - PEXExtCreateFilteredTMFromWindow does not operate correctly and may get BadMatch error. - HP-PEX 5.1v3/9.07 header files are missing function prototypes for most OCC utility functions; prototype for PEXCopyOCCValues was misnamed. - PEXPolylineSetWithData performance in Structure mode can be as much as 25% lower in HP-PEX 5.1v3/9.07 than it was in 5.1v2/9.05. Immediate mode performance is unaffected. - The prototypes for most OCC attributes and primitives were missing from PEXlib.h. PEXlib.h has been corrected. - OCC interface cannot be used when procedure PEXlib interface (enabled by defining HPPEX_PROCEDURES in the application compilation) is in use. - Setting up an output command context (OCC) for strided data format, and then using the same OCC with several different PEX Renderers, results in incorrect rendering. PHSS_5622: - Memory corruption may result if block_move is done in a window with backing store enabled and certain combinations of obscuring windows. - Core dump in _hp_acm_polyline_from_polygon with edging enabled using quad-mesh primitives. - User will see random polygon edging when screen door transparency is turn on AND move/draw flags are specified. - When a PEX texture mapping program specifies explicit texture mapping but then gives no floatlist, on VISUALIZE devices incorrect data will be picked up for the texture coords; PEX specifies the coords should default to zeroes. - If the first primitive used in a program is a DC- polygon, and nothing is done after that that retransmits clip limits, MC primitives may not get clipped correctly. They could get totally clipped away inside the shared streamline loop. Problem is that the DC-clip special tries to only revalidate part of MATRIX state. Must revalidate all of it. The fix is to change the matrix-dirt mask for dc-clip to revalidate all matrix state. - Streamlined polygons (fast path) can cause a memory leak when the polygons are concave. The leaked memory will be freed as soon as you do an operation that gets out of streamlines. Clipping polygons or vectors or doing graphical text are all ways of getting out of the streamlines. - Switching between a lot of different fonts can result is memory getting eaten up because the memory for the fonts is not freed as it should be. The fix is to free the memory properly. - When using the Starbase Texturing composition mode TM_COMPOSITE_DECAL with a texture that includes alpha values, the visualize 48 will render only a non textured image. When using the Starbase Texturing composition mode TM_COMPOSITE_DECAL with a texture that includes alpha values, the VISUALIZE-48 will render only a non-textured image. - Widelines can pass a NULL pointer to strcmp() - PHIGS applications, when linked with archive libraries, don't draw expected direct pick highlights. - Customer: Starbase application dumps core when moving window on PVRX only. - CRX24Z and CRX48Z Stinger dither a pure color, but shouldn't [5,3,0] The color scales were too small, making these devices unable to render full intensity colors. One pixel out of each 4x4 dither cell was rendered with a color component less than the maximum, making solid colors look speckled. - Using line_width(w,VDC_UNITS) with a transformation from viewing coordinates to vdc's that is anisotropic, wide lines appear distorted. Widelines were only scaled correctly along X. - While using block move with backing store on, memory corruptions may happen while the window is obscured. Defect Description: PHSS_11804: See Symptoms PHSS_9234: See Symptoms PHSS_8090: See Symptoms PHSS_7488: See Symptoms PHSS_7486: See Symptoms PHSS_6908: See Symptoms PHSS_6906: See Symptoms PHSS_6540: See Symptoms PHSS_6538: See Symptoms PHSS_6244: See Symptoms PHSS_6242: See Symptoms PHSS_6128: See Symptoms PHSS_6020: See Symptoms PHSS_6018: See Symptoms PHSS_5624: See Symptoms PHSS_5622: See Symptoms SR: 1653130724 5003131466 5003285437 1653154005 5003300145 5003290593 5003291534 1653152355 5003280743 5003300509 5003292284 1653158634 1653159764 5003295493 1653159269 1653151340 1653167205 5003304253 5003309682 1653171439 1653173104 1653183731 1653180190 1653219493 1653219501 Patch Files: /usr/lib/starbase/sb_daemon_9.0 /usr/bin/timd /usr/lib/libsb.sl /usr/lib/libsbdl.sl /usr/lib/libddhcrx.sl /usr/lib/libddhcrx48.sl /usr/lib/libtdhcrx48.sl /usr/lib/libddgcrx.sl /usr/lib/libddcrx48z.sl /usr/lib/libddvmx.sl /usr/lib/libsbload.sl /usr/lib/libdd98705.sl /usr/lib/libdd98765.sl /usr/lib/libdd98766.sl /usr/lib/libddnull.sl /usr/lib/libddhpcgm.sl /usr/lib/libsbXg.sl /usr/lib/libfa.sl /usr/lib/libfontm.sl /usr/bin/X11/pexd /usr/bin/X11/pexd_init /usr/lib/libPEX5.sl /usr/lib/PEX5/cge_utilities/libPEXUt.sl /etc/newconfig/907RelNotes/Starbase /etc/newconfig/907RelNotes/CommonGraphics /etc/newconfig/907RelNotes/PEX5 what(1) Output: /usr/lib/starbase/sb_daemon_9.0: GRAPHICS CORE R907 BRANCH 97/01/21libdd98704.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libdd98705.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libdd98735.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libdd98736.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddbyte.a $Revis ion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddcrx48z $Revis ion: 530.1.100.2 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddgcrx $Revisio n: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddhcrx48 $Revis ion: 530.1.100.21 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddhyper $Revisi on: 530.1.100.13 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddhil.a $Revisi on: 530.1.100.2 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddhpgl.a $Revis ion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddkbd.a $Revisi on: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddlkbd.a $Revis ion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddsox11.a $Revi sion: 540.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddhpterm.a $Rev ision: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddvmx $Revision : 530.1.100.2 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch $Revision: 530.1.100.2 $ Prototype VM-Xlib rasteriz ers GRAPHICS CORE R907 BRANCH 97/01/21libXwindow.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libsb1.a $Revision : 530.1.100.3 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libpi $Revision: 5 30.1.100.4 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libsga $Revision: 530.1.100.11 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libddnull $Revisio n: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libsb2.a $Revision : 530.1.100.2 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch PATCH_8.0X libdvio.a 700 66.4 91/11/05 /usr/bin/timd: GRAPHICS CORE R907 BRANCH 97/01/21timd $Revision: 53 0.1.100.13 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libsb.sl: GRAPHICS CORE R907 BRANCH 97/01/21libsb.sl $Revision : 530.1.100.3 $ PHSS_11804/11805 Starbase Runtime/Develop Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libsb2.a $Revision : 530.1.100.2 $ PHSS_11804/11805 Starbase Runtime/Develop Periodic P atch GRM Library HP-UX 8.0 A.01 Protocol PROTO_VER F ILE_VERSION GRAPHICS CORE R907 BRANCH 97/01/21libpi $Revision: 5 30.1.100.4 $ PHSS_11804/11805 Starbase Runtime/Develop Periodic P atch GRAPHICS CORE R907 BRANCH 97/01/21libsga $Revision: 530.1.100.11 $ PHSS_11804/11805 Starbase Runtime/Develop Periodic P atch /usr/lib/libsbdl.sl: GRAPHICS CORE R907 BRANCH 97/01/21libsbdl.a $Revisio n: 530.1.100.5 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libddhcrx.sl: GRAPHICS CORE R907 BRANCH 97/01/21libddhyper $Revisi on: 530.1.100.13 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libddhcrx48.sl: GRAPHICS CORE R907 BRANCH 97/01/21libddhcrx48 $Revis ion: 530.1.100.21 $ PHSS_11804/11805 Starbase Runtime/Develop Periodic P atch /usr/lib/libtdhcrx48.sl: GRAPHICS CORE R907 BRANCH 97/01/21libtdhcrx48.sl $Re vision: 530.1.100.7 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libddgcrx.sl: GRAPHICS CORE R907 BRANCH 97/01/21libddgcrx $Revisio n: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libddcrx48z.sl: GRAPHICS CORE R907 BRANCH 97/01/21libddcrx48z $Revis ion: 530.1.100.2 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libddvmx.sl: $Revision: 530.1.100.2 $ Prototype VM-Xlib rasteriz ers GRAPHICS CORE R907 BRANCH 97/01/21libddvmx $Revision : 530.1.100.2 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libsbload.sl: No what string for this file /usr/lib/libdd98705.sl: GRAPHICS CORE R907 BRANCH 97/01/21libdd98705.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libdd98765.sl: GRAPHICS CORE R907 BRANCH 97/01/21libdd98735.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libdd98766.sl: GRAPHICS CORE R907 BRANCH 97/01/21libdd98736.a $Revi sion: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libddnull.sl: GRAPHICS CORE R907 BRANCH 97/01/21libddnull $Revisio n: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libddhpcgm.sl: GRAPHICS CORE R907 BRANCH 96/10/16libddhpcgm.a $Revi sion: 530.1.100.2 $ PHSS_6904 April 96 Hardcopy 9.07 Periodic Patch /usr/lib/libsbXg.sl: GRAPHICS CORE HP-UX 9.0 930315 libsbXg /usr/lib/libfa.sl: GRAPHICS CORE R907 BRANCH 97/01/21libfa.a $Revision: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/lib/libfontm.sl: GRAPHICS CORE R907 BRANCH 97/01/21libfontm.a $Revisi on: 530.1.100.1 $ PHSS_9234/9235 Jan. 97 Starbase/CORE 9.07 Periodic P atch /usr/bin/X11/pexd: $Revision: R907 $ $Date: 97/01/21 $ pexd PEX 5.1 v2 Server Daemon PHSS_9234/9236 Jan. 97 PEX5 9.07 Periodic Patch /usr/bin/X11/pexd_init: $Revision: R907 $ $Date: 97/01/21 $ pexd PEX 5.1 v2 Server Daemon PHSS_9234/9236 Jan. 97 PEX5 9.07 Periodic Patch /usr/lib/libPEX5.sl: $Revision: R907 $ $Date: 97/01/21 $ libPEX5 PEX 5.1 v2 API Library PHSS_9234/9236 Jan. 97 PEX5 9.07 Periodic Patch /usr/lib/PEX5/cge_utilities/libPEXUt.sl: CGE Version 1.0 Utilities Library $Revision: 530.1.100.1 $ $Date: 95/03/31 19:20:40 $ /etc/newconfig/907RelNotes/Starbase: No what string for this file /etc/newconfig/907RelNotes/CommonGraphics: No what string for this file /etc/newconfig/907RelNotes/PEX5: No what string for this file sum(1) Output: 50009 6216 /usr/lib/starbase/sb_daemon_9.0 5850 80 /usr/bin/timd 18495 5328 /usr/lib/libsb.sl 45509 1168 /usr/lib/libsbdl.sl 5696 696 /usr/lib/libddhcrx.sl 9007 640 /usr/lib/libddhcrx48.sl 38143 32 /usr/lib/libtdhcrx48.sl 36953 608 /usr/lib/libddgcrx.sl 44006 392 /usr/lib/libddcrx48z.sl 4165 392 /usr/lib/libddvmx.sl 29255 56 /usr/lib/libsbload.sl 35495 776 /usr/lib/libdd98705.sl 56319 392 /usr/lib/libdd98765.sl 51337 1632 /usr/lib/libdd98766.sl 14143 40 /usr/lib/libddnull.sl 20481 296 /usr/lib/libddhpcgm.sl 31353 56 /usr/lib/libsbXg.sl 53023 120 /usr/lib/libfa.sl 48437 144 /usr/lib/libfontm.sl 23413 536 /usr/bin/X11/pexd 19111 152 /usr/bin/X11/pexd_init 60485 3656 /usr/lib/libPEX5.sl 53524 80 /usr/lib/PEX5/cge_utilities/libPEXUt.sl 22555 57 /etc/newconfig/907RelNotes/Starbase 22555 57 /etc/newconfig/907RelNotes/CommonGraphics 24632 97 /etc/newconfig/907RelNotes/PEX5 Patch Conflicts: None Patch Dependencies: s700: 9.01 9.03 9.05: PHSS_5695 and PHSS_5696 and PHSS_5914 and PHSS_5916 Hardware Dependencies: None Other Dependencies: None Supersedes: PHSS_5622 PHSS_5624 PHSS_6018 PHSS_6020 PHSS_6128 PHSS_6242 PHSS_6244 PHSS_6538 PHSS_6540 PHSS_6906 PHSS_6908 PHSS_7486 PHSS_7488 PHSS_8090 PHSS_9234 Equivalent Patches: None Patch Package Size: 11930 KBytes Installation Instructions: Please review all instructions and the Hewlett-Packard SupportLine User Guide or your Hewlett-Packard support terms and conditions for precautions, scope of license, restrictions, and, limitation of liability and warranties, before installing this patch. ------------------------------------------------------------ 1. Back up your system before installing a patch. 2. Copy the patch to your /tmp directory and unshar it: cd /tmp cp patch_source/PHSS_11804 . sh PHSS_11804 3. Become root and run update: /etc/update [-r [kernel_gen_file]] -s \ /tmp/PHSS_11804.updt PHSS_11804 Update moves the original software to /system/PHSS_11804/orig. Keep this file to recover from any potential problems. You should move the .text file to /system/PHSS_11804 for future reference. To put this patch on a magnetic tape and update from the tape drive, use dd: dd if=PHSS_11804.updt of=/dev/rmt/0m bs=2048 Special Installation Instructions: Be sure that applications using Starbase are NOT running and that the X-server is NOT running before installing this patch. Executables may appear "busy" to the file system and therefore unwritable because HP-UX uses the executable's image on disk as swap for code segments. The same is true for shared libraries because they are executable images as well.