Document revision date: 9 May 2001 | |
Previous | Contents | Index |
This section contains release notes pertaining to the DECwindows X11
display server for OpenVMS Alpha systems.
B.8.1 Graphics Boards Support
V7.3
You must install Compaq Open3D (Version 4.9A or later) for OpenVMS Alpha to support the following types of graphics boards on Version 7.3:
Alpha computers equipped with S3 Trio32 or Trio64 graphics cards
support single-screen display only. Multihead graphics are not
supported.
B.8.3 Integrated Graphics Boards Supported
V7.3
Under V7.3, support for graphics boards is fully integrated with the OpenVMS operating system. The following new boards are now supported:
This section contains release notes pertaining to DMCC.
B.9.1 Alpha 5/366 and 5/433 PICMG SBC Restriction
V7.2
The KZPDA SCSI Controller and the PBXGA Graphics Card cannot be placed
in a slot behind the bridge on the DIGITAL Modular Computing Components
(DMCC) Alpha 5/366 and 5/433 PICMG SBCs.
B.9.2 Updating the SRM Console
To update the SRM console on the Alpha 4/233 (21064a), 4/266 (21164a), 5/366, and 5/433 DMCC systems, you must choose either the SRM console or the AlphaBIOS setup. You can store only one console.
If you accidentally update both the SRM and the AlphaBIOS consoles, you will enter the AlphaBIOS Setup menu, and you will not have the option to return to the SRM console. The only way to exit the AlphaBIOS Setup menu and return to the SRM console is to use a Firmware Update Utility located at the following Internet site:
This section contains release notes pertaining to the PowerStorm 300
and Powerstorm 350 graphics cards.
B.10.1 PowerStorm 300/350 OpenVMS Graphics Support Release Notes
For release notes on the Powerstorm 300/350 PCI graphics controller support for a Compaq Workstation running OpenVMS Alpha, refer to the PowerStorm 300/350 OpenVMS Graphics Release Notes Version 1.1. You can find these release notes on the OpenVMS Documentation CD-ROM in the following directory:
Directory | File Name |
---|---|
[73.DOCUMENTATION.PS_TXT] | P300_350_REL_NOTES.PS,TXT |
These documents, release notes, and installation guides are shipped with the Graphics cards.
Starting with OpenVMS V7.3, the following parameter settings are not
relevant for PowerStorm 300 and 350 graphics cards: MAXBOBMEM,
MAXBOBS0S1, and MAXBOBS2.
B.10.2 AlphaStation 255 PowerStorm Graphics Cards
V7.3
On AlphaStation 255 systems using the PowerStorm 3D30 and 4D20 (TGA2)
graphics cards, the system no longer hangs under OpenVMS Version 7.3
when the user selects the InlayColor or InlayPlain backdrop in the
Style Manager's Backdrop dialog box.
B.11 RF73 and Other RFnn DSSI Disk Devices
Release notes in this section pertain to the RF31T, RF31T+, RF35,
RF35+, RF73, and RF74 DSSI disk devices.
B.11.1 RF73 and Other RFnn DSSI Disk Devices and Controller Memory Errors
V6.2
A problem exists with the microcode for earlier versions of RF31T, RF31T+, RF35, RF35+, RF73, and RF74 DSSI disk devices that can cause data loss. The problem can occur when reading data from one of these devices if the device has had a controller memory error (also known as an error detection and correction (EDC) error). The error could have been induced by a virtual circuit closure or faulty hardware.
Compaq advises customers with any of these devices to check their microcode revision levels. If the microcode revision levels are lower than the numbers shown in Table B-1, Compaq recommends that you update the microcode. The microcode for all models, except RF31T, RF31T+, and RF35+, is provided on the latest OpenVMS binary distribution CD-ROM.
The RF_VERS utility, a utility program that displays the microcode revision level of the DSSI disk devices, is also provided on the CD-ROM. Instructions both for using the utility program and for updating the microcode are provided in this section.
If you have an RF31T, RF31T+, or RF35+ disk drive with a version of microcode that is not supported (see Table B-1), and if you have a support contract, contact your Compaq support representative. Otherwise, contact your authorized reseller. |
The earliest supportable revision levels of the DSSI disk microcode are shown in Table B-1.
Device Type | Minimum Level with Supported Microcode |
---|---|
RF31T | T387E |
RF31T+ | T387E |
RF35 | T392D |
RF35+ | T392D |
RF36 | V427P |
RF73 | T392D |
RF74 | V427P |
To display the microcode revision level of your DSSI disk devices, perform the following steps:
$ SET PROCESS /PRIVILEGE=(DIAGNOSE,CMKRNL,SYSPRV) $ SHOW DEVICE FYA0: |
$ RUN SYS$SYSTEM:SYSGEN SYSGEN> CONN FYA0/NOADAP SYSGEN> ^Z |
$ RUN SYS$SYSTEM:SYSMAN SYSMAN> IO CONNECT FYA0: /NOADAP SYSGEN> ^Z |
The following is an example of the display produced by the RF_VERS utility:
Program Name: RF_VERS Revision Level: V1.2s NOTICE: This program does not currently support the RF72 or any HSDxx controllers. See next version for support. DSSI disks currently on this system as seen by RF_VERS Device Node Status Hardware Firmware Name Name Type Version _$22$DIA7: R4JL2I mounted RF73 T387A _$22$DIA6: R4I0BG mounted RF73 T387A _$22$DIA8: R4XLWE mounted RF73 T387A _$22$DIA2: R4FCZK mounted RF73 T387A _$22$DIA3: R4CKCG mounted RF73 T387A _$22$DIA4: R4ZKUE mounted RF73 T387A _$22$DIA9: R4GYYI mounted RF73 T387A _$22$DIA1: R4XRYI mounted RF73 T387A |
To update the microcode in your device, use the appropriate command for your device and platform from Table B-2.
Back up the disk before updating the microcode. |
Device Type | Platform | Command |
---|---|---|
RF35 | Alpha | $RUN SYS$ETC:RF35_T392F_DEC_ALPHA.EXE |
RF35 | VAX | $RUN SYS$ETC:RF35_T392F_DEC.EXE |
RF36 | Alpha | $RUN SYS$ETC:RF36_V427P_DEC_ALPHA.EXE |
RF36 | VAX | $RUN SYS$ETC:RF36_V427P_DEC.EXE |
RF73 | Alpha | $RUN SYS$ETC:RF73_T392F_DEC_ALPHA.EXE |
RF73 | VAX | $RUN SYS$ETC:RF73_T392F_DEC.EXE |
RF74 | Alpha | $RUN SYS$ETC:RF74_V427P_DEC_ALPHA.EXE |
RF74 | VAX | $RUN SYS$ETC:RF74_V427P_DEC.EXE |
Do not delete SCSI_INFO.EXE, RF_VERS.EXE, or any of the files listed in Table B-2. If these files are deleted, VMSKITBLD.COM (on VAX) will not be able to find them. Similarly, on Alpha systems, the PRODUCT INSTALL commands in AXPVMS$PCSI_INSTALL and AXPVMS$PCSI_INSTALL_MIN will fail. |
Index | Contents |
privacy and legal statement | ||
6637PRO_014.HTML |