**************************************************************************** **************************************************************************** * * * PIIX Bus Master IDE Drivers for Windows 95* * * Installation, Usage, and Release Note Information * * * * NOTE: * * In this document, the term "PIIX" refers to any/all of the * * following Intel PCIset devices: * * 82371FB (PIIX1) or 82371SB (PIIX3) in conjunction with * * the following Intel PCIsets: * * 430FX, 430HX, 430VX and 440FX * * * * Also, the term "processor" refers to the Intel Pentium(R) * * and Pentium(R) Pro devices ONLY. * * * **************************************************************************** **************************************************************************** **************************************************************************** * INTRODUCTION * **************************************************************************** This document describes the installation procedure and usage information for the PIIX Bus Master IDE Drivers for Windows 95*. Also included are release notes describing any problems or issues with the software which were known at the time of shipment. **************************************************************************** * CONTENTS OF THIS DOCUMENT * **************************************************************************** This document contains the following sections: System Requirements Installing the Software - Manual Method Verifying Installation of the Driver Un-installing the Software - Manual Method Troubleshooting Identifying the Software Version Number Contents of the Distribution Package Storage Devices Supported by the Driver Release Notes **************************************************************************** * SYSTEM REQUIREMENTS * **************************************************************************** Hardware: 1. The system must contain a supported processor and PIIX device as specified by the NOTE at the beginning of this document. 2. Ensure that a mouse is connected to the system. 3. Do not use any other add-in IDE (PCI or ISA) card in the system during installation. Operating System: 1. Windows 95 must be installed on the system prior to installing the driver. 2. Perform installation off of the on-board primary PIIX IDE interface. BIOS: The BIOS must properly initialize the PIIX IDE interface for bus master operation. **************************************************************************** * INSTALLING THE SOFTWARE - MANUAL METHOD * **************************************************************************** This installation procedure is specific only to the version of the driver and installation file included in this package. NOTE: This procedure assumes that the driver (IDEATAPI.MPD) and installation file (IDEATAPI.INF) are located in the same directory. Record the locations of the driver installation and Windows 95 directories before installing the driver. In order to determine if the driver is currently installed on the system, follow the directions in the "Verifying Installation of the Software" section of the document. If the driver is installed on the system, un-install the driver (following the directions in the "Un-installing the Software - Manual Method" section) PRIOR to re-installing the driver. 1. Check the System Requirements. Windows 95 must be fully installed and running on the system prior to installing the driver. 2. Close any running applications. 3. Remove references to installed real-mode IDE device drivers in the AUTOEXEC.BAT and CONFIG.SYS files (especially any drivers that control ATAPI CD-ROM and special IDE features). 4. Remove references to the default installed IDE device drivers. A. Open the Control Panel folder. B. Invoke the System applet. C. Click on the Device Manager tab. D. Select the View Devices by Type option. A list of the devices connected to the system will be displayed. E. Click on the Hard Disk Controllers record. There could be eight cases. For CASE 1, there could be up to three instances listed: Intel 82371SB PCI Bus Master IDE Controller Primary IDE controller Secondary IDE controller Go to step F for CASE 1. For CASE 2, there could be up to three instances listed: Intel 82371FB PCI Bus Master IDE Controller Primary IDE controller Secondary IDE controller Go to step F for CASE 2. For CASE 3, there could be up to three instances listed: Intel PIIX Bus Mastering PCI IDE Controller Primary IDE controller Secondary IDE controller Go to step F for CASE 3. For CASE 4, there could be up to three instances listed: Intel PIIIX Bus Mastering PCI IDE Controller Primary IDE controller Secondary IDE controller Go to step F for CASE 4. For CASE 5, there could be up to three instances listed: Intel PIIX PCI IDE Controller [Bus Mastering not supported] Primary IDE controller Secondary IDE controller Go to step F for CASE 5. For CASE 6, there could be up to three instances listed: Intel PIIIX Bus Mastering PCI IDE Controller Primary IDE controller Secondary IDE controller Go to step F for CASE 6. For CASE 7, there could be up to three instances listed: Standard Dual PCI IDE Primary IDE controller Secondary IDE controller Go to step F for CASE 7. For CASE 8, there could be up to two instances listed: Standard ESDI/IDE Controller Standard ESDI/IDE Controller Go to step G for CASE 8. NOTE FOR ALL CASES: a. The content of these text strings is dependent on the default Windows 95 INF file for hard disk controllers, MSHDC.INF. As a result, the individual controller descriptions may vary slightly from what is listed above. In this case, select the closest match. NOTES FOR CASES 1-7: b. Depending on the current system configuration, only one of the instances displayed for the Primary or Secondary IDE controllers may be displayed. c. The order in which the individual hard disk controller instances are listed may vary. NOTE FOR CASE 8: d. Depending on the current system configuration, only one of the instances may be displayed. F. Remove the Main Controller's listing (CASES 1-7). 1.) Select the main controller listing (the listing that does not have Primary or Secondary). 2.) Click on the Remove button. 3.) Select 'OK' when prompted to remove this controller. 4.) Go to step H. G. Remove the Standard ESDI/IDE Controller listings (CASE 8). NOTE: if only a single instance of the Standard ESDI/IDE Controller is visible, start with Step 2. 1.) Remove the Secondary Controller's listing. a. Select the SECOND instance of the Standard ESDI/ IDE Controller listings. b. Click on the Remove button. c. Select OK when prompted to remove this controller. 2.) Remove the Primary Controller's listing. a. Select the remaining instance of the Standard ESDI/IDE Controller listings. b. Click on the Remove button. c. Select OK when prompted to remove this controller. 3.) Go to step H. H. Select 'Yes' when prompted to re-start Windows 95; Windows 95 will re-start. 5. Install the PIIX Bus Master IDE driver when prompted to do so. A. Windows 95 will report that an IDE controller has been detected in the system. Select 'Driver from disk provided by hardware manufacturer.' B. Enter the path where the containing the driver file (IDEATAPI.MPD) and installation file (IDEATAPI.INF) into the system when prompted to do so. C. Choose 'OK' when prompted to load the driver. D. Select 'Yes' when prompted to re-start Windows 95. The IDEATAPI.MPD driver will be installed and used as long as the PIIX IDE interface is enabled. After installation, the IDEATAPI.MPD file is stored in the \System\IOSubSys directory. The IDEATAPI.INF information on the install floppy is integrated into the Windows 95 device database for automatic support of the PIIX Bus Master IDE driver and is stored in the \INF directory as one of the files named OEM.INF (name varies with system). **************************************************************************** * VERIFYING INSTALLATION OF THE SOFTWARE * **************************************************************************** In order to verify the installation of the driver: 1. Open the Control Panel folder. 2. Invoke the System applet. 3. Click on the Device Manager tab. 4. Select the View Devices by Type option. A list of the devices connected to the system will be displayed. 5. Click on the Hard Disk Controllers record. There could be three cases. For CASE 1, there could be up to three instances listed: Intel 82371SB PCI Bus Master IDE Controllers Primary Bus Master IDE Controller Secondary Bus Master IDE Controller Go to step 6 for CASE 1. For CASE 2, there could be up to three instances listed: Intel 82371FB PCI Bus Master IDE Controllers Primary Bus Master IDE Controller Secondary Bus Master IDE Controller Go to step H for CASE 2. 6 For CASE 3, there could be up to two instances listed: Intel PIIX PCI Bus Master IDE Controller Intel PIIX PCI Bus Master IDE Controller Go to step 7 for CASE 3. NOTE FOR ALL CASES: a. The content of the text strings is dependent on the driver's INF file (named IDEATAPI.INF in the driver's install directory). As a result, the individual controller descriptions may vary slightly from what is listed above. In this case, select the closest match. NOTES FOR CASES 1 and 2: b. Depending on the current system configuration, only one of the instances displayed for the Primary or Secondary IDE controllers may be displayed. c. The order in which the individual hard disk controller instances are listed may vary. NOTE FOR CASE 3: d. Depending on the current system configuration, only one of the instances may be displayed. 6. Verify the Intel 82371xx PCI Bus Master IDE Controllers Driver listing (CASES 1 and 2). 1.) Select the main controller listing (the listing that does not have Primary or Secondary). 2.) Click on the Properties button. 3.) Click on the Driver tab. 4.) Ensure that the Driver file listed is: \System\IOSubSys\IDEATAPI.MPD NOTE: if the correct driver file is not listed, the driver has not been installed. 5.) In certain releases of the driver, the driver version will be listed in the File Details portion of the dialog box. Refer to the 'Identifying the Software Version Number' section for more information. 6.) Go to Step 8. I. Verify the Intel PIIX PCI Bus Master IDE Controller Driver listings (CASE 3). NOTE: if only a single instance of the Standard ESDI/IDE Controller is visible, start with Step 2. 1.) Select the Secondary Controller's listing. a.) Select the SECOND instance of the Intel PIIX PCI Bus Master IDE Controller from the listing. b.) Click on the Properties button. c.) Click on the Driver tab. d.) Ensure that the Driver file listed is: \System\IOSubSys\IDEATAPI.MPD NOTE: if the correct driver file is not listed, the driver has not been installed. e.) In certain releases of the driver, the driver version will be listed in the File Details portion of the dialog box. Refer to the 'Identifying the Software Version Number' section for more information. 2.) Remove the Primary Controller's listing. a.) Select the remaining instance of the Intel PIIX PCI Bus Master IDE Controller from the listing. b.) Click on the Properties button. c.) Click on the Driver tab. d.) Ensure that the Driver file listed is: \System\IOSubSys\IDEATAPI.MPD NOTE: if the correct driver file is not listed, the driver has not been installed. e.) In certain releases of the driver, the driver version will be listed in the File Details portion of the dialog box. Refer to the 'Identifying the Software Version Number' section for more information. 6. Verify proper controller operation when the driver is installed (CASES 1 & 2). There should be no yellow warning symbol displayed next to the main controller instance (the instance that does not have Primary or Secondary in the text). If only one of the Primary or Secondary instances is present, there should be no yellow warning symbol next to it. If both Primary and Secondary instances are present, there should be no yellow marks next to the controller instances where devices are connected. NOTE: It is NORMAL for a yellow warning symbol to be displayed next to either the Primary or Secondary interface when there is no device connected to it. If a yellow warning symbol appears in error, the driver may not have been installed and/or may not be working properly. 7. Verify proper controller operation when the driver is installed (CASE 3). If only one instance is present, there should be no yellow warning symbol next to it. If both instances are present, there should be no yellow marks next to the instances where devices are connected. NOTE: It is NORMAL for a yellow warning symbol to be displayed next to a controller instance when there is no device connected to it. If a yellow warning symbol appears in error, the driver may not be installed and/or working properly. **************************************************************************** * UN-INSTALLING THE SOFTWARE - MANUAL METHOD * **************************************************************************** This procedure allows one to un-install the PIIX Bus Master IDE driver, and restore the default Windows 95 driver for IDE support. This un-install procedure is specific only to the version of the driver and installation file included with this package. Depending on the configuration of the system, subsequent re-installations of the driver may require an entirely new installation of the Windows 95 operating system. NOTE: Record the locations of the driver installation and Windows 95 directories before un-installing the driver. 1. Close any running applications. 2. Un-install the PIIX Bus Master IDE driver. A. Delete the associated .INF file. 1.) Go to the INF directory. a. Invoke the MS-DOS* Prompt applet. b. Type: cd \INF 2.) Determine which .INF file to delete. The *.INF file for the PIIX Bus Master IDE driver is located in one of the files named either: IDEATAPI.INF (if the auto-install method was followed) -OR- OEM.INF (if the manual method was followed). In the OEM.INF case, There may be one or more of these OEM.INF files loaded on the system. To determine the correct one to delete, perform a file compare between each of the OEM.INF files and the IDEATAPI.INF file located in the driver install directory. Other devices may have an OEM.INF file associated with them, so it is important to select the correct one. Another way to determine the correct OEM.INF file to delete is to use the FIND command. Change to the INF directory and locate all OEM.INF (oem0.inf, oem1.inf, etc.) files. PIIX_HDC is a unique pattern contained in the drivers inf file. For example,to determine if OEM0.INF is the correct INF file, type: find /I "PIIX_HDC" oem0.inf If oem0.inf is the correct file then this message will be printed: "-------OEM.INF %INTEL%=PIIX_HDC [PIIX_HDC]" If this is not the case, repeat for each OEM.INF file in the INF directory. 3.) Delete the correct driver INF file. B. Delete the associated driver file. 1.) Go to the IOSUBSYS directory. a. Invoke the MS-DOS Prompt applet. b. Type: cd \SYSTEM\IOSUBSYS 2.) Delete the driver binary file: del IDEATAPI.MPD C. Open the Control Panel folder. D. Invoke the System applet. E. Click on the Device Manager tab. F. Select the View Devices by Type option. A list of the devices connected to the system will be displayed. G. Click on the Hard Disk Controllers record. There could be three cases. For CASE 1, there could be up to three instances listed: Intel 82371SB PCI Bus Master IDE Controllers Primary Bus Master IDE Controller Secondary Bus Master IDE Controller Go to step H for CASE 1. For CASE 2, there could be up to three instances listed: Intel 82371FB PCI Bus Master IDE Controllers Primary Bus Master IDE Controller Secondary Bus Master IDE Controller Go to step H for CASE 2. For CASE 3, there could be up to two instances listed: Intel PIIX PCI Bus Master IDE Controller Intel PIIX PCI Bus Master IDE Controller Go to step I for CASE 3. NOTE FOR ALL CASES: a. The content of the text strings is dependent on the driver's INF file (named IDEATAPI.INF in the driver's install directory). As a result, the individual controller descriptions may vary slightly from what is listed above. In this case, select the closest match. NOTES FOR CASES 1 and 2: b. Depending on the current system configuration, only one of the instances displayed for the Primary or Secondary IDE controllers may be displayed. c. The order in which the individual hard disk controller instances are listed may vary. NOTE FOR CASE 3: d. Depending on the current system configuration, only one of the instances may be displayed. H. Remove the Intel 82371xx PCI Bus Master IDE Controllers listing (CASES 1 and 2). 1.) Select the main controller listing (the listing that does not have Primary or Secondary). 2.) Click on the Remove button. 3.) Select 'OK' when prompted to remove this controller. 4.) Go to step J. I. Remove the Intel PIIX PCI Bus Master IDE Controller listings (CASE 3). NOTE: if only a single instance of the Standard ESDI/IDE Controller is visible, start with Step 2. 1.) Remove the Secondary Controller's listing. a. Select the SECOND instance of Intel PIIX PCI Bus Master IDE Controller from the listing. b. Click on the Remove button. c. Select OK when prompted to remove this controller. 2.) Remove the Primary Controller's listing. a. Select the remaining instance of Intel PIIX PCI Bus Master IDE Controller from the listing. b. Click on the Remove button. c. Select OK when prompted to remove this controller. J. Select Yes when prompted to re-start Windows 95; Windows 95 will re-start. 3. Install the default Windows 95 drivers when prompted to do so. A. Windows 95 will report that an IDE controller has been detected. Select the Windows default driver for installation. B. Select Yes when prompted to re-start Windows 95. **************************************************************************** * TROUBLESHOOTING * **************************************************************************** The following procedure assumes that the hardware/software requirements from above have been satisfied. The following procedure also assumes that the installation of the driver was performed as described in the 'Verifying Installation of the Driver' section. Refer to the 'Release Notes' section of the document for additional information. COMMON PROBLEMS: **************** 1. The device is incompatible with PCI Bus Master IDE operation. This is due to the fact that the device does not work properly when accessed in a PCI Bus Master IDE fashion. Contact the device manufacturer for more information. 2. Verify the length of the cables that are being used to connect the IDE or ATAPI devices to the primary and secondary PIIX IDE interfaces. The length of these cables from END-TO-END should not exceed 18 inches (0.46 m). Furthermore, the capacitance of the cable should not exceed 35 pF. 3. A conflict between the PIIX Bus Master IDE driver and a real-mode ATAPI CD-ROM or IDE device driver may occur if the real-mode driver references have not been properly removed from the AUTOEXEC.BAT and/or CONFIG.SYS files. This conflict occurs when the PIIX Bus Master IDE driver attempts to access the legacy ISA IDE resources to control the PIIX. ALL REFERENCES TO REAL-MODE DRIVERS (IDE or ATAPI) IN THE AUTOEXEC.BAT AND CONFIG.SYS MUST BE REMOVED. **************************************************************************** * IDENTIFYING THE SOFTWARE VERSION NUMBER * **************************************************************************** The driver's version can be determined by using one or more of the following procedures. PROCEDURE 1: Reading Windows* properties embedded in the driver file while the driver is installed. When the driver is installed, the driver version can be obtained through the Control Panel->System applet. This procedure is described in the 'Verifying Installation of the Driver' section. PROCEDURE 2: Reading Windows* properties embedded in the driver file when the driver is not installed. When the driver is not installed, the driver version can be obtained by querying the driver file's properties under My Computer. 1. Invoke the My Computer applet. 2. Select the path containing the driver file. 3. Select the driver file, IDEATAPI.MPD. 4. Open the File menu. 5. Click on the Properties item. 6. Click on the Version tab. 7. The driver's version should be listed in the 'Product Version' portion of the dialog. PROCEDURE 3: Using the SEEVER.EXE utility when Windows* properties are not embedded in the driver file. If procedures 1 or 2 failed to describe the version of the driver, the SEEVER.EXE utility may be used to determine the current driver version. The following procedure uses the SEEVER.EXE utility to identify the version number and build date of the PIIX Bus Master IDE driver. This procedure assumes that the SEEVER.EXE utility and the driver file (IDEATAPI.MPD) are in the same working directory. 1. Open an MS-DOS command window. 2. Go to the directory where the driver is installed: Type cd \System\IOSubSys 3. Run the version identification utility (SEEVER.EXE): Type \SEEVER IDEATAPI.MPD Assumes that SEEVER.EXE is located in the driver's installation directory. **************************************************************************** * CONTENTS OF THE DISTRIBUTION PACKAGE * **************************************************************************** The PIIX Bus Master IDE Driver for Microsoft Windows 95 package contains the following items: 1. PIIX Bus Master IDE Driver: IDEATAPI.MPD 2. Installation File: IDEATAPI.INF 3. Readme File: README.TXT 4. Version Identification Utility: SEEVER.EXE **************************************************************************** **************************************************************************** * STORAGE DEVICES SUPPORTED BY THE DRIVER * **************************************************************************** The driver supports only ATA fixed disk and ATAPI CD-ROM devices connected to the PIIX IDE interface. The driver does not support ATAPI tape drives. During initialization, the driver will auto-identify all the devices connected to the PIIX IDE interface. Depending on the capabilities of the devices connected to the system, the driver will initialize the PIIX IDE interface for bus mastering operation. Only ATA fixed disk and ATAPI CD-ROM devices identified as bus master capable will be accessed as a bus master; all other ATA fixed disk and ATAPI CD-ROM devices will be accessed in a PIO-only fashion. In general, bus mastering is possible for ATA fixed disk and ATAPI CD-ROM devices that support the following DMA timing modes: Single Word DMA Mode 2 Multi-Word DMA Mode 1 Multi-Word DMA Mode 2 These devices will be accessed by the driver in either a bus mastering or a PIO-fashion, depending on the specific transfer conditions. Devices that do not support the DMA timing modes listed above, or whose PIO timings are faster than their DMA timings, will be accessed in a PIO-fashion ONLY. For more information and a list of tested devices, see the RELEASE NOTES section of this document. **************************************************************************** * RELEASE NOTES * **************************************************************************** **************************************************************************** * RELEASE NOTE OVERVIEW * **************************************************************************** The release notes describe the current, known state of the PIIX Bus Master IDE Driver for Windows 95. The release notes are divided into three sections: General Release Information Release-Specific Troubleshooting Information Release Testing Information **************************************************************************** * GENERAL RELEASE INFORMATION * **************************************************************************** The driver supports general CD-ROM operations such as: file transfers, data streaming and audio. Advanced CD-ROM applications/features (VideoCD*, CDPlus*, multi-CD changers, etc), especially those outside of the scope of the current Windows 95 CD-ROM support, have not been tested with this driver. If a problem is encountered, un-install the driver. Since the driver does not support ATAPI tape drives, this release of the driver should not be installed on systems with ATAPI tape drives. If the driver has been installed on a system with an ATAPI tape drive and problems are experienced, un-install the driver. **************************************************************************** * RELEASE-SPECIFIC TROUBLESHOOTING INFORMATION * **************************************************************************** Verifying the installation of the driver and other generic troubleshooting is discussed in the "TROUBLESHOOTING" section above. This section describes release-specific troubleshooting. This section contains a list of known problems with certain system configurations discovered during testing of the driver. A list of all storage devices tested with the driver is given below in the "RELEASE TESTING INFORMATION" section of this document. If the solution given to any of the problems listed below is to un-install the driver, follow the un-installation instructions outlined above in the section "UN-INSTALLING THE SOFTWARE". Issue: The system does not operate reliably or fails to boot when the driver is installed. Solution: Un-install the driver. Issue: The system fails to boot in NORMAL (non-SAFE-MODE) mode when the driver is installed. Solution: Un-install the driver. Issue: One or more of the IDE/ATAPI drives on the system fail to perform correctly and/or is not recognized by the driver. Solution: Ensure that devices on the system are connected according to the manufacturers' documentation. If the system still fails to operate reliably, Un-install the driver. Issue: The CD-ROM drive fails to perform correctly after the driver has been installed (e.g. audio CD-ROMs or advanced CD-ROM applications fail to perform correctly). Solution: A conflict between the PIIX Bus Master IDE driver and a real-mode ATAPI CD-ROM device driver may have occurred. This conflict occurs when both the real-mode driver and the PIIX Bus Master IDE driver attempt to access the resources of the PIIX controller. If the drive fails to operate in the case that NO real-mode driver for the device is installed, Un-install the driver. Issue: The driver is not compatible with EZ-Drive* floppy boot protection option. Solution: If EZ-Drive is installed on the boot drive, the floppy boot protection option must be disabled prior to installing the PIIX Bus Master IDE Driver for Windows 95. If, for any reason, the floppy boot protection cannot be disabled, the driver should not be installed. Issue: The driver does not support CD-ROM audio playback with the following CD-ROM drives: Gallant GCD-R542B Mitsumi FX400 Torisan S1G Torisan C3G Toshiba XM-5302B Wearnes CDD-220 Solution: Do not install the driver in configurations equipped with these CD-ROM drives. Issue: The driver does not support the following fixed disk drives: Conner CFA850A Maxtor 71626A Maxtor 71260AT Solution: Do not install the driver in configurations equipped with these fixed disk drives. **************************************************************************** * RELEASE TESTING INFORMATION * **************************************************************************** This section contains information on how the driver was tested, including a list of storage devices used in testing. If any problems are encountered running the driver with devices listed below, refer to the "RELEASE-SPECIFIC TROUBLESHOOTING INFORMATION" section above for more detailed information. The following fixed disk drives were tested with the PIIX Bus Master IDE Driver: Conner*: CFA540A CFA850A CFA1275A CFS425A CFS850A CFS1275A IBM*: DALA-3540 DALA-31080 Maxtor*: 7245AT 7540AV 71260AT 71626AP Quantum*: FB540A FB640A FB1080A FB1280A LPS270A TRB420A TRB850A Seagate*: ST5660A ST5850A ST51080A ST31220A ST31270A ST32140A Western Digital*: AC2420 AC2510 AC2700 AC2850 AC31000 AC31600 AC21000 The following ATAPI CD-ROM drives were tested with the PIIX Bus Master IDE Driver: Gallant*: GCD-R542B Hitachi*: 7730 CDR-7930 Matshita*: CR581 Mitsumi*: FX001DE FX400 FX400B FX400C FX600S FX600T NEC*: CDR260R CDR271 CDR272 Panasonic*: CD-574B Philips*: CM207 Sanyo*: CRD-S54P Sony*: CDU55E CDU76E CDU77E TEAC*: CD44E CD56E Torisan*: S1G C3G Toshiba*: XM5302B Vertos*: V300HPD Wearnes*: CDD-120 CDD-220 **************************************************************************** Intel is making no claims of usability, efficacy or warranty. The Shrink Wrap Software License Agreement completely defines the license and use of the PIIX Bus Master IDE Driver. **************************************************************************** **************************************************************************** * Intel Corporation disclaims all warranties and liabilities for the use * * of this document and the information contained herein, and assumes no * * responsibility for any errors which may appear in this document, nor * * does Intel make a commitment to update the information contained herein. * * Intel reserves the right to make changes to this document at any time, * * without notice. * **************************************************************************** **************************************************************************** * Other brands and names are the property of their respective owners. Copyright (c) Intel Corporation, 1995-1996 *** Document Header Revision Information: *** $Revision: 1.3 $ *** $Date: Apr 26 1996 12:51:38 $ *** Installation and Usage Documentation Revision Information: *** $Revision: 1.12 $ *** $Date: May 09 1996 08:36:30 $ *** Release Note Revision Information: *** $Revision: 1.9 $ *** $Date: May 09 1996 08:36:32 $ *** Release Testing Revision Information: *** $Revision: 1.1 $ *** $Date: May 09 1996 09:37:52 $ *** Disclaimer Revision Information: *** $Revision: 1.2 $ *** $Date: Mar 06 1996 10:49:56 $