Professional Documents
Culture Documents
Windows
Windows
Windows
Windows
Windows
Windows
Windows
Windows
Windows
Windows
Windows
Windows
7
7 x64
Server 2008 R2 x64
8
8 x64
Server 2012 x64
8.1
8.1 x64
Server 2012 R2 x64
10 (Refer Release Notes for details.)
10 x64
Server 2016 x64
Click on Start.
Select Settings.
Select Control Panel.
Double-click on the System icon.
Click on the General system properties tab.
Verify which OS has been installed by reading
the System information.
-orChipset_<version>_MUP.zip
-orChipset_<version>_BKC.zip
-orChipset_<version>_<configuration>_MUP.zip
-orChipset_<version>_<configuration>_BKC.zip
The <version> string could be similar to "10.0.0", and
the <configuration> string could be similar to "Pre-Alpha",
"Alpha", "Beta, "Public", or "NDA".
************************************************************
* 3A. PUBLIC AND NDA CONFIGURATIONS
************************************************************
The Intel(R) Chipset Device Software supports two types of
configurations, "Public" and "NDA". The Public configuration
has all Intel Confidential (IC) information, such as platform
codenames, stripped out of the build. The NDA configuration
includes this information, as well as extra installation
functionality that is not safe enough to be released
publicly, but is required for validation efforts. For this
reason, NDA-configured releases are not permitted to be
released publicly or to anyone not possessing a Non-Dislosure
Agreement (NDA) with Intel Corporation.
To help identify whether a given build configured with NDA
functionality, a large red banner has been added to the user
interface of the installer, stating that it is an NDA build.
The Public and NDA configurations are only available for
production releases, "Production Candidate" (PC) and
"Production Version" (PV). For non-production releases
Pre-Alpha, Alpha, and Beta, it is assumed that the build
will not be released publicly. Therefore, non-production
releases only have one configuration, the NDA configuration.
The Intel(R) Chipset Device Software does not support
installation of both build configurations on a single
machine, this will result in an error thrown by the
Microsoft Windows* Installer framework during the second
installation, manifesting as an error message in the log
files and on the installer user interface when running in
Interactive mode. The installer will exit with code 666.
************************************************************
* 4. LIST OF AVAILABLE COMMAND LINE FLAG OPTIONS
************************************************************
The Intel(R) Chipset Device Software supports several
command line switches for various installation options.
Below is a list of all the available command line switches that
may be used with the program call.
Switch
----?
Description
----------Displays the the help dialog
-downgrade
-lang <lcid>
-norestart
-overall
-p <path>
-q
-quiet
-s
-silent
Below are the language codes used with the '-lang' switch:
LCID
-------0401
0804
0404
0405
0406
0413
0409
040B
040C
0407
0408
040D
040E
0410
0411
0412
0414
0415
041B
0416
0816
0419
040A
041D
041E
041F
Language
-----------------------Arabic (International)
Chinese (Simplified)
Chinese (Traditional)
Czech
Danish
Dutch
English (United States)
Finnish
French (International)
German
Greek
Hebrew
Hungarian
Italian
Japanese
Korean
Norwegian
Polish
Slovak
Portuguese (Brazil)
Portuguese (Standard)
Russian
Spanish (International)
Swedish
Thai
Turkish
************************************************************
* 5. INSTALLING THE SOFTWARE IN INTERACTIVE MODE
************************************************************
ml.
6. Create a Configuration Set
(In this step, you create a configuration set that will gather all of the resour
ce files
that you specified in your answer file into one location.)
A. In Windows SIM, on the Tools menu, select Create Configuration Set.
B. The Create Configuration Set window opens.
C. Specify a destination location where you intend to publish the config
uration set
D. Select a removable drive such as a USB flash drive (UFD), and then cl
ick OK.
7. Deploying a Configuration Set Without a Network
A. Turn on the new computer.
B. Insert both the removable media containing your configuration set and
the
supported Windows OS product DVD into the new computer.
Note: When using a USB flash drive, insert the drive directly in
to the
primary set of USB ports for the computer. For a desktop c
omputer,
this is typically in the back of the computer.
C. Restart the computer by pressing CTRL+ALT+DEL.
Note: This example assumes that the hard drive is blank.
D. Windows Setup (Setup.exe) begins automatically.
E. By default, Windows Setup searches all removable media for an answer
file
called Autounattend.xml. Autounattend.xml must be located at the root
of the
removable media.
F. After Setup completes, validate that all customizations were applied,
and then
reseal the computer by using the generalize option
For more information about supported Windows OS answer
files and unattended installations, please refer to the
Windows Automated Installation Kit (WAIK) User's Guide.
************************************************************
* 8. INSTALLING THE INF FILES AFTER OS INSTALLATION
************************************************************
By [supported Windows OS] it is meant a Windows operating system
that is listed in section 2.
Some Intel(R) chipset platforms already are supported by
supported Windows OS so it may not be necessary to use the
INF files provided by this software to update the supported
Windows OS.
The following steps describe the installation process of
the supported Windows OS INF files. You may need to repeat these
steps to update all Intel(R) chipset devices not supported
by supported Windows OS.
1. Copy the contents of the <INF Extract Directory>
to the root directory of a removable media, such as
a USB flash drive (UFD) or floppy disk (A:\).
2. Close all programs currently running on the system.
3. Click on Start.
4. Select Settings.
5.
6.
7.
8.
9.
10.
Solution:
Solution:
Issue:
Solution:
Issue:
Solution:
Issue:
Solution: