ECO NUMBER: VMS721_CPU2208-V0200 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 COVER LETTER 1 KIT NAME: VMS721_CPU2208-V0200 2 KITS SUPERSEDED BY THIS KIT: o VMS721_CPU2208-V0100 o VMS721_DS20E_ES40-V0100 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: o VMS721_UPDATE-V0100 o VMS721_PCSI-V0100 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-1. 4.2 Files patched or replaced: o [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE (new image) o [SYS$LDR]SYS$CPU_ROUTINES_2508.EXE (new image) o [SYSLIB]DECW$SERVER_DDX_GZ.EXE (new image) o [SYS$LDR]EXEC_INIT.EXE (new image) o [SYSEXE]GCU.EXE (new image) -- COVER LETTER -- Page 2 18 January 2001 o [SYS$LDR]SYS$EIDRIVER.EXE (new image) o [SYS$LDR]SYS$GZDRIVER.EXE (new image) o [SYS$LDR]SYS$GZVDRIVER.EXE (new image) o [SYS$LDR]SYS$IIDRIVER.EXE (new image) o [SYSEXE]SYS$SMHANDLER.EXE (new image) o [SYSMGR]DECW$DEVICE_CONFIG_GZ.COM (new file) o [SYSEXE]SYS$CONFIG.DAT (new file) o [SYSMGR]GALAXY.GCR (new file) 5 PROBLEMS ADDRESSED IN VMS721_CPU2208-V0200 KIT o The VMS721_DS20E-V0100 and VMS721_CPU2208-V0100 remedial kits contained common images. The VMS721_CPU2208-V0200 kit simply combines these two kits. If you have already installed the VMS721_DS20E-V0100 and VMS721_CPU2208-V0100 remedial kits there is no need to install this VMS712_CPU2208-V0200 kit. 6 PROBLEMS ADDRESSED IN VMS721_CPU2208-V0100 KIT o The VMS Correctable Error Throttling Notification (CETN) does not subscribe to the Regatta PFMS 3.1 specifications as follows: I. Throttling on to throttling-off cycling does not operate with automatic 5 minute intervals. II. Throttling-on threshold is not set at 4 correctable events within a 2 second timing window III. Reboot initialization CETN event status is not provided IV. CETN event throttle-on (Set) and throttle-off (Clear) bits are not set to their correct states Images Affected: - [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE - [SYS$LDR]SYS$CPU_ROUTINES_2508.EXE o Allow mixed CPU operation in support of field replacements. This allows field replacement of CPUs without having to replace all the CPUs in the system. Images Affected: -- COVER LETTER -- Page 3 18 January 2001 - [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE o A potential data inconsistency has been identified on some systems (referenced below) during qualification testing of an unreleased graphics software kit. This error has only occurred in a highly stressful technical validation environment. Compaq does not expect customers to experience this problem, but in an effort to provide the highest level of customer service, we recommend that users with the following systems install the DEC-AXPVMS-VMS721_CPU2208-V0100-4.PCSI (or later) or DEC-AXPVMS-VMS712_CPU2208-V0100-4.PCSI (or later) remedial kits: AlphaServers AlphaStations ------------------- -------------------------------------- Compaq AlphaServer Compaq AlphaStation ES40 ES40 Compaq AlphaServer Compaq AlphaStation XP900 DS10 Compaq AlphaServer Compaq AlphaStation XP1000 DS10L Compaq AlphaServer Compaq AlphaStation 21264 PCI/ISA SBC DS20 Compaq AlphaServer Compaq AlphaStation DS20E DS20E ---------------------------------------------------------------- For OpenVMS Version 7.2-1H1, this fix is also included in the DEC-AXPVMS-VMS721H1_UPDATE-V0300 (or later) remedial kit. Images Affected: - [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE - [SYS$LDR]SYS$CPU_ROUTINES_2508.EXE 7 NEW FUNCTIONALITY ADDRESSED IN VMS721_DS20E_ES40-V0100 KIT -- COVER LETTER -- Page 4 18 January 2001 7.1 Compaq AlphaServer DS20E Support This kit provides OpenVMS Version 7.2-1 support for the Compaq AlphaServer DS20E. The DS20E is a follow-on to the Compaq AlphaServer DS20. This kit includes the following OpenVMS support on the DS20E: o Server management o 3X-DEPVD-AA PCI adapter o IDE CD-ROM and boot and runtime Image(s) Affected: - [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE - [SYS$LDR]SYS$IIDRIVER.EXE - [SYSEXE]SYS$SMHANDLER.EXE 7.2 DS20E Restrictions 7.2.1 I/O to Tribytes in PCI Space Unsupported On Compaq AlphaServer DS20E systems, you cannot use the following system routines to perform I/O tribyte reads and writes: o IOC$READ_PCI_CONFIG o IOC$WRITE_PCI_CONFIG o IOC$READ_IO o IOC$WRITE_IO If a device driver calls any of these system routines with a length of three, you must use one of the following methods instead-depending on your I/O cards characteristics: For IOC$READ_IO and IOC$READ_PCI_CONFIG: o Use a longword read, and mask out the byte. o Do a combination of word and byte reads, and append the data. For IOC$WRITE_IO and IOC$WRITE_PCI_CONFIG: o Read a longword, modify the tribyte, and rewrite the longword. -- COVER LETTER -- Page 5 18 January 2001 Note that AlphaServer 8200/8400 and GS60/140 systems with Alpha 21264 CPUs support tribyte reads and writes. 7.2.2 I/O to Unaligned Words in PCI Space is Not Allowed This note applies to Compaq AlphaServer DS20E systems. When device drivers call the IOC$CRAM_CMD, IOC$READ_IO, and IOC$WRITE_IO system routines with the IOC$K_WORD or IOC$K_WORD_LANED parameters, the I/O address must be on a natural, word-aligned boundary. (In other words, the I/O address must be an even number). If the I/O address is an odd number, these system routines return SS$_BADPARAM. Use AUTOGEN with Feedback to Resize ERLBUFFERPAGES for FRU Configuration Error Log Entry The FRU configuration tree provided by the Compaq AlphaServer DS20E console firmware is not copied to the errorlog file if the SYSGEN parameter ERLBUFFERPAGES is not large enough. Use the following command to run AUTOGEN with the FEEDBACK option to automatically calculate the correct setting of ERLBUFFERPAGES and resize the SYS$ERRORLOG.DMP file for the configuration error log entry. $ @SYS$UPDATE:AUTOGEN SAVPARAMS REBOOT FEEDBACK 7.2.3 Server Management Event Handler Driver and Process on Compaq AlphaServer DS20E OpenVMS Alpha Version 7.1-2 automatically starts the Server Management Event handler driver and process on Compaq AlphaServer DS20E systems. The SMHANDLER process spends most of the time in the hibernate state. When a Server Management Event occurs, an interrupt is delivered to the system specific handler, which parses the exception frame and notifies SMDRIVER that an event has occurred. The driver then delivers an AST to the SMHANDLER process with the event type. The SMHANDLER process reports signaled events in the process log file SYS$MANAGER:SMHANDLER.LOG and with an OPCOM message. Additional information about the event is recorded in the system error log file. The SMHANDLER process may produce one of following new system error messages: o %SMHANDLER-S-STARTUP, server management event handler startup o %SMHANDLER-W-RFF, redundant fan failure detected o %SMHANDLER-W-RPS, redundant power supply failure detected -- COVER LETTER -- Page 6 18 January 2001 o %SMHANDLER-W-TEMP, warning temperature exceeded To correct the problem, the system manager should schedule a system shutdown at a convenient time and request Compaq Field Service to replace the failing hardware component. In the meantime, the system will continue, but without the protection of the redundant hardware. 7.3 DS20E Support for the 3X-DEPVD-AA PCI Adapter and TCP/IP for OpenVMS TCP/IP for OpenVMS Version 4.2 does not support the new 3X-DEPVD-AA PCI adapter on the AlphaServer DS20E. Prior to running UCX$CONFIG procedures, use the following command to manually configure TCP/IP with the new ethernet adapter: _$ /INTERNET_INTERFACE=I /TYPE=(ETHERNET,CLUSTER) - _$ /INTERNET_INTERFACE=I /TYPE=(ETHERNET,CLUSTER) - _$ /DESCRIPTION=INTEL_ETHERNET Check with your Compaq support representative if you have further questions on TCP/IP and the 3X-DEPVD-AA PCI adapter. 7.4 P2v (JIB CARD) graphics support This change adds P2V chip support to the P2A code used on ELSA. This functionality is only used if you are using a P2V graphics adaptor Image(s) Affected: - [SYS$LDR]SYS$GZVDRIVER.EXE - [SYSEXE]SYS$CONFIG.DAT 7.5 Creating an OpenVMS Galaxy on an AlphaServer ES40 System This Section describes the requirements and procedures for creating an OpenVMS Galaxy computing environment on an AlphaServer ES40. For complete information about the Galaxy Software Architecture on OpenVMS Alpha, refer to the OpenVMS Alpha Galaxy Guide (Order number: AA-REZQB-TE). The most recent version is always available at http://www.openvms.digital.com:8000/ For complete information about AlphaServer ES40 systems, see the AlphaServer ES40 Owners Guide (Order number: EK-ES240-UG.A01). -- COVER LETTER -- Page 7 18 January 2001 Image(s) Affected: - [SYSEXE]GCU.EXE - [SYSMGR]GALAXY.GCR - [SYS$LDR]SYS$CPU_ROUTINES_2208.EXE - [SYS$LDR]SYS$CPU_ROUTINES_2508.EXE - [SYSEXE]SYS$SMHANDLER.EXE To create an OpenVMS Galaxy on an AlphaServer ES40 system: 1. Read the Release Notes chapter in the OpenVMS Alpha Galaxy Guide. 2. Read the configuration and hardware requirements in Section 5.5.1 3. Perform the steps in sections Section 5.5.2 through Section 5.5.6. 7.5.1 Before You Start In addition to the information in the Release Notes chapter in the OpenVMS Alpha Galaxy Guide, you must also be familiar with the following configuration and hardware requirements: o Two-instance maximum You can run a maximum of two instances of OpenVMS on an AlphaServer ES40. o Console firmware To create an OpenVMS Galaxy environment on AlphaServer ES40 systems, you must download the latest version of the V5.5-xx console firmware from the following location: http://ftp.digital.com/pub/Digital/Alpha/firmware/interim/ES40/ o AlphaServer ES40 clock An AlphaServer ES40 has one clock. For an OpenVMS Galaxy, this means that you cannot run the two instances at different times. Also, the SET TIME command affects both instances. Note that this may not become evident until a number of hours have passed. o Console ports COM1 (lower) is the console port for instance 0. -- COVER LETTER -- Page 8 18 January 2001 COM2 (upper) is the console port for instance 1. Unlike creating an OpenVMS Galaxy on an AlphaServer 8400, you do not need additional hardware for the second console. COM-2 is used for this purpose. o CPUs CPU0 must be the primary for instance 0. CPU1 must be the primary for instance 1. CPUs 2 and 3 are optional secondary CPUs that can be migrated. For an example of the CPU environment variable settings on an AlphaServer ES40, see Section 6.2.5 o I/O adapters PCI Hose 0 (PCI0) belongs to instance 0 (upper 4 PCI slots) PCI Hose 1 (PCI1) belongs to instance 1 (lower 6 PCI slots) Note that PCI0 contains an embedded ISA controller. To see an I/O adapter configuration example, refer to Section 6.2.2 o Storage controllers You will need one storage controller (such as a KZPSA) per instance. For each instance, this can go to a separate Storagework box or to the same box for running as a SCSI cluster. o Network cards If each instance needs network access, a network card (such as a DE500) is required for each instance. One card each goes in PCI0 and PCI1. o Memory Granularity Restrictions Private memory must start on a 64MB boundary. Shared memory must start on an 8MB boundary. All instances except the last must have a multiple of 64MB. 7.5.2 Step 1: Confirm the AlphaServer ES40 Configuration Use the SHOW CONFIG command to make sure that the AlphaServer ES40 you are using to create an OpenVMS Galaxy environment meets the requirements described in Section 6.2.1 At the console prompt, enter the following command: P00>>>show config -- COVER LETTER -- Page 9 18 January 2001 The console displays information similar to the following example: Firmware ARC Console: v5.70 PALcode: OpenVMS PALcode V1.61-2 Tru64 UNIX PALcode V1.54-2 Serial Rom: V2.2-F RMC Rom: V1.0 RMC Flash Rom: T2.0 Processors CPU 0 Alpha 21264-4 500 MHz 4MB Bcache CPU 1 Alpha 21264-4 500 MHz 4MB Bcache CPU 2 Alpha 21264-4 500 MHz 4MB Bcache CPU 3 Alpha 21264-4 500 MHz 4MB Bcache Core Logic Cchip DECchip 21272-CA Rev 9(C4) Dchip DECchip 21272-DA Rev 2 Pchip 0 DECchip 21272-EA Rev 2 Pchip 1 DECchip 21272-EA Rev 2 TIG Rev 10 Memory Array Size Base Address Intlv Mode --------- ---------- ---------------- ---------- 0 4096Mb 0000000000000000 2-Way 1 4096Mb 0000000100000000 2-Way 2 1024Mb 0000000200000000 2-Way 3 1024Mb 0000000240000000 2-Way 10240 MB of System Memory Slot Option Hose 0, Bus 0, PCI 1 DAPCA-FA ATM622 MMF 2 DECchip 21152-AA Bridge to Bus 2, PCI 3 DEC PCI FDDI fwb0.0.0.3.0 00-00-F8-BD-C6-5C 4 DEC PowerStorm 7 Acer Labs M1543C Bridge to Bus 1, ISA 15 Acer Labs M1543C IDE dqa.0.0.15.0 dqb.0.1.15.0 dqa0.0.0.15.0 TOSHIBA CD-ROM XM-6302B 19 Acer Labs M1543C USB Option Hose 0, Bus 1, ISA Floppy dva0.0.0.1000.0 Slot Option Hose 0, Bus 2, PCI 0 NCR 53C875 pkd0.7.0.2000.0 SCSI Bus ID 7 1 NCR 53C875 pke0.7.0.2001.0 SCSI Bus ID 7 dke100.1.0.2001.0 RZ1BB-CS dke200.2.0.2001.0 RZ1BB-CS dke300.3.0.2001.0 RZ1CB-CS -- COVER LETTER -- Page 10 18 January 2001 dke400.4.0.2001.0 RZ1CB-CS 2 DE500-AA Network Con ewa0.0.0.2002.0 00-06-2B-00-0A-58 Slot Option Hose 1, Bus 0, PCI 1 NCR 53C895 pka0.7.0.1.1 SCSI Bus ID 7 dka100.1.0.1.1 RZ2CA-LA dka300.3.0.1.1 RZ2CA-LA 2 Fore ATM 155/622 Ada 3 DEC PCI FDDI fwa0.0.0.3.1 00-00-F8-45-B2-CE 4 QLogic ISP10x0 pkb0.7.0.4.1 SCSI Bus ID 7 dkb100.1.0.4.1 HSZ50-AX dkb101.1.0.4.1 HSZ50-AX dkb200.2.0.4.1 HSZ50-AX dkb201.2.0.4.1 HSZ50-AX dkb202.2.0.4.1 HSZ50-AX 5 QLogic ISP10x0 pkc0.7.0.5.1 SCSI Bus ID 7 dkc100.1.0.5.1 RZ1CB-CS dkc200.2.0.5.1 RZ1CB-CS dkc300.3.0.5.1 RZ1CB-CS dkc400.4.0.5.1 RZ1CB-CS 6 DECchip 21154-AA Bridge to Bus 2, PCI Slot Option Hose 1, Bus 2, PCI 4 DE602-AA eia0.0.0.2004.1 00-08-C7-91-0A-AA 5 DE602-AA eib0.0.0.2005.1 00-08-C7-91-0A-AB 6 DE602-TA eic0.0.0.2006.1 00-08-C7-66-80-9E 7 DE602-TA eid0.0.0.2007.1 00-08-C7-66-80-5E 7.5.3 Step 2: Install OpenVMS Alpha Version 7.2-1 No special installation procedures are required to run OpenVMS Galaxy software. Galaxy functionality is included in the base operating system and can be enabled or disabled using the console command and system parameter values described later in this chapter. If your AlphaServer ES40 is not part of a SCSI cluster, you must install OpenVMS Version 7.2-1 on two system disks-one disk for each instance. If your AlphaServer ES40 is part of a SCSI cluster with a cluster-common system disk, install OpenVMS Version 7.2-1 on one system disk. For more information about installing the OpenVMS Alpha operating system, see the OpenVMS Alpha Version 7.2 Upgrade and Installation Guide. -- COVER LETTER -- Page 11 18 January 2001 7.5.4 Step 3: Upgrade the Firmware To upgrade the firmware, use one of the following procedures: Copy the firmware file to MOM$SYSTEM on a MOP-enabled server that is accessible to the AlphaServer ES40. Enter the following commands on the console: P00>>> boot -fl 0,0 ewa0 -fi {firmware filename} UPD> update srm* Or, use the following commands: P00>>> BOOT -FLAGS 0,A0 cd_device_name . . . Bootfile: {firmware filename} . . . 7.5.5 Set Environment Variables Configure the primary console for instance 0. CPU0 is the primary for instance 0. CPU1 is the primary for instance 1. For descriptions of the Galaxy environment variables and common values for them, refer to Chapter 6 in the OpenVMS Alpha Galaxy Guide. The following example is for an AlphaServer ES40 with three CPUs and 512MB of memory divided into 256MB + 192MB + 64MB. P00>>> set lp_count 2 P00>>> set lp_cpu_mask0 1 P00>>> set lp_cpu_mask1 6 P00>>> set lp_io_mask0 10 P00>>> set lp_io_mask1 20 P00>>> set lp_mem_size0 10000000 P00>>> set lp_mem_size1 c000000 P00>>> set lp_shared_mem_size 4000000 P00>>> set auto_action halt If you have four CPUs and you want to assign all secondary CPUs to instance 1, the lp_cpu_mask1 variable will be E. If you split the CPUs between both instances, CPU 0 must be the primary for instance 0, and CPU 1 must be the primary CPU for instance 1. -- COVER LETTER -- Page 12 18 January 2001 The following example shows LP_CPU_MASK values for secondary CPU assignments with primary CPUs. Assign secondary CPU 2 with primary CPU 0 and secondary CPU 3 with primary CPU 1. >>>set lp_cpu_mask0 5 >>>set lp_cpu_mask1 A CPU Selection LP_CPU_MASK 0(primary partition 0) 2^0 = 1 1(primary partition 1) 2^1 = 2 2(secondary) 2^2 = 4 3(secondary) 2^3 = 8 The mem_size variables depend on your configuration and how you want to split it up. lp_io_mask0 must be set to 1 lp_io_mask1 must be set to 2 You must set the console environment variable AUTO_ACTION to HALT. This will ensure that the system does not boot and that you will be able to enter the Galaxy command. 7.5.6 Step 5: Initialize the System and Start the Console Devices 1. Initialize the system and start the Galaxy firmware by entering the following commands: P00>>> init P00>>> lpinit ! same as galaxy command After the self-test completes, the Galaxy command will start the console on instance 1. Note that when the I/O bus is divided between the two Galaxy partitions, the port letter of a device might change. For example, a disk designated as DKC300 when the AlphaServer ES40 is a single system could become DKA300 when it is configured as partition 0 of the OpenVMS Galaxy. 2. Configure the console for instance 1. 3. Configure the system root, boot device, and other related variables. The following example settings are from an OpenVMS Engineering system. Change these variables to meet the needs of your own environment. -- COVER LETTER -- Page 13 18 January 2001 Instance 0 P00>>> set boot_osflags 12,0 P00>>> set bootdef_dev dka0 P00>>> set boot_reset off !!! must be OFF !!! P00>>> set ewa0_mode twisted Instance 1 P01>>> set boot_osflags 11,0 P01>>> set bootdef_dev dkb200 P01>>> set boot_reset off !!! must be OFF !!! P01>>> set ewa0_mode twisted 4. Boot instance 1 as follows: P01>>> boot Once instance 1 is booted, log in to the system account and edit the SYS$SYSTEM:MODPARAMS.DAT file to include the following line: GALAXY=1 Confirm that the SCSNODE and SCSSYSTEMID SYSGEN parameters are correct. Run AUTOGEN as follows to configure instance 1 as a Galaxy member, and leave the system halted: $ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL 5. Boot instance 0 as follows: P00>>> boot Once instance 0 is booted, log in to the system account and edit the SYS$SYSTEM:MODPARAMS.DAT file to include the following line: GALAXY=1 Confirm that the SCSNODE and SCSSYSTEMID SYSGEN parameters are correct. Run AUTOGEN as follows to configure instance 0 as a Galaxy member, and leave the system halted: $ @SYS$UPDATE:AUTOGEN GETDATA SHUTDOWN INITIAL 6. Prepare the Galaxy to come up automatically upon initialization or power cycle of the system. Set the AUTO_ACTION environment variable on both instances to RESTART. P00>>> set auto_action restart -- COVER LETTER -- Page 14 18 January 2001 P01>>> set auto_action restart 7. Initialize the Galaxy again by entering the following commands at the primary console: P00>>> init When the console displays the following confirmation prompt, type Y: Do you REALLY want to reset all partitions? (Y/N) Alternatively, you could power-cycle your system, and the Galaxy with both instances should bootstrap automatically. Congratulations! You have created an OpenVMS Galaxy. 8 PROBLEMS ADDRESSED IN VMS721_DS20E_ES40 KIT o The EXTENDED_ID flag in the SYS$CONFIG.DAT file is used to allow full 64-bit ID checking on PCI devices. This will be used for LAN and ATM devices to ensure that the device is a qualified device. A problem in the LOOKUP_ID code causes the ID mask to be extended to 64-bits the first time the flag is seen, and it is never reduced back to 32-bits for non-extended IDs. This causes a failure to find some disk devices at boot, and prevents booting. The user sees an error that a device on the boot command line could not be found, and the system halts. Image(s) Affected: - [SYS$LDR]EXEC_INIT.EXE o When the 680 handler issued the code 22Bh to SYS$SMHANDLER it did not display a message. Image(s) Affected: - [SYSEXE]SYS$SMHANDLER.EXE -- COVER LETTER -- Page 15 18 January 2001 9 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: 2 : Customers using the following systems should install this kit: AlphaServers AlphaStations ------------------- -------------------------------------- Compaq AlphaServer Compaq AlphaStation ES40 ES40 Compaq AlphaServer Compaq AlphaStation XP900 DS10 Compaq AlphaServer Compaq AlphaStation XP1000 DS10L Compaq AlphaServer Compaq AlphaStation 21264 PCI/ISA SBC DS20 Compaq AlphaServer Compaq AlphaStation DS20E DS20E ---------------------------------------------------------------- For OpenVMS Version 7.2-1H1, this fix is also included in the DEC-AXPVMS-VMS721H1_UPDATE-V0300 (or later) remedial kit. 10 INSTALLATION INSTRUCTIONS: Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS721_CPU2208 /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt This kit requires a system reboot. Compaq strongly recommends that a reboot is performed immediately after kit installation to avoid system instability -- COVER LETTER -- Page 16 18 January 2001 If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. Copyright (c) Compaq Computer Corporation, 2001 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL COMPAQ BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.