***********************************************************
** ENU ****************************************************
***********************************************************
*
* Intel(R) Chipset Software Installation Utility
* OEM Preload Instructions
*
*
* NOTE: This document refers to systems containing the
* following Intel chipset(s):
*
* Intel(R) 810 Chipset
* Intel(R) 810E Chipset
* Intel(R) 815 Chipset
* Intel(R) 815E Chipset
* Intel(R) 815EM Chipset
* Intel(R) 820 Chipset
* Intel(R) 820E Chipset
* Intel(R) 840 Chipset
* Intel(R) 850 Chipset
* Intel(R) 440BX AGPset
* Intel(R) 440DX AGPset
* Intel(R) 440EX AGPset
* Intel(R) 440GX AGPset
* Intel(R) 440LX AGPset
* Intel(R) 440ZX AGPset
* Intel(R) 440MX Chipset
* Intel(R) 430TX PCIset
*
*
************************************************************
************************************************************
************************************************************
* CONTENTS OF THIS DOCUMENT
************************************************************
This document contains the following sections:
1. Overview
2. Contents of the Extracted Files
3. System Requirements
4. Installing the INF Files Prior to OS Installation
4A. Installing the Windows* 2000 INF Files Prior
to OS Installation
4B. Installing the Windows 98/Windows ME INF Files Prior to OS
Installation
4C. Installing the Windows 95 INF Files Prior to OS
Installation
5. Installing the INF Files After OS Installation
5A. Installing the Windows 2000 INF Files after
OS Installation
5B. Installing the Windows 98/Windows ME INF Files
after OS Installation
5C. Installing the Windows 95 INF Files after OS
Installation
6. Verifying Installation of the Software
7. Identifying the Software Version Number
8. Troubleshooting
************************************************************
* 1. OVERVIEW
************************************************************
The Intel(R) Chipset Software Installation Utility contains
Windows device installation (*.INF) files that outline to
the operating system how the chipset components shall be
configured for proper functionality of the following
features:
- Core PCI and ISAPNP Services
- AGP Support
- IDE/ATA33/ATA66 Storage Support
- USB Support
- Identification of Intel Chipset Components in
Device Manager
INF Files for Windows* 95, Windows 98, Windows ME and Windows 2000
operating systems may be extracted from this software by
executing one of the following command-line calls:
Self-extracting .EXE distribution: INFINST_ENU.EXE -A -A
Compressed .ZIP distribution : SETUP.EXE -A
The system integrator can then install these files prior
to Windows 95, Windows 98 or Windows ME OS installation.
NOTES:
1. The software and the procedures described in this
document apply to the OEM Preload Kit versions of
Windows 95, Windows 98, Windows 98 Second Edition,
Windows ME or Windows 2000.
They are not designed to work with end-user ("RETAIL")
versions of the operating systems.
2. In this document, "Windows 98" refers to either
Windows 98 or Windows 98 Second Edition.
3. The files for Windows 95 are designed to work solely with
Windows 95 (all versions). The files for Windows 98 are
designed to work solely with Windows 98. The files for
Windows 2000 are designed to work solely with
Windows 2000. The files for Windows ME are
designed to work solely with Windows ME.
4. On systems where Intel(R) Security Driver is going to be
installed, the IFWH.INF and IFWH.CAT files should not
be used or referenced in the preload. Refer to Section 9,
Troubleshooting, for more information.
5. On systems where Intel(R) LanDesk(R) driver is going to be
installed, the ICHxSMB.INF and ICHxSMB.CAT files should
not be used or referenced in the preload. Refer to Section 9,
Troubleshooting, for more information.
6. On systems where Intel(R) Ultra ATA Storage Driver is going to be
installed, the ICHxIDE.INF and ICHxIDE.CAT files should
not be used or referenced in the preload. Refer to Section 9,
Troubleshooting, for more information.
************************************************************
* 2. CONTENTS OF THE EXTRACTED FILES
************************************************************
INF files are copied to the hard disk drive after running the
Intel(R) Chipset Software Installation Utility executable with
a '-A' flag (i.e., "INFINST_ENU.EXE -A -A" or "SETUP.EXE -A").
The location of the INF files depends on whether a '-P' flag
is specified along with the '-A' flag:
1. If a '-P' flag is NOT specified, then the INF files are
copied to the following directory:
"C:\Program Files\Intel\INFINST"
2. If a '-P' flag IS specified, then the INF files are
copied to the location listed immediately after the
'-P' flag.
See README.TXT for more information on flag usage.
After INF file extraction, the INF files and components are
copied to the <INF Extract Directory>. These files and
components are categorized according to the Intel(R) Chipset
types. The following table summarizes the locations of the
INF files, by chipsets:
NOTE: The INF files are designed to update ONLY devices
not supported by the corresponding operating systems.
NOTE: "<INF Extract Directory>" is abbreviated "<IED>"
in the remainder of this section.
For each subdirectory of <IED> (e.g., 440MX, ICH, ICH2, or PIIXX),
the INF files are further classified according to the operating
systems they are designed for:
Win95Old\ ---> Contains INF files designed for the
Original Release and OSR1 versions of
Windows 95 ONLY.
Win95Cur\ ---> Contains INF files designed for the
OSR2 and later versions of
Windows 95 ONLY.
Win98\ ---> Contains INF files designed for
Windows 98 ONLY.
Win98SE\ ---> Contains INF files designed for
Windows 98 Second Edition ONLY.
Win2000\ ---> Contains INF files designed for
Windows 2000 ONLY.
Millenn\ ---> Contains INF files designed for
Windows ME ONLY.
NOTES:
1. PRELOAD.TXT is this file.
2. Files in <IED>\440MX\ directory are designed for
Intel(R) 440MX Chipset platforms.
3. Files in <IED>\ICH\ directory are designed for
Intel(R) 810, Intel(R) 810E, Intel(R) 820,
Intel(R) 840, and Intel(R) 815 Chipset platforms.
4. Files in <IED>\ICH2\ directory are designed for
Intel(R) Chipset platforms with Intel(R) 82801BA/BAM
components.
5. Files in <IED>\PIIXX\ directory are designed for
Intel(R) 430TX PCIset, Intel(R) 440BX, Intel(R) 440DX,
Intel(R) 440EX, Intel(R) 440GX, Intel(R) 440LX,
and Intel(R) 440ZX AGPset platforms.
6. INFPrelo.INF makes a CUSTOM.INF template that installs
the INF files for Intel(R) Chipsets during OS setup.
OEMs can incorporate this file into the SETUP directory
for the OEM Preload Kit.
(Refer to Section 4 for more details.)
************************************************************
* 3. SYSTEM REQUIREMENTS
************************************************************
1. The INF files included with this software are
designed to operate with the following chipset
configurations:
Intel(R) 810 Chipset
Intel(R) 810E Chipset
Intel(R) 815 Chipset
Intel(R) 815E Chipset
Intel(R) 815EM Chipset
Intel(R) 820 Chipset
Intel(R) 840 Chipset
Intel(R) 850 Chipset
Intel(R) 440BX AGPset
Intel(R) 440DX AGPset
Intel(R) 440EX AGPset
Intel(R) 440GX AGPset
Intel(R) 440LX AGPset
Intel(R) 440ZX AGPset
Intel(R) 440MX Chipset
Intel(R) 430TX PCIset
2. The software and the procedures described in this
document apply to the OEM Preload Kit versions of
the following operating systems:
Windows 95 4.00.950 (Original Release)
Windows 95 4.00.950a (OSR1)
Windows 95 4.00.950b (OSR2 without USB
Supplement)
Windows 95 4.00.950b (OSR2.1 with USB
Supplement)
Windows 95 4.00.950c (OSR2.5 with or
without USB Supplement)
Windows 98 4.10.1998 (Original Release)
Windows 98 Second Edition
4.10.2222 (Original Release)
Windows ME 4.90.3000 (Original Release)
Windows 2000 5.00.2195 (Original Release)
3. It is recommended that the software be installed on
systems with at least 32MB of system memory.
4. It is recommended that there be sufficient hard disk
space in the <TEMP> directory (typically C:\WINDOWS\TEMP)
on the system, in order to install this software.
Please check with your system provider to determine which
operating system and Intel chipset are used in your system.
************************************************************
* 4. INSTALLING THE INF FILES PRIOR TO OS INSTALLATION
************************************************************
************************************************************
* 4A. INSTALLING THE WINDOWS 2000 INF FILES PRIOR TO
* OS INSTALLATION
************************************************************
NOTE: The Windows 2000 OEM Preload Kit distribution CD
contains a setup directory with all the base OS setup
files and installation programs (WINNT.EXE and
WINNT32.EXE).
The name of the directory may vary depending on the
distribution CD (e.g., \I386\).
1. Copy the OS installation files from the Windows 2000 setup
directory to a directory on the hard disk. This
procedure requires a large amount of disk space. It
is important to make sure there is enough disk space
before beginning the copy process. This directory shall
be referred to as the <WIN2000 Setup Directory>.
2. Create the following directory structure under the
<WIN2000 Setup Directory>:
\$OEM$\$$\INF
3. Copy the Windows 2000 INF files from
<INF Extract Directory>\XXXX\Win2000 to the directory
created in Step 2 above:
<WIN2000 Setup Directory>\$OEM$\$$\INF
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
4. Create the following directory structure under the
<WIN2000 Setup Directory>:
\$OEM$\$1\drivers\IntelINF
5. Copy the Windows 2000 INF files AND the catalog files (.CAT)
from <INF Extract Directory>\XXXX\Win2000 to the directory
created in Step 4 above:
<WIN2000 Setup Directory>\$OEM$\$1\drivers\IntelINF
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
6. Either modify the default Windows 2000 installation
answer file, UNATTEND.TXT, located in <WIN2000 Setup Directory>,
or create a customized answer file. The answer file must include
the following information:
[Unattended]
OemPreinstall = Yes
OemPnPDriversPath="drivers\IntelINF"
A sample answer file for preloading the Intel(R) INF files
is available: <INF Extract Directory>\XXXX\Win2000\INFAnswr.TXT
For more information about Windows 2000 answer files and
unattended installations, please refer to the Microsoft*
Windows 2000 Guide to Unattended Setup. For more information
about the \$OEM$ folder, see the Microsoft Windows 2000
OEM Preinstallation Kit (OPK) User Guide, if you are a computer
manufacturer. Otherwise, see the Microsoft Windows 2000
Deployment Guide.
7. Run "WINNT.EXE /u:<answer file name> /s:<WIN2000 Setup Directory>"
to install Windows 2000.
************************************************************
* 4B. INSTALLING THE WINDOWS 98/WINDOWS ME INF FILES PRIOR TO
* OS INSTALLATION
************************************************************
NOTE: The Windows* 98, Windows 98 Second Edition, or Windows ME OEM
Preload Kit distribution CD contains a setup directory
with all the base OS setup files (*.CAB) and the
installation program (SETUP.EXE).
The name of the directory may vary depending on the
distribution CD (e.g., \WIN98\).
1. Copy the OS installation files from the Windows 98 setup
directory to a directory on the hard disk. This
procedure requires a large amount of disk space. It
is important to make sure there is enough disk space
before beginning the copy process. This directory shall
be referred to as the <WIN98 Setup Directory>.
2. Copy the Windows 98 INF files from the
<INF Extract Directory>\XXXX\Win98 to the setup
directory identified in Step 1 above, if you are
preloading Windows 98.
-or-
Copy the Windows 98 Second Edition INF files from
<INF Extract Directory>\XXXX\Win98SE to the setup
directory identified in Step 1 above, if you are
preloading Windows 98 Second Edition.
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
3. Depending on your <WIN98 Setup Directory> content,
there are two cases:
Case A: CUSTOM.INF file IS NOT present in the
<WIN98 Setup Directory>.
In this case, rename INFPRELO.INF to CUSTOM.INF.
Case B: CUSTOM.INF file IS present in the
<WIN98 Setup Directory>.
In this case, incorporate the content of
INFPRELO.INF into the existing CUSTOM.INF file.
For more information, refer to the guidelines
for "General Customizations for Preloaded Systems"
contained in the Microsoft OEM Preload Kit.
4. Run SETUP.EXE to install Windows 98.
************************************************************
* 4C. INSTALLING THE WINDOWS 95 INF FILES PRIOR TO OS
* INSTALLATION
************************************************************
NOTE: The Windows* 95 OEM Preload Kit distribution CD contains
a setup directory with all the base OS setup files (*.CAB)
and the Windows 95 installation program (SETUP.EXE).
The name of the directory may vary depending on the
distribution CD (e.g., \WIN95\).
NOTE: The files for Windows 95 are designed to work solely
with Windows 95 (all versions).
1. Copy the OS installation files from the Windows 95 setup
directory to a directory on the hard disk. This
procedure requires a large amount of disk space. It
is important to make sure that there is enough disk space
before beginning the copy process. This directory shall
be referred to as the <WIN95 Setup Directory>.
2. If you are installing Windows 95 Original Release or OSR1,
copy the Windows 95 INF files from <INF Extract
Directory>\XXXX\Win95Old to the setup directory identified in
Step 1 above, and then proceed to Step 4.
Otherwise, go to Step 3.
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
3. If you are installing Windows 95 OSR2 or later, copy the
Windows 95 INF files from <INF Extract Directory>\XXXX\Win95Cur
to the setup directory identified in Step 1 above.
IMPORTANT: DO NOT copy the files in the
<INF Extract Directory>\XXXX\Win95Cur\USB\
directory to the Step 1 setup directory at this
time, even if you intend to install the
USB Supplement after the OS setup.
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
4. Depending on your <WIN95 Setup Directory> content, there are
two cases:
Case A: CUSTOM.INF file IS NOT present in the
<WIN95 Setup Directory>.
In this case, rename INFPRELO.INF to CUSTOM.INF.
Case B: CUSTOM.INF file IS present in the
<WIN95 Setup Directory>.
In this case, incorporate the content of
INFPRELO.INF into the existing CUSTOM.INF file.
For more information, refer to the guidelines
for "General Customizations for Preloaded Systems"
contained in the Microsoft OEM Preload Kit.
5. Run SETUP.EXE to install Windows 95.
If you are installing Windows 95 Original Release, OSR1
or OSR2 without the USB Supplement, the installation is
complete.
Steps 6 and after are needed only if Windows 95 OSR2 or
a subsequent version is being installed, AND if you intend
to install the USB Supplement. Refer to the System
Requirements section for more information.
6. Run Device Manager to prepare for the update of the
USB device driver:
a. Click on Start.
b. Select Settings.
c. Select Control Panel.
d. Double-click on System icon.
e. Click on Device Manager tab.
f. Click on View Devices by Connection button.
g. Click on Plug and Play BIOS.
h. Click on PCI.
i. Click on PCI Universal Serial Bus.
j. Click on Remove.
7. If you are updating an Intel(R) 82440MX Chipset platform,
copy 440MXUSB.INF from the
<INF Extract Directory>\440MX\Win95Cur\USB directory to
the <WINDOWS Directory>\INF directory, and then proceed
to Step 11. Otherwise, go to Step 8.
8. If you are updating an Intel(R) 810, Intel(R) 820 or
Intel(R) 840 Chipset platform, copy ICHxUSB.INF from the
<INF Extract Directory>\ICH\Win95Cur\USB directory to the
<WINDOWS Directory>\INF directory, and then proceed to
Step 11. Otherwise, go to Step 9.
9. If you are updating an Intel(R) Chipset platform with
"ICH2" components, copy ICH2USB.INF from the
<INF Extract Directory>\ICH2\Win95Cur\USB directory to
the <WINDOWS Directory>\INF directory, and then proceed
to Step 11. Otherwise, go to Step 10.
10. If you are updating an Intel(R) Chipset platform with
PIIX3 or PIIX4 components, copy PIIXXUSB.INF from the
<INF Extract Directory>\PIIXX\Win95Cur\USB directory to
the <WINDOWS Directory>\INF directory.
11. Install the Windows 95 "USB Supplement" executable.
Follow screen prompts to reboot the system.
This completes the setup.
************************************************************
* 5. INSTALLING THE INF FILES AFTER OS INSTALLATION
************************************************************
************************************************************
* 5A. INSTALLING THE WINDOWS 2000 INF FILES AFTER OS
* INSTALLATION
************************************************************
Some Intel chipset platforms already are supported by
Windows 2000, so it may not be necessary to use
the INF files provided by this software to update
Windows 2000.
The following steps describe the installation process of
the Windows 2000 INF files. You may need to repeat these
steps to update all Intel chipset devices not supported
by Windows 2000.
1. Copy the contents of the
<INF Extract Directory>\XXXX\Win2000
directory to the root directory of the floppy disk (A:\).
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
2. Close all programs currently running on the system.
3. Click on Start.
4. Select Settings.
5. Select Control Panel.
6. Double-click on System icon.
7. Click on Hardware tab.
8. Click on Device Manager button.
9. Select "Devices by connection" under the View menu.
10. Click on MPS Uniprocessor PC -OR- MPS Multiprocessor PC.
NOTE: Only one of the above items will be displayed for
a given system.
11. Click on PCI bus.
12. Right-click on the line containing the description
PCI standard host CPU bridge
-or-
PCI standard ISA bridge
-or-
PCI standard PCI-to-PCI bridge
-or-
PCI System Management Bus
-or-
Standard Dual PCI IDE Controller
-or-
Standard Universal PCI to USB Host Controller
(This line will be selected.)
13. Select Properties from the pull-down menu.
14. Click on the Driver tab.
15. Click on Update Driver button.
16. Windows 2000 will launch the Upgrade Device Driver
Wizard. Select Next.
17. Ensure that the following choice is selected:
Search for a suitable driver for my device (recommended)
18. Insert the floppy containing the Windows 2000 INF files into
the floppy drive.
19. Select Next.
20. Windows 2000 will list locations from where the
updated driver file can be found. Ensure that the
following choice is selected:
Floppy disk drives
21. Select Next.
22. Windows 2000 should report that a driver has been
found:
(The detected device name will be displayed.)
Select Next.
23. Select Finish.
24. Restart the system when prompted to do so.
************************************************************
* 5B. INSTALLING THE WINDOWS 98/WINDOWS ME INF FILES AFTER
* OS INSTALLATION
************************************************************
Some Intel chipset platforms already are supported by
Windows 98 Second Edition, so it may not be necessary
to use the INF files provided by this software to update
these operating systems.
The following steps describe the installation process for
the Windows 98, Windows 98 Second Edition and Windows ME INF files.
You may need to repeat these steps to update all Intel
chipset devices not supported by these operating systems.
1. Depending on the operating system you intend to update,
copy the contents of one of the following directories
to the root directory of the floppy disk (A:\).
For Windows 98: <INF Extract Directory>\XXXX\Win98
For Windows 98 Second Edition: <INF Extract Directory>\XXXX\Win98SE
For Windows ME: <INF Extract Directory>\XXXX\Millenn
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
2. Close all programs currently running on the system.
3. Click on Start.
4. Select Settings.
5. Select Control Panel.
6. Double click on System icon.
7. Click on Device Manager tab.
8. Click on View Devices by Connection button.
9. Click on Plug and Play BIOS, or
Advanced Configuration and Power Interface (ACPI) BIOS.
NOTE: Only one of the above items will be displayed for
a given system.
10. Click on PCI bus.
11. Click on the line containing the description
PCI standard host CPU bridge
-or-
PCI standard ISA bridge
-or-
PCI standard PCI-to-PCI bridge
-or-
PCI System Management Bus
-or-
Standard Dual PCI IDE Controller
-or-
Standard Universal PCI to USB Host Controller
(This line will be selected.)
12. Click on the Remove button at the bottom of the window.
13. If more than one Intel chipset device needs updating, go to
Step 11 to remove more devices.
14. When prompted to restart the system, select Yes.
15. Restart the system.
16. The Windows operating system will launch the Add New Hardware Wizard.
Select Next in the dialog box that states:
"This wizard searches for new drivers for:"
17. Ensure that the following choice is selected:
Search for the best driver for your device (Recommended)
18. Select Next.
19. Insert the floppy containing the .INF files into the floppy drive.
20. Ensure that the following choice is selected:
Floppy disk drives
21. If the .INF files are not located in the root directory of the
floppy disk, also select the following and enter the path to
the .INF files needed to update this operating system:
Specify a location:
22. Select Next.
23. The Windows operating system should report that the driver has
been found and that it is "now ready to install the best driver for
this device."
24. Select Next.
25. Select Finish.
26. The Windows operating system may prompt you to install additional
drivers if more than one device was removed during Steps 11 through
13. Follow the same procedure to install the remaining Intel chipset
devices.
27. Restart the system when prompted to do so.
************************************************************
* 5C. INSTALLING THE WINDOWS 95 INF FILES AFTER OS
* INSTALLATION
************************************************************
The following steps describe the installation process for
the Windows 95 INF files. You may need to repeat these
steps to update all Intel chipset devices not supported
by these operating systems.
1. Depending on the operating system you intend to update,
copy the contents of one of the following directories
to the root directory of the floppy disk (A:\):
For Windows 95 Retail or OSR1: <INF Extract Directory>\XXXX\Win95Old
For Windows 95 OSR2 or later: <INF Extract Directory>\XXXX\Win95Cur
Note: XXXX is the directory name for the chipset of interest.
See Section 2 for more details.
2. Close all programs currently running on the system.
3. Click on Start.
4. Select Settings.
5. Select Control Panel.
6. Double-click on System icon.
7. Click on Device Manager tab.
8. Click on View Devices by Connection button.
9. Click on Plug and Play BIOS, or
Advanced Configuration and Power Interface (ACPI) BIOS.
NOTE: Only one of the above items will be displayed for
a given system.
10. Click on PCI bus.
11. Click on the line containing the description
PCI standard host CPU bridge
-or-
PCI standard ISA bridge
-or-
PCI standard PCI-to-PCI bridge
-or-
PCI System Management Bus
-or-
Standard Dual PCI IDE Controller
-or-
Standard Universal PCI to USB Host Controller
(This line will be selected.)
12. Click on the Remove button at the bottom of the window.
13. If more than one Intel chipset device needs updating, go to
Step 11 to remove more devices.
14. When prompted to restart the system, select Yes.
15. Restart the system.
16. Windows 95 will launch the Add New Hardware Wizard.
Select Next at the dialog box that states:
"This wizard searches for new drivers for:"
17. Ensure that the following choice is selected:
Search for the best driver for your device (Recommended)
18. Select Next.
19. Insert the floppy containing the .INF files into the floppy drive.
20. Ensure that the following choice is selected:
Floppy disk drives
21. If the .INF files are not located in the root directory of the
floppy disk, also select the following and enter the path to
the .INF files needed to update this operating system:
Specify a location:
22. Select Next.
23. Windows 95 should report that the driver has been found and
that it is "now ready to install the best driver for this device."
24. Select Next.
25. Select Finish.
26. The Windows operating system may prompt you to install additional
drivers if more than one device was removed during Steps 11 through
13. Follow the same procedure to install the remaining Intel chipset
devices.
27. Restart the system when prompted to do so.
************************************************************
* 6. VERIFYING INSTALLATION OF THE SOFTWARE
************************************************************
Run Device Manager to verify the correct installation and
usage of the INF files.
For Windows 95, Windows 98, Windows 98 Second Edition and Windows ME:
1. Click on Start.
2. Select Settings.
3. Select Control Panel.
4. Double-click on System icon.
5. Click on Device Manager tab.
6. Click on View Devices by Connection button.
7. Click on Plug and Play BIOS or
Advanced Configuration and Power Interface (ACPI) BIOS.
8. Click on PCI bus.
For Windows 2000 systems:
1. Click on Start.
2. Select Settings.
3. Select Control Panel.
4. Double-click on System icon.
5. Click on Hardware tab.
6. Click on Device Manager button.
7. From the View menu, select menu item Devices by connection.
8. Click on Standard PC, or
Advanced Configuration and Power Interface (ACPI) PC.
9. Click on PCI bus.
After the Device Manager is launched as described above, check the
descriptions for the following entries:
*** NOTE: Device Manager will display only the names of devices
currently detected in the system.
Intel(R) 810 Chipset:
Intel(R) 82810 System and Graphics Controller
-or-
Intel(R) 82810 DC-100 System and Graphics Controller
Intel(R) 810E Chipset:
Intel(R) 82810E DC-133 System and Graphics Controller
Intel(R) 820 Chipset, Intel(R) 820E Chipset:
Intel(R) 82820 Processor to I/O Controller
Intel(R) 82820 Processor to AGP Controller
Intel(R) 840 Chipset:
Intel(R) 82840 Processor to I/O Controller
Intel(R) 82840 Processor to AGP Controller
Intel(R) 82840 PCI Bridge
Intel(R) 82806AA PCI 64-bit Hub:
Intel(R) 82806AA Advanced Programmable Interrupt Controller
Intel(R) 82806AA PCI Bridge
Intel(R) 82806AA Controller (reserved)
Intel(R) 82801AA I/O Controller Hub (ICH):
Intel(R) 82801AA LPC Interface Controller
Intel(R) 82801AA Ultra ATA Controller
Intel(R) 82801AA USB Universal Host Controller
Intel(R) 82801AA SMBus Controller
Intel(R) 82801AA PCI Bridge
Intel(R) 82801AB I/O Controller Hub (ICH0):
Intel(R) 82801AB LPC Interface Controller
Intel(R) 82801AB Ultra ATA Controller
Intel(R) 82801AB USB Universal Host Controller
Intel(R) 82801AB SMBus Controller
Intel(R) 82801AB PCI Bridge
Intel(R) 82371AB PCI to ISA/IDE Xcelerator (PIIX4):
Intel(R) 82371AB PCI to ISA bridge (EIO mode)
Intel(R) 82371AB PCI to ISA bridge (ISA mode)
Intel(R) 82371AB Power Management Controller
Intel(R) 82371AB/EB/MB PCI Bus Master IDE Controller
Intel(R) 82371AB/EB/MB PCI to USB Universal Host Controller
Intel(R) 82371EB/MB PCI to ISA/IDE Xcelerator (PIIX4):
Intel(R) 82371EB/MB PCI to ISA bridge (EIO mode)
Intel(R) 82371EB/MB PCI to ISA bridge (ISA mode)
Intel(R) 82371EB/MB Power Management Controller
Intel(R) 82371AB/EB/MB PCI Bus Master IDE Controller
Intel(R) 82371AB/EB/MB PCI to USB Universal Host Controller
Intel(R) 82371SB PCI to ISA/IDE Xcelerator (PIIX3):
Intel(R) 82371SB PCI to ISA bridge
Intel(R) 82371SB PCI Bus Master IDE Controller
Intel(R) 82371SB PCI to USB Universal Host Controller
Intel(R) 440MX Chipset:
Intel(R) 82440MX Processor to I/O Controller
Intel(R) 82440MX PCI to ISA Bridge
Intel(R) 82440MX Power Management Controller
Intel(R) 82440MX Bus Master IDE Controller
Intel(R) 82440MX USB Universal Host Controller
Intel(R) 430TX PCIset:
Intel(R) 82443TX Processor to PCI bridge
Intel(R) 440BX AGPset, Intel(R) 440DX AGPset, Intel(R) 440ZX AGPset:
Intel(R) 82443BX/ZX/DX Processor to PCI bridge
Intel(R) 82443BX/ZX/DX Processor to AGP controller
Intel(R) 440GX AGPset:
Intel(R) 82443GX Processor to PCI bridge
Intel(R) 82443GX Processor to AGP controller
Intel(R) 440LX AGPset:
Intel(R) 82443LX Processor to PCI bridge
Intel(R) 82443LX Processor to AGP controller
Intel(R) 815 Chipset, Intel(R) 815E Chipset, Intel(R) 815EM Chipset:
Intel(R) 82815 Processor to I/O Controller - 1130
Intel(R) 82815 Processor to AGP Controller - 1131
Intel(R) 82801BA I/O Controller Hub:
Intel(R) 82801BA LPC Interface Controller - 2440
Intel(R) 82801BA PCI Bridge - 244E
Intel(R) 82801BA Ultra ATA Storage Controller - 244B
Intel(R) 82801BA/BAM SMBus Controller - 2443
Intel(R) 82801BA/BAM USB Universal Host Controller - 2442
Intel(R) 82801BA/BAM USB Universal Host Controller - 2444
Intel(R) 82801BA/BAM AC '97 Audio Controller - 2445
Intel(R) 82801BAM I/O Controller Hub:
Intel(R) 82801BAM LPC Interface Controller - 244C
Intel(R) 82801BAM PCI Bridge - 2448
Intel(R) 82801BAM Ultra ATA Storage Controller - 244A
Intel(R) 82801BA/BAM SMBus Controller - 2443
Intel(R) 82801BA/BAM USB Universal Host Controller - 2442
Intel(R) 82801BA/BAM USB Universal Host Controller - 2444
Intel(R) 82801BA/BAM AC '97 Audio Controller - 2445
Intel(R) 850 Chipset:
Intel(R) 82850 Processor to I/O Controller - 2530
Intel(R) 82850 Processor to AGP Controller - 2532
10. On certain systems, the following device may also be updated:
a. Click on View Devices by Connection button.
b. Click on Plug & Play BIOS, or
Advanced Configuration and Power Interface (ACPI) BIOS.
c. Verify that the following entry is present:
Intel(R) 82802 Firmware Hub Device -OR-
Intel(R) Security Driver
************************************************************
* 7. IDENTIFYING THE SOFTWARE VERSION NUMBER
************************************************************
The version of the software included in the distribution
package is specified in the file RELNOTES.TXT.
RELNOTES.TXT is available in English only.
The version of the software included in the distribution
package can also be identified by examining the following
registry location:
Key name: \\HKEY_LOCAL_MACHINE\Software\Intel\InfInst
Value name: version
************************************************************
* 8. TROUBLESHOOTING
************************************************************
It is assumed that the system requirements in Section 3
have been satisfied.
Issue: System locks up during Device Manager Remove or
during restart.
Solution: System lockup can occur during restart as a
result of several possible system issues. In
the event of a system lockup, restart the machine
and view the Device Manager. If devices are listed
properly and the system experiences no further
problems, then the .INF file restore process was
successful. If devices are not configured
correctly, try rerunning the procedures outlined
in Section 4 or Section 5.
If this does not fix problems or further
problems are experienced, reinstall the
operating system.
Issue: When updating the USB device for Windows 95
operating systems with the USB Supplement, the
system halts with a blue screen during USB
update or the USB device description in
Device Manager has a yellow exclamation mark
next to it.
Solution: Ensure that the all steps were followed in
Section 4C, "Installing the Windows 95 INF
Files Prior to OS Installation".
To address this problem, reinstall the
operating system according to the
directions in Section 4C.
Issue: The Intel(R) Security Driver fails to install.
Solution: The IFWH.INF file references the
Intel(r) 82802 Firmware Hub Controller device,
which also are controlled by the Intel(R) Security
Driver. The operating system can only reference
one of these driver sets.
To address this problem on systems where the
Intel(R) Security Driver will be installed
choose one of the following installation
scenarios:
A. If you choose to preload the INF files included
with this software:
1. Remove the IFWH.INF and IFWH.CAT file
references in the CUSTOM.INF file (for
Windows 95, Windows 98, and Windows 98
Second Edition ONLY).
2. Remove the IFWH.INF and IFWH.CAT files from
the <Windows Setup Directory> identified in
Section 4, Installing the
INF Files Prior to OS Installation.
3. Re-install the operating system according to
the directions in Section 4.
B. If you are loading the Windows 2000 INF files included
with this software after OS Installation:
1. Do NOT install the IFWH.INF file as described
in Section 5A.
Issue: The Intel(R) LANDesk(R) Software Package
fails to install.
Solution: The ICHxSMB.INF file references the Intel(R) 82801AA
and Intel(r) 82801AB SMBus Controllers,
which are also controlled by the SMBus Device Driver
included the Intel(R) LANDesk software package.
To address this problem on a system where the
SMBus device driver for Intel(R) LANDesk will be
installed, the user must ensure that the
ICHxSMB.INF file is not used. Choose one of the
following installation scenarios:
A. If you choose to preload the INF files included
with this software:
1. Remove the ICHxSMB.INF and ICHxSMB.CAT references
in the CUSTOM.INF file (for Windows 95, Windows 98,
and Windows 98 Second Edition ONLY).
2. Remove the ICHxSMB.INF and ICHxSMB.CAT files from
the <Windows Setup Directory> identified in
Section 4, Installing the INF Files Prior to
OS Installation.
3. Reinstall the operating system according to the
directions in Section 4.
B. If you are loading the Windows 2000 INF files included
with this software, after OS installation:
1. Do NOT install the ICHxSMB.INF file,
as described in Section 5A.
Issue: The Intel(R) Ultra ATA Storage Driver fails to install.
Solution: The ICHxIDE.INF file references the Intel(R) 82801AA
and Intel(r) 82801AB Ultra ATA Controllers,
which also are controlled by the Intel(R) Ultra ATA
Storage Driver. The operating system can only reference
one of these driver sets.
To address this problem on systems where the
Intel(R) Ultra ATA Storage Driver will be installed
choose one of the following installation
scenarios:
A. If you choose to preload the INF files included
with this software:
1. Remove the ICHxIDE.INF and ICHxIDE.CAT file
references in the CUSTOM.INF file (for
Windows 95, Windows 98 and Windows 98
Second Edition ONLY).
2. Remove the ICHxIDE.INF and ICHxIDE.CAT files from
the <Windows Setup Directory> identified in
Section 4, Installing the
INF Files Prior to OS Installation.
3. Re-install the operating system according to
the directions in Section 4.
B. If you are loading the Windows 2000 INF files included
with this software after OS Installation:
1. Do NOT install the ICHxIDE.INF file as described
in Section 5A.
************************************************************
************************************************************
* DISCLAIMER
************************************************************
Intel is making no claims of usability, efficacy or
warranty.
The INTEL SOFTWARE LICENSE AGREEMENT
(OEM / IHV / ISV Distribution & Single User)
completely defines the licensed use of this software.
************************************************************
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. 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 Corporation disclaims all warranties and liabilities
for the use of this document and the information contained
herein, and assumes no responsibility for any errors that
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.
************************************************************
************************************************************
* Third-party brands and names are the property of their
respective owners.
Copyright (c) 1998-2000, Intel Corporation
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.