***********************************************************
** ENU ***************************************************
***********************************************************
*
* Intel(R) Chipset Software Installation Utility
* Installation Readme
*
************************************************************
************************************************************
************************************************************
* CONTENTS OF THIS DOCUMENT
************************************************************
This document contains the following sections:
1. Overview
2. System Requirements
3. Contents of the Distribution Package
4. List of Available Command Line Flag Options
5. Contents of the Extracted Files
6. Installing the Software in Interactive Mode
7. Installing the Software in Silent Mode
8. Installing the INF Files Prior to OS Installation
8A. Installing the Windows* 2000 INF Files Prior
to OS Installation
8B. Installing the Windows* 98/Windows 98 SE/Windows* Me
INF Files Prior to OS Installation
8C. Installing the Windows* 95 INF Files Prior to OS
Installation
9. Installing the INF Files After OS Installation
9A. Installing the Windows* 2000 INF Files after
OS Installation
9B. Installing the Windows* 98/Windows* 98 SE/Windows* Me/
Windows* 95 INF Files after OS Installation
10. Verifying Installation of the Software
11. Identifying the Software Version Number
12. Troubleshooting
************************************************************
* 1. OVERVIEW
************************************************************
The Intel(R) Chipset Software Installation Utility installs
to the target system the Windows* INF files that outline to
the operating system how the chipset components will be
configured. This is needed for the proper functioning 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
This software can be installed in three modes: Interactive,
Silent and Unattended Preload. The Interactive Mode
requires user input during installation; the Silent Mode and
Unattended Preload do not.
Additionally, this software offers a set of command line
flag options that enable extended installation functionality.
The command line flags are not case-sensitive. See Section
4 for detailed descriptions of these flags.
Important Note:
The Intel(R) Chipset Software Installation Utility is
distributed in two formats -- self extracting .EXE files
(INFINST_xxx.EXE) or compressed .ZIP files (INFINST_xxx.ZIP).
Depending on which distribution format is being executed,
the command-line syntax may differ. See Section 4 for more
details.
************************************************************
* 2. SYSTEM REQUIREMENTS
************************************************************
1. The software included with this distribution package is
designed to operate with the following chipset
configurations:
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
Intel(R) 810 Chipset
Intel(R) 810E Chipset
Intel(R) 810E2 Chipset
Intel(R) 815 Chipset
Intel(R) 815E Chipset
Intel(R) 815EM Chipset
Intel(R) 815EP Chipset
Intel(R) 815P Chipset
Intel(R) 820 Chipset
Intel(R) 820E Chipset
Intel(R) 840 Chipset
Intel(R) 850 Chipset
Intel(R) 860 Chipset
2. One of the following operating systems must be
fully installed and running on the system
before installing this software:
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 SE 4.10.2222 (Original Release)
Windows* Me 4.90.3000 (Original Release)
Windows* 2000 5.00.2195 (Original Release)
Windows* XP 5.00.2296 (Beta 1)
To verify which operating system has been installed onto
the target system, follow the steps below:
a. Click on Start.
b. Select Settings.
c. Select Control Panel.
d. Double-click on the System icon.
e. Click on the General system properties tab.
f. Verify, which OS has been installed by reading
the System information.
3. It is recommended that the software be installed on systems
with at least 32MB of system memory when using Windows* 9x and
Windows* Me. Windows* 2000 requires at least 64MB of system memory.
4. It is recommended that there be sufficient hard disk
space in the directory (typically C:\WINDOWS\TEMP)
on the system, in order to install this software.
5. Check the System Requirements. The operating system
must be fully installed and running on the system before
running this software.
6. Close any running applications. Otherwise, you may
experience difficulties.
7. It is recommended that the Intel(R) Chipset Software
Installation utility be installed onto the target system
prior to the installation of other drivers.
Please check with your system provider to determine which
operating system and Intel chipset are used in your system.
************************************************************
* 3. CONTENTS OF THE DISTRIBUTION PACKAGE
************************************************************
The Intel(R) Chipset Software Installation Utility package
contains the following items:
File(s)
-------
INFINST_xxx.EXE -or- INFINST_xxx.ZIP
README.TXT, RELNOTES.HTM
RELNOTES.HTM is available in English only.
*** NOTE: Only the files that reference the currently
detected devices are copied to the system.
For a complete list of the INF files, refer to
the RELNOTES.HTM file.
If the -A option is exercised, the files are
not copied to the \INF directory.
See Section 4 for more information.
************************************************************
* 4. LIST OF AVAILABLE COMMAND LINE FLAG OPTIONS
************************************************************
The Intel(R) Chipset Software Installation Utility supports
several command line flags for various installation options.
All command line flags and parameters must be separated by a
space, except for the language code after the '-L' flag.
Due to the different distribution formats available for the
Intel(R) Chipset Software Installation Utility, the command
line flag syntax may vary:
1. Self-Extracting .EXE Distribution:
When installing this software using the .EXE distribution,
an extra '-A' must be appended to the INFINST_xxx.EXE
program call (i.e. INFINST_ENU.EXE -A) in order to
successfully pass command line parameters. The extra
'-A' flag for the self-extracting .EXE package
is DIFFERENT from the '-A' command line flag option
described below.
Example: To extract INF files using the '-A' flag
described below, the installation program
should be invoked as follows:
INFINST_ENU.EXE -A -A (optional -P)
2. Compressed .ZIP Distribution:
When installing this software using the .ZIP distribution,
there is no need to append any extra flags to the SETUP.EXE
program call in order to pass command line flags.
Example: To extract INF files using the '-A' flag
described below, the installation program
should be invoked as follows:
SETUP.EXE -A (optional -P)
Below is a list of all the available command line flags that
may be used with the program call. Note that the '-L' and
the '-S' flags MUST be specified at the end of the command line
flag list.
Flag Description
---- -----------
-? Help flag. Displays the list of available command line
flags. This parameter works in the Interactive mode only.
-A Extracts the INF files and README.TXT to either
"C:\Program Files\Intel\InfInst" or the
directory specified using the '-P' flag. The software will
NOT install these INF files to the system. This flag can
be combined only with the '-P' flag option. All other
options will be ignored if the '-A' flag is specified.
This parameter works in either Silent mode or Interactive
mode.
-B Automatically reboots the system after installation.
This flag is ignored if '-A' flag is specified. This
parameter works in either Silent mode or Interactive mode.
-L Forces the InstallShield user interface to
display the specified language during setup.
Note that there should be NO spaces between '-L'
and the 4-digit language code (see below). This
flag and the '-S' flag must be placed at the end
of the command line flag list. This parameter works
in Interactive mode only.
-OVER AUD Overrides the default behavior of the installer with respect
to update of the Audio controller device.
-P
Specifies the HDD location to which the INF program
files are copied. If this flag is not specified
at the command line, the
directory is by default assumed to be:
C:\Program Files\Intel\INFInst
If this flag is used without the
'-A' option, only README.TXT will
be copied to . The directory name can
include spaces. In this case, however, a pair of double
quotes (") must enclose the directory name. This parameter
works in either Silent mode or Interactive mode.
-S Runs the Installer in silent mode. No user interface
is displayed. This flag and the '-L' flag
must be placed at the end of the command line
flag list.
Below are the language codes used with the '-L' flag:
Language
-------- ----------
Chinese (PRC) 0804
Chinese (Taiwan) 0404
Danish 0006
Dutch 0013
English (US) 0409
Finnish 000B
French (Canadian) 0C0C
French (Standard) 040C
German 0007
Italian 0010
Japanese 0011
Korean 0012
Norwegian 0014
Polish 0015
Portuguese (Brazilian) 0416
Portuguese (Standard) 0816
Russian 0019
Spanish 000A
Swedish 001D
Thai 001E
************************************************************
* 5. 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 . 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: "" is abbreviated ""
in the remainder of this section.
For each subdirectory of (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.
WinME\ ---> Contains INF files designed for
Windows* Me ONLY.
WinXP\ ---> Contains INF files designed for
Windows* XP ONLY.
NOTES:
1. Files in \440MX\ directory are designed for
Intel(R) 440MX Chipset platforms.
2. Files in \ICH\ directory are designed for
Intel(R) 810, Intel(R) 810E, Intel(R) 820,
Intel(R) 840, and Intel(R) 815 Chipset platforms.
3. Files in \ICH2\ directory are designed for
Intel(R) Chipset platforms with Intel(R) 82801BA
components.
4. Files in \ICH2M\ directory are designed for
Intel(R) Chipset platforms with Intel(R)
82801BAM components.
5. Files in \ICH3M\ directory are designed for
Intel(R) Chipset platforms with Intel(R) 82801CAM
components.
6. Files in \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.
7. 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 8 for more details.)
************************************************************
* 6. INSTALLING THE SOFTWARE IN INTERACTIVE MODE
************************************************************
1. Verify that all system requirements have been met as described
in section 2.
2. Run the InstallShield* installation program:
Self-extracting .EXE distribution: INFINST_xxx.EXE
Compressed .ZIP distribution : SETUP.EXE
3. You will be prompted to agree to the license agreement.
If you do not agree, the Installer will exit before
extracting any files.
4. Follow the on-screen instructions and use the default
settings to complete the setup, once the operating
system has rebooted.
5. This completes the installation of the Intel(R) Chipset
Software Installation Utility.
************************************************************
* 7. INSTALLING THE SOFTWARE IN SILENT MODE
************************************************************
1. Verify that all system requirements have been met as described
in section 2.
2. Run the InstallShield installation program:
For silent install with auto-reboot:
Self-extracting .EXE distribution: INFINST_xxx.EXE -a -b -s
Compressed .ZIP distribution : SETUP.EXE -b -s
- OR -
For silent install without auto-reboot:
Self-extracting .EXE distribution: INFINST_xxx.EXE -a -s
Compressed .ZIP distribution : SETUP.EXE -s
3. The utility will perform the necessary updates and record
the installation status in the following system registry
key:
HKEY_LOCAL_MACHINE\Software\Intel\INFInst
4. If the utility was invoked with the "-b" flag, the
system will automatically reboot if the update was
successful.
NOTE: The system MUST be rebooted for all device updates
to take effect.
5. To determine whether the install was successful, verify
the 'install' value in the registry key specified in Step 4.
The following table describes the various parameter values:
Value Type Data Description
------ ---- ---- -----------
"install" String "success" The installation was successful.
"fail" The installation was not successful.
No INF files were copied to the
system.
"reboot" String "Yes" A reboot is required to complete
the installation.
"No" No reboot is required to complete
the installation.
"version" String Current version number of the
Intel(R) Chipset Software
Installation Utility
************************************************************
* 8. INSTALLING THE INF FILES PRIOR TO OS INSTALLATION
************************************************************
1. Copy the OS installation files from the 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. The directories shall
be referred to as follows:
Windows 2000 :
Windows 98 :
Windows 98 SE :
Windows Me :
Windows 95 :
************************************************************
* 8A. 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. Create the following directory structure under the
:
\$OEM$\$$\INF
2. Copy the Windows* 2000 INF files from
\XXXX\Win2000 to the directory
created in Step 2 above:
\$OEM$\$$\INF
Note: XXXX is the directory name for the chipset of
interest. See Section 8 for more details.
3. Create the following directory structure under the
:
\$OEM$\$1\drivers\IntelINF
4. Copy the Windows* 2000 INF files AND the catalog files
(.CAT) from \XXXX\Win2000 to the
directory created in Step 4 above:
\$OEM$\$1\drivers\IntelINF
Note: XXXX is the directory name for the chipset of
interest. See Section 8 for more details.
5. Either modify the default Windows* 2000 installation
answer file, UNATTEND.TXT, located in , 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) Chipset
Software Installation utility files is available:
\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.
6. Run "WINNT.EXE /u: /s:" to install Windows* 2000.
************************************************************
* 8B. INSTALLING THE WINDOWS* 98/Windows* 98 SE/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 Windows* 98 INF files from the
\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
\XXXX\Win98SE to the setup
directory identified in Step 1 above, if you are
preloading Windows* 98 Second Edition.
-or-
Copy the Windows* Me INF files from
\XXXX\WinME to the setup
directory identified, if you are
preloading Windows* Me.
Note: XXXX is the directory name for the chipset of
interest. See Section 8 for more details.
2. Depending on your content,
there are two cases:
Case A: CUSTOM.INF file IS NOT present in the
.
In this case, rename INFPRELO.INF to CUSTOM.INF.
Case B: CUSTOM.INF file IS present in the
.
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.
3. Run SETUP.EXE to install Windows* 98.
************************************************************
* 8C. 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. If you are installing Windows* 95 Original Release or
OSR1, copy the Windows* 95 INF files from \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 8 for more details.
2. If you are installing Windows* 95 OSR2 or later, copy
the Windows* 95 INF files from \XXXX\Win95Cur to the setup directory
identified in Step 1 above.
IMPORTANT: DO NOT copy the files in the
\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 8 for more details.
3. Depending on your content,
there are two cases:
Case A: CUSTOM.INF file IS NOT present in the
.
In this case, rename INFPRELO.INF to
CUSTOM.INF.
Case B: CUSTOM.INF file IS present in the
.
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* 95.
If you are installing Windows* 95 Original Release, OSR1
or OSR2 without the USB Supplement, the installation is
complete.
Steps 5 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.
5. 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.
6. If you are updating an Intel(R) 82440MX Chipset
platform, copy 440MXUSB.INF from the
\440MX\Win95Cur\USB directory to
the \INF directory, and then proceed
to Step 11. Otherwise, go to Step 8.
7. If you are updating an Intel(R) 810, Intel(R) 820 or
Intel(R) 840 Chipset platform, copy ICHxUSB.INF from
the \ICH\Win95Cur\USB directory
to the \INF directory, and then
proceed to Step 11. Otherwise, go to Step 9.
8. If you are updating an Intel(R) Chipset platform with
"ICH2" components, copy ICH2USB.INF from the
\ICH2\Win95Cur\USB directory to
the \INF directory, and then proceed
to Step 11. Otherwise, go to Step 10.
9. If you are updating an Intel(R) Chipset platform with
PIIX3 or PIIX4 components, copy PIIXXUSB.INF from the
\PIIXX\Win95Cur\USB directory to
the \INF directory.
10. Install the Windows* 95 "USB Supplement" executable.
Follow screen prompts to reboot the system.
This completes the setup.
************************************************************
* 9. INSTALLING THE INF FILES AFTER OS INSTALLATION
************************************************************
************************************************************
* 9A. 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
\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 8 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.
************************************************************
* 9B. INSTALLING THE WINDOWS* 98/Windows* 98 SE/WINDOWS* Me/
* WINDOWS* 95 INF FILES AFTER OS INSTALLATION
************************************************************
Some Intel chipset platforms already are supported by
Windows* 98 Second Edition and Windows* Me, 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, Windows* Me and
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* 98:
\XXXX\Win98
For Windows* 98 Second Edition:
\XXXX\Win98SE
For Windows* Me:
\XXXX\WinME
For Windows* 95 Retail or OSR1:
\XXXX\Win95Old
For Windows* 95 OSR2 or later:
\XXXX\Win95Cur
Note: XXXX is the directory name for the chipset of
interest.
See Section 8 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.
************************************************************
* 10. VERIFYING INSTALLATION OF THE SOFTWARE
************************************************************
Run Device Manager to verify the correct installation and
usage of the INF files.
For Windows* 95, Windows* 98 and 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:
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 Microsoft ACPI Compliant System
10. 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) 810E2 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) 815EP 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/82860 Processor to AGP Controller - 2532
Intel(R) 860 Chipset:
Intel(R) 82860 Processor to I/O Controller - 2531
Intel(R) 82850/82860 Processor to AGP Controller - 2532
Intel(R) 82860 PCI Bridge - 2533
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
************************************************************
* 11. IDENTIFYING THE SOFTWARE VERSION NUMBER
************************************************************
The version of the software included in the distribution
package is specified in the file RELNOTES.HTM.
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
************************************************************
* 12. TROUBLESHOOTING
************************************************************
It is assumed that the system requirements in Section 2
above 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 system lockup, restart the machine
and view 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 re-running the procedures outlined
in Section 3.
If this does not fix problems or further
problems are experienced, reinstall the
operating system.
Issue: After running the setup program and rebooting the
machine, Windows reports that it cannot find one
of the following files:
ESDI_506.pdr
Solution: Click Browse in the dialog box where this problem
occurs, locate the
\System\IOSubsys
directory and click OK. The system should
be able to locate this file in this directory
and continue re-enumerating for the new devices.
Issue: After running the setup program and rebooting the
machine, Windows reports that it cannot find one
of the following files:
UHCD.SYS
USBD.SYS
USBHUB.SYS
Solution: Click Browse in the dialog box where this problem
occurs, locate the
\System32\drivers (for Windows* 98,
Windows* Me)
-or-
\System (for Windows* 95)
directory, and click OK. The system should
be able to locate this file in this directory
and continue re-enumerating for the new devices.
Issue: During setup, installation stops and prompts for one
of the following files:
UHCD.SYS
USBD.SYS
USBHUB.SYS
Solution: Ensure that the Windows* 95 USB Supplement has been
installed prior to running the Intel(R) Chipset Software
Installation Utility setup program.
Issue: After running the setup program and rebooting the
machine, Windows reports that it cannot find the
following file:
isapnp.vxd
Solution: Click Browse in the dialog box where this problem
occurs, locate the
\System
directory, and click OK. The system should
be able to locate this file in this directory
and continue re-enumerating for the new devices.
Issue: After performing the silent install, the
HKLM\Software\Intel\InfInst key was not created
or the data of the value "install" is not
"success".
Solution: This is caused by one of the following scenarios:
- The current system does not contain
a supported operating system, or
- The current system does not contain
a supported chipset.
Verify the System Requirements in Section 2.
************************************************************
* 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 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.
************************************************************
************************************************************
* Third-party brands and names are the property of their
respective owners.
Copyright (c) Intel Corporation, 1997-2001