E
AP-650 APPLICATION NOTE
Microsoft Windows*95 Support For PIIX4
October 1997
Order Number: 292208-001
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
Information in this document is provided in connection with Intel products. No license, express or implied, by estoppel or otherwise, to any intellectual property rights is granted by this document. Except as provided in Intel’s Terms and Conditions of Sale for such products, Intel assumes no liability whatsoever, and Intel disclaims any express or implied warranty, relating to sale and/or use of Intel products including liability or warranties relating to fitness for a particular purpose, merchantability, or infringement of any patent, copyright or other intellectual property right. Intel products are not intended for use in medical, life saving, or life sustaining applications. Intel may make changes to specifications and product descriptions at any time, without notice. Designers must not rely on the absence or characteristics of any features or instructions marked "reserved" or "undefined." Intel reserves these for future definition and shall have no responsibility whatsoever for conflicts or incompatibilities arising from future changes to them. The PIIX4 may contain design defects or errors known as errata which may cause the product to deviate from published specifications. Current characterized errata are available on request. *Third-party brands and names are the property of their respective owners. Copyright © Intel Corporation 1997
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E 1.0.
AP-650
PIIX4 IMPLEMENTATION AND BACKGROUND INFORMATION
The PIIX4 component is a PCI device which contains four distinct PCI Functions in PCI Configuration Space. All of the PIIX4 PCI Functions are addressable at the same PCI Bus and Device Number and share the same PCI Vendor ID of 8086h. The PIIX4 is used in conjunction with the 82439TX & 82433LX components. Their related PCI Functions and Device Numbers are also shown below. Intel 82371AB PCI to ISA bridge. This device corresponds to PCI Function 0. • This device has PCI Device ID 7110h. • Intel 82371AB PCI Bus Master IDE Controller This device corresponds to PCI Function 1 • This device has PCI Device ID 7111h. • Intel 82371AB PCI to USB Universal Host Controller This device corresponds to PCI Function 2 • This device has PCI Device ID 7112h. • Intel 82371AB Power Management Controller This device corresponds to PCI Function 3 • This device has PCI Device ID 7113h. • Intel 82439TX Pentium® Processor to PCI bridge This device corresponds to PCI Function 0 • This device has PCI Device ID 7100h. • Intel 82443LX Pentium® II Processor to PCI bridge This device corresponds to PCI Function 0 • This device has PCI Device ID 7180h. • Intel 82443LX Pentium® II Processor to AGP Controller This device corresponds to PCI Function 1 • This device has PCI Device ID 7181h. • There are two different configurations available for the Intel 82371AB PCI to ISA bridge. Both configurations have identical PCI Device ID of 7110h, as specified above. ISA configuration: This device has PCI Base Class ID 06h and Sub Class ID 01h. • This configuration requires driver support for full ISA bus. • Extended IO configuration: This device has PCI Base Class ID 06h and Sub Class ID 80h. • This device can be configured for a full ISA bus or a subset of the ISA bus called the Extended IO (EIO) bus. The use of the EIO bus allows unused signals to be configured as General Purpose Inputs and Outputs that are specified by the Platform’s BIOS or system initialization software. As a result, there are differences between the the ISA configuration and the EIO configuration of the PCI to ISA bridge device. Those differences are described in this document.
1
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
1.1.
Windows*95 Background Information
The Microsoft Windows 95* operating system currently uses special device information files (*.INF) to specify and define the characteristics of various controller and device classes of the operating system. For certain classes, the device controller’s PCI Device ID must be explicitly listed in the file for optimal operation. The system INF files are located in the following directory upon installation: C:\\INF\ The PCI Device IDs for the functions embedded in the PIIX4 component is not listed in the following versions of the Windows 95* operating system: Version 950 Windows 95 (Retail Release) Version 950A Windows 95 OEM Service Release 1 (OSR1) Version 950B Windows 95 OEM Service Release 2.0 (OSR2) or Windows 95 OEM Service Release 2.0 plus USB Supplement (OSR2.1) Check the version number of the Windows 95* operating system you are using by looking at Control Panel -> System -> General. The version information is displayed under “System:”. This Application Note will describe the additional PIIX4-specific entries that facilitate proper, optimal system operation on PIIX4-based systems. This document contains procedures that describe how to update the following INF files in Versions 950, 950A and 950B: MACHINE.INF MSHDC.INF USB.INF Other versions of Windows 95 (including future releases) are not addressed in this document. NOTE OEMs currently should contact Microsoft to receive the up to date versions of the “MSHDC.INF” file, “MACHINE.INF” file, and ”USB.INF” file or for information concerning their ability to make necessary changes to this file for production shipments.
2
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E 2.0.
AP-650
REQUIRED CHANGES TO THE BASE WINDOWS*95 INF FILES
NOTE: Some of the following procedures may need to differentiate between the version of Windows 95* operating system. Please note that the procedures only apply to the 950, 950A, and 950B Versions of Windows 95*. Procedures for other versions of Windows 95* are not specified in this document. Where applicable, both ISA and EIO configuration options will be listed. Please follow the procedure for the configuration option implemented in the system.
2.1.
Necessary Entries in "MSHDC.INF" File to Recognize the PIIX4 Component
The following text represents the portions of the MSHDC.INF file which must be verified to include the correct information. Note that the below information also shows the required data for the 82371SB PIIX3 component. The .INF files are divided into sections preceded by the section name inside square brackets. The sections may contain data for numerous devices other than PIIX3/PIIX4. Ensure that the text in each of the sections [INTEL_HDC], [Control Flags], and [Strings] matches as shown below in order for the PIIX3/PIIX4 devices to be recognized correctly. [INTEL_HDC] ;;ensure that the following lines are present: %PCI\VEN_8086&DEV_7010.DeviceDesc%=DUAL_GOOD_IDE, ,PCI\VEN_8086&DEV_7010 %PCI\VEN_8086&DEV_7111.DeviceDesc%=DUAL_GOOD_IDE, ,PCI\VEN_8086&DEV_7111 [ControlFlags] ;;ensure that the following lines are present: CopyFilesOnly=PCI\VEN_8086&DEV_7010 CopyFilesOnly=PCI\VEN_8086&DEV_7111 [Strings] ;;ensure that the following lines are present: PCI\VEN_8086&DEV_7010.DeviceDesc="Intel 82371SB PCI Bus Master IDE Controller ” PCI\VEN_8086&DEV_7111.DeviceDesc="Intel 82371AB PCI Bus Master IDE Controller ”
2.2.
Necessary Entries in "MACHINE.INF" File to Recognize the PIIX4
The following text represents the portions of the MACHINE.INF file which must be verified to include the correct information. Data for the 82371SB PIIX3, the 82439TX Pentium processor to PCI bridge, and the 82443LX Pentium II processor to PCI bridge components are also shown in addition to the PIIX4. The .INF files are divided into sections preceded by the section name inside square brackets. The sections may contain data for numerous devices other than PIIX3/PIIX4. Ensure that the text in each of the sections [MS_SYS], [PCI_DRV_AddReg] , [Control Flags], and [Strings] matches as shown below in order for the PIIX3/PIIX4 devices to be recognized correctly. Note that changes to MACHINE.INF for Windows 95* Retail (OSR1) and Windows 95* OEM Service Release 2.0 (OSR2/OSR2.1) are different and NOT interchangeable. Make sure you refer to the correct section for your operating system. Where applicable, ISA and EIO configuration options will be listed. Please follow the procedure for the configuration option implemented in the system. 3
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
2.2.1
CHANGES THAT APPLY TO SYSTEMS WITH THE WINDOWS*95 RETAIL OR OSR1 RELEASES
ISA Configuration [MS_SYS] ;;ensure that the following lines are present: %PCI\VEN_8086&DEV_7000.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7000 %PCI\VEN_8086&DEV_7110.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7110 %PCI\VEN_8086&DEV_7113.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7113 %PCI\VEN_8086&DEV_7100.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7100 %PCI\VEN_8086&DEV_7180.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7180 [PCI_DRV_AddReg] ;;ensure that the following lines are present: ; Devices specific settings (value name is DevID cat with VenID) ; Bit 0: Devices video wanting no IRQ ; Bit 1: Devices PCMCIA wanting IRQ ; Bit 2: Devices Dual PCI IDE without programming code with bit 3 set HKLM,System\CurrentControlSet\Services\VxD\PCI,70108086,1,04,00,00,00 HKLM,System\CurrentControlSet\Services\VxD\PCI,71118086,1,04,00,00,00 [ControlFlags] ;;ensure that the following lines are present: ExcludeFromSelect=PCI\VEN_8086&DEV_7000 ExcludeFromSelect=PCI\VEN_8086&DEV_7110 ExcludeFromSelect=PCI\VEN_8086&DEV_7113 ExcludeFromSelect=PCI\VEN_8086&DEV_7100 ExcludeFromSelect=PCI\VEN_8086&DEV_7180
4
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
[Strings] ;;ensure that the following lines are present: PCI\VEN_8086&DEV_7000.DeviceDesc="Intel 82371SB PCI to ISA bridge" PCI\VEN_8086&DEV_7110.DeviceDesc="Intel 82371AB PCI to ISA bridge" PCI\VEN_8086&DEV_7113.DeviceDesc="Intel 82371AB Power Management Controller" PCI\VEN_8086&DEV_7100.DeviceDesc="Intel 82439TX Pentium(R) Processor to PCI bridge" PCI\VEN_8086&DEV_7180.DeviceDesc="Intel 82443LX Pentium(R) II Processor to PCI bridge" EIO Configuration [MS_SYS] ;;ensure that the following lines are present: %PCI\VEN_8086&DEV_7000.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7000 %PCI\VEN_8086&DEV_7110.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7110 %PCI\VEN_8086&DEV_7113.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7113 %PCI\VEN_8086&DEV_7100.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7100 %PCI\VEN_8086&DEV_7180.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7180 [PCI_DRV_AddReg] ;;ensure that the following lines are present: ; Devices specific settings (value name is DevID cat with VenID) ; Bit 0: Devices video wanting no IRQ ; Bit 1: Devices PCMCIA wanting IRQ ; Bit 2: Devices Dual PCI IDE without programming code with bit 3 set HKLM,System\CurrentControlSet\Services\VxD\PCI,70108086,1,04,00,00,00 HKLM,System\CurrentControlSet\Services\VxD\PCI,71118086,1,04,00,00,00
5
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
[ControlFlags] ;;ensure that the following lines are present: ExcludeFromSelect=PCI\VEN_8086&DEV_7000 ExcludeFromSelect=PCI\VEN_8086&DEV_7110 ExcludeFromSelect=PCI\VEN_8086&DEV_7113 ExcludeFromSelect=PCI\VEN_8086&DEV_7100 ExcludeFromSelect=PCI\VEN_8086&DEV_7180 [Strings] ;;ensure that the following lines are present: PCI\VEN_8086&DEV_7000.DeviceDesc="Intel 82371SB PCI to ISA bridge" PCI\VEN_8086&DEV_7110.DeviceDesc="Intel 82371AB PCI to ISA bridge" PCI\VEN_8086&DEV_7113.DeviceDesc="Intel 82371AB Power Management Controller" PCI\VEN_8086&DEV_7100.DeviceDesc="Intel 82439TX Pentium(R) Processor to PCI bridge" PCI\VEN_8086&DEV_7180.DeviceDesc="Intel 82443LX Pentium(R) II Processor to PCI bridge"
6
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E 2.2.2
AP-650
CHANGES THAT APPLY TO SYSTEMS WITH THE WINDOWS*95 OEM SERVICE RELEASE 2.0 (OSR2) OR WINDOWS*95 OEM SERVICE RELEASE 2.0 PLUS USB SUPPLEMENT (OSR2.1) RELEASES
ISA Configuration [MS_SYS] ;;ensure that the following lines are present: %PCI\VEN_8086&DEV_7000.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7000 %PCI\VEN_8086&DEV_7110.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7110 %PCI\VEN_8086&DEV_7113.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7113 %PCI\VEN_8086&DEV_7100.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7100 %PCI\VEN_8086&DEV_7180.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7180 %PCI\VEN_8086&DEV_7181.DeviceDesc%=PCI_BRIDGE_DRV,PCI\VEN_8086&DEV_7181 [PCI_DRV_AddReg] ;;ensure that the following lines are present: ; Devices specific settings (value name is DevID cat with VenID) ; Bit 0: Devices video wanting no IRQ ; Bit 1: Devices PCMCIA wanting IRQ ; Bit 2: Devices Dual PCI IDE without programming code with bit 3 set HKLM,System\CurrentControlSet\Services\VxD\PCI,70108086,1,04,00,00,00 HKLM,System\CurrentControlSet\Services\VxD\PCI,71118086,1,04,00,00,00 ; IRQ Miniport Data HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Name,,"Intel 82371SB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Instance,1,01,00,00,00 HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\71108086,Name,,"Intel 82371AB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\71108086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\71108086,Instance,1,01,00,00,00
7
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
; IDE Miniport Data HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Name,,"Intel 82371SB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Instance,1,00,00,00,00 HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Name,,"Intel 82371AB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Instance,1,00,00,00,00 [ControlFlags] ;;ensure that the following lines are present: ExcludeFromSelect=PCI\VEN_8086&DEV_7000 ExcludeFromSelect=PCI\VEN_8086&DEV_7110 ExcludeFromSelect=PCI\VEN_8086&DEV_7113 ExcludeFromSelect=PCI\VEN_8086&DEV_7100 ExcludeFromSelect=PCI\VEN_8086&DEV_7180 ExcludeFromSelect=PCI\VEN_8086&DEV_7181 [Strings] ;;ensure that the following lines are present: PCI\VEN_8086&DEV_7000.DeviceDesc="Intel 82371SB PCI to ISA bridge" PCI\VEN_8086&DEV_7110.DeviceDesc="Intel 82371AB PCI to ISA bridge" PCI\VEN_8086&DEV_7113.DeviceDesc="Intel 82371AB Power Management Controller" PCI\VEN_8086&DEV_7100.DeviceDesc="Intel 82439TX Pentium(R) Processor to PCI bridge" PCI\VEN_8086&DEV_7180.DeviceDesc="Intel 82443LX Pentium(R) II Processor to PCI bridge" PCI\VEN_8086&DEV_7181.DeviceDesc="Intel 82443LX Pentium(R) II Processor to AGP Controller"
8
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
EIO Configuration [MS_SYS] ;;ensure that the following lines are present: %PCI\VEN_8086&DEV_7000.DeviceDesc%=ISA_DRV,PCI\VEN_8086&DEV_7000 %PCI\VEN_8086&DEV_7110.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7110 %PCI\VEN_8086&DEV_7113.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7113 %PCI\VEN_8086&DEV_7100.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7100 %PCI\VEN_8086&DEV_7180.DeviceDesc%=NO_DRV,PCI\VEN_8086&DEV_7180 %PCI\VEN_8086&DEV_7181.DeviceDesc%=PCI_BRIDGE_DRV,PCI\VEN_8086&DEV_7181 [PCI_DRV_AddReg] ;;ensure that the following lines are present: ; Devices specific settings (value name is DevID cat with VenID) ; Bit 0: Devices video wanting no IRQ ; Bit 1: Devices PCMCIA wanting IRQ ; Bit 2: Devices Dual PCI IDE without programming code with bit 3 set HKLM,System\CurrentControlSet\Services\VxD\PCI,70108086,1,04,00,00,00 HKLM,System\CurrentControlSet\Services\VxD\PCI,71118086,1,04,00,00,00 ; IRQ Miniport Data HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Name,,"Intel 82371SB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\70008086,Instance,1,01,00,00,00 HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\71108086,Name,,"Intel 82371AB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\71108086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IRQMiniports\71108086,Instance,1,01,00,00,00 ; IDE Miniport Data HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Name,,"Intel 82371SB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\70108086,Instance,1,00,00,00,00 9
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Name,,"Intel 82371AB" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Path,,"PCIMP.PCI" HKLM,System\CurrentControlSet\Services\VxD\PCI\IDEMiniports\71118086,Instance,1,00,00,00,00 [ControlFlags] ;;ensure that the following lines are present: ExcludeFromSelect=PCI\VEN_8086&DEV_7000 ExcludeFromSelect=PCI\VEN_8086&DEV_7110 ExcludeFromSelect=PCI\VEN_8086&DEV_7113 ExcludeFromSelect=PCI\VEN_8086&DEV_7100 ExcludeFromSelect=PCI\VEN_8086&DEV_7180 ExcludeFromSelect=PCI\VEN_8086&DEV_7181 [Strings] ;;ensure that the following lines are present: PCI\VEN_8086&DEV_7000.DeviceDesc="Intel 82371SB PCI to ISA bridge" PCI\VEN_8086&DEV_7110.DeviceDesc="Intel 82371AB PCI to ISA bridge" PCI\VEN_8086&DEV_7113.DeviceDesc="Intel 82371AB Power Management Controller" PCI\VEN_8086&DEV_7100.DeviceDesc="Intel 82439TX Pentium(R) Processor to PCI bridge" PCI\VEN_8086&DEV_7180.DeviceDesc="Intel 82443LX Pentium(R) II Processor to PCI bridge" PCI\VEN_8086&DEV_7181.DeviceDesc="Intel 82443LX Pentium(R) II Processor to AGP Controller"
10
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E 2.3.
AP-650
Necessary Entries in "USB.INF" File to Recognize the PIIX4
USB is only supported under Windows 95 OEM Service Release 2.0 plus USB Supplement (OSR2.1) Release. The following text represents the portions of the “USB.INF” file which must be verified to include the correct information. Note that the below information also shows the required data for the 82371SB PIIX3 component. The .INF files are divided into sections preceded by the section name inside square brackets. The sections may contain data for numerous devices other than PIIX3/PIIX4. Ensure that the text in each of the sections [Intel.Section], and [Strings] matches as shown below in order for the PIIX4/PIIX3 devices to be recognized correctly. [Intel.Section] ;;ensure the following lines are present: %PCI\VEN_8086&DEV_7020.DeviceDesc%=UniversalHCD.Dev,PCI\VEN_8086&DEV_7020 %PCI\VEN_8086&DEV_7112.DeviceDesc%=UniversalHCD.Dev,PCI\VEN_8086&DEV_7112 [Strings] ;ensure the following lines are present: Intel.Mfg="Intel" PCI\VEN_8086&DEV_7020.DeviceDesc="Intel 82371SB PCI to USB Universal Host Controller" PCI\VEN_8086&DEV_7112.DeviceDesc="Intel 82371AB PCI to USB Universal Host Controller"
3.0.
EDITING THE .INF FILES FOR SYSTEM TESTING
The following procedures can be used to modify the MSHDC.INF, MACHINE.INF, and USB.INF files for system testing of 82371AB PIIX4 under Windows 95 . It is strongly recommended that the edited MSHDC.INF and MACHINE.INF files be present at the time of installation. Although the MSHDC.INF and MACHINE.INF files can be edited after installation, it is discouraged due to potential system lockup. See Section 3.5. In order to update the USB.INF file, Windows 95 OEM Service Release 2.0 and USB Supplement must be installed first. Note: OEMs currently should contact Microsoft to receive the up to date versions of the MSHDC.INF, MACHINE.INF, and USB.INF files or for information concerning their ability to make necessary changes to this file for production shipments.
11
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
3.1.
Incorporating MACHINE.INF and MSHDC.INF Files at Time of O/S Installation
•
This is the only acceptable procedure for OSR1
•
This is the suggested procedure for High Volume Manufacturing
1.
The Windows*95 distribution CD contains a CAB directory with all the .CAB files and installation program. The name of the directory can vary depending on the distribution. (i.e. \WIN95\*.CAB, etc.) Copy the .CAB files and installation files from the Windows 95* CAB directory to a directory on the hard disk. It is recommended to prepare the subdirectory with all the necessary .CAB files and .INF files and perform installation from this subdirectory. This procedure requires a large amount of disk storage. It is important to make sure this is enough disk space before beginning the copy process.
2.
Extract the MACHINE.INF and MSHDC.INF files from the .CAB files contained on your CD. Locate the EXTRACT.EXE program either on your CD or system. You can do the extraction with the following commands: extract /a precopy1.cab machine.inf extract /a precopy1.cab mshdc.inf This command will start with the PRECOPY.CAB file and work through the chain of .CAB files until it finds MACHINE.INF and MSHDC.INF and saves them to your current directory.
3.
Make a copy of the existing MSHDC.INF and MACHINE.INF files and then edit both files according to Section 2.1 & 2.2 of this document.
4.
Run SETUP.EXE to install Windows 95*.
5.
After setup is complete, view devices in Device Manager to ensure all devices are configured correctly. If you are using Windows*95 Retail or OSR1 Releases, all devices should be set up correctly at this time. If you are using Windows 95 OEM Service Release 2.0, USB will not be set up correctly until the USB Supplement has been installed and the USB.INF file has been updated correctly. To view Device Manager: •
Run the Control Panel -> System applet
•
Click on Device Manager
•
Click on View devices by connection
•
Click on Plug and Play BIOS
•
Click on PCI bus
•
Confirm none of the PIIX4 devices are preceded with a yellow ‘!’ or ‘?’ symbol. The diagram shows an example of correct configuration of devices.
12
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
TEMP
Figure 1. Device Manager Example of PIIX4 Updated Files
13
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
3.2.
Updating the USB.INF File
At the time this document was created, USB was not available as an integral part of the operating system installation. As a result, the USB Supplement installation and USB.INF file update procedure is documented as a two-step process. 1.
In order to update the USB.INF file, Windows*95 OEM Service Release 2.0 and USB Supplement must be installed first. Install Windows 95 OSR2.1, including USB software stack (if not already done).
2.
Make copy of existing “USB.INF” file > cd \\INF\ \ \INF> copy USB.INF USB.000
3.
Edit the USB.INF file, adding the necessary information as described in section 2.3.
4.
Run the Control Panel->System applet.
5.
Click on Device Manager
6.
Click on View devices by connection.
7.
Click on Plug and Play BIOS.
8.
Click on ? PCI Universal Serial Bus.
9.
Select Remove. (See Section 3.5 Warning)
10. Select Yes to restart the system. (See Section 3.5 Warning) 11. Windows 95 will display messages when various hardware components in the system are recognized. When prompted to install a driver, select the Windows Default driver or appropriate device drivers from disk provided by the hardware manufacturer if needed. 12. Select Yes to restart the system. (Steps 10-11 may occur several times.) 13. Re-install the custom drivers from disk provided by the hardware manufacturer if needed.
3.3.
Editing MACHINE.INF and MSHDC.INF Files After O/S Installation
Please note this method of updating system files is not recommended. The preferred mechanism is to incorporate updated MACHINE.INF and MSHDC.INF files at time of installation as described in section 2.1 of this document. Do not use this procedure for OSR1 based systems. 1.
Make copy of existing MACHINE.INF and MSHDC.INF files. > cd \\INF\ \ \INF> copy MACHINE.INF MACHINE.000 \ \INF> copy MSHDC.INF MSHDC.000
2.
Edit the MSHDC.INF and MACHINE.INF files, adding the necessary information as described in section 2.1 & 2.2.
3.
Run the Control Panel->System applet.
4.
Click on Device Manager
14
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
5.
Click on View devices by connection.
6.
Click on Plug and Play BIOS.
7.
Click on PCI bus.
8.
Select Remove. (See Section 3.5 Warning)
9.
Select Yes to restart the system. (See Section 3.5 Warning)
10. Windows 95 will display messages when various hardware components in the system are recognized. When prompted to install a driver, select the Windows Default driver or appropriate device drivers from disk provided by the hardware manufacturer if needed. 11. Select Yes to restart the system. (Steps 10-11 may occur several times.) 12. Re-install the custom drivers from disk provided by the hardware manufacturer if needed.
3.4.
Restoring Original MACHINE.INF, MSHDC.INF, and USB.INF Files
If it is desired to restore the original MACHINE.INF or MSHDC.INF file: 1.
Make copy of new existing MACHINE.INF, MSHDC.INF, and USB.INF files
2.
Restore the original MACHINE.INF, MSHDC.INF, and USB.INF files C:> cd \\INF\ C:\ \INF> copy MACHINE.000 MSHDC.INF C:\ \INF> copy MSHDC.000 MSHDC.INF C:\ \INF> copy USB.000 MSHDC.INF
3. Delete PCI from Device Manager by doing the following: •
Run the Control Panel->System applet.
•
Click on Device Manager
•
Click on View devices by connection.
•
Click on Plug and Play BIOS.
•
Click on PCI bus.
•
Select Remove. (See Section 4.5 Warning)
•
Select Yes to restart the system. (See Section 4.5 Warning)
•
Windows 95 will display messages when various hardware components in the system are recognized. When prompted to install a driver, select the Windows Default driver or appropriate device drivers from disk provided by the hardware manufacturer if needed.
•
Select Yes to restart the system. (Steps 10-11 may occur several times.)
•
Re-install the custom drivers from disk provided by the hardware manufacturer if needed.
15
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
E
AP-650
3.5.
Warning - Potential System Lockup
System lockup can occur during Device Manager Remove operation or Control Panel Restart as a result of possible system issues during these operations. In the event of system lockup, restart the machine and view Device Manager. If devices are listed properly and system experiences no further problems, then .INF file update process was successful. If devices are not configured correctly or further problems are experienced, re-install Windows 95* and re-do the editing process using the pre-install method described in Section 3.1.
16
11/13/97 1:20 PM AP_650.DOC
INTEL CONFIDENTIAL (until publication date)
UNITED STATES, Intel Corporation 2200 Mission College Blvd., P.O. Box 58119, Santa Clara, CA 95052-8119 Tel: +1 408 765-8080 JAPAN, Intel Japan K.K. 5-6 Tokodai, Tsukuba-shi, Ibaraki-ken 300-26 Tel: + 81-29847-8522 FRANCE, Intel Corporation S.A.R.L. 1, Quai de Grenelle, 75015 Paris Tel: +33 1-45717171 UNITED KINGDOM, Intel Corporation (U.K.) Ltd. Pipers Way, Swindon, Wiltshire, England SN3 1RJ Tel: +44 1-793-641440 GERMANY, Intel GmbH Dornacher Strasse 1 85622 Feldkirchen/ Muenchen Tel: +49 89/99143-0 HONG KONG, Intel Semiconductor Ltd. 32/F Two Pacific Place, 88 Queensway, Central Tel: +852 2844-4555 CANADA, Intel Semiconductor of Canada, Ltd. 190 Attwell Drive, Suite 500 Rexdale, Ontario M9W 6H8 Tel: +416 675-2438
