Hi,
is there a way to install the Intel Chipset Software Installation Utility while installing Windows ?
I know that you can extract the .cat & .inf files fom the compressed .EXE file by running the file with the switches: -a -a -p <path>. But then,is there a way to add them as drivers ? Maybe with Nlite ?
Full Version: Unattended Intel Chipset Software Installation Utility?
Use PowerArchiver to extract files (or winrar) and copy all to %cdrom%\$OEM$\$1\Drivers\001_INF and to %cdrom%\$OEM$\$$\inf 
using winnt.sif method is the bes i found for intel inf drivers. just do as mercury says. you can download the zipped files (not the installer) from intel. extract them to $OEM$\$1\Drivers\00_inf or whatever folder you want, preferably first folder as intel says is better to install first inf then all other drivers.
then just use OemPnpDriversPath = "Drivers\00_inf" in you winnt.sif file.
there is no need to extract them to $$\inf
i just use them in drivers\00_inf and is working well.
then just use OemPnpDriversPath = "Drivers\00_inf" in you winnt.sif file.
there is no need to extract them to $$\inf
i just use them in drivers\00_inf and is working well.
ok,thanks for the infos. Just wondering,does anyone know if the integration via Nlite works ?
I just chose any inf from those available and they install the chipset drivers just fine...i remember in 0.99 beta they didn't work, but they've been working now for quite some time
QUOTE (elajua @ Feb 22 2006, 09:16 PM) 
there is no need to extract them to $$\inf
i just use them in drivers\00_inf and is working well.
i just use them in drivers\00_inf and is working well.
Did you check your drivers after install?
INTEL says to copy them to $$\inf too Without this for me it doesn't work 
QUOTE (Mercury_22 @ Feb 23 2006, 07:29 AM)
QUOTE (elajua @ Feb 22 2006, 09:16 PM)
there is no need to extract them to $$\inf
i just use them in drivers\00_inf and is working well.
Did you check your drivers after install?
INTEL says to copy them to $$\inf too Without this for me it doesn't work i have double-checked them. they are installed right in my comp. are you using the files that are inside the zip or extract them via installer with switches? i have them right in just drivers\00_inf (using the one inside the zip release for developer at intel's.
i have 915p chipset and is all installed. i think windows copy them to system32\inf when it installs them from drivers\00_inf. almost sure...
You can also use silent post-install, I use that method and works great !
Intel INF
-------------
1) Download last version from Intel.com
2) Extract files into a new folder
3) Repackage all in the new folder into a auto extractible archive (like winrar) and set run after uncompression : "setup.exe -OVERALL -S"
Intel INF
-------------
1) Download last version from Intel.com
2) Extract files into a new folder
3) Repackage all in the new folder into a auto extractible archive (like winrar) and set run after uncompression : "setup.exe -OVERALL -S"
QUOTE (Sonic @ Feb 24 2006, 05:32 AM)
You can also use silent post-install, I use that method and works great !
Intel INF
-------------
1) Download last version from Intel.com
2) Extract files into a new folder
3) Repackage all in the new folder into a auto extractible archive (like winrar) and set run after uncompression : "setup.exe -OVERALL -S"
Intel INF
-------------
1) Download last version from Intel.com
2) Extract files into a new folder
3) Repackage all in the new folder into a auto extractible archive (like winrar) and set run after uncompression : "setup.exe -OVERALL -S"
My Drivers are installing perfect the way I posted above But i remeber one time i've copy them only to $OEM$\$1\Drivers\001_INF and NOT ALL get instaled!
And here is INTEL's INSTALLING METHOD FROM INTEL'S reademe.txt
CODE
************************************************************
* 8B. INSTALLING THE WINDOWS* XP INF FILES PRIOR TO
* OS INSTALLATION
************************************************************
NOTE: The Windows* XP OEM Preload Kit distribution CD contains
a setup directory with all the base operating system
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
<WINXP Setup Directory>:
\$OEM$\$$\INF
2. Copy the Windows* XP INF files from
<INF Extract Directory>\XP to the directory
created in Step 1 above:
<WINXP Setup Directory>\$OEM$\$$\INF
3. Create the following directory structure under the
<WINXP Setup Directory>:
\$OEM$\$1\drivers\IntelINF
4. Copy the Windows* XP INF files AND the catalog files
(.CAT) from <INF Extract Directory>\XP to the
directory created in Step 3 above:
<WINXP Setup Directory>\$OEM$\$1\drivers\IntelINF
5. Either modify the default Windows* XP installation
answer file, UNATTEND.TXT, located in <WINXP 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) Chipset
Software Installation utility files is available:
<INF Extract Directory>\XP\INFAnswr.TXT
If you are a computer manufacturer, refer to the Microsoft*
Windows* XP Guide to Unattended Setup for more information
about Windows* XP answer files and unattended installations.
For more information about the \$OEM$ folder, refer to the
Microsoft Windows* XP OEM Preinstallation Kit (OPK)
User Guide. If you are not a manufacturer, refer to the Microsoft
Windows* XP Deployment Guide.
6. Run "WINNT.EXE /u:<answer file name> /s:<WINXP Setup
Directory>" to install Windows* XP.
* 8B. INSTALLING THE WINDOWS* XP INF FILES PRIOR TO
* OS INSTALLATION
************************************************************
NOTE: The Windows* XP OEM Preload Kit distribution CD contains
a setup directory with all the base operating system
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
<WINXP Setup Directory>:
\$OEM$\$$\INF
2. Copy the Windows* XP INF files from
<INF Extract Directory>\XP to the directory
created in Step 1 above:
<WINXP Setup Directory>\$OEM$\$$\INF
3. Create the following directory structure under the
<WINXP Setup Directory>:
\$OEM$\$1\drivers\IntelINF
4. Copy the Windows* XP INF files AND the catalog files
(.CAT) from <INF Extract Directory>\XP to the
directory created in Step 3 above:
<WINXP Setup Directory>\$OEM$\$1\drivers\IntelINF
5. Either modify the default Windows* XP installation
answer file, UNATTEND.TXT, located in <WINXP 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) Chipset
Software Installation utility files is available:
<INF Extract Directory>\XP\INFAnswr.TXT
If you are a computer manufacturer, refer to the Microsoft*
Windows* XP Guide to Unattended Setup for more information
about Windows* XP answer files and unattended installations.
For more information about the \$OEM$ folder, refer to the
Microsoft Windows* XP OEM Preinstallation Kit (OPK)
User Guide. If you are not a manufacturer, refer to the Microsoft
Windows* XP Deployment Guide.
6. Run "WINNT.EXE /u:<answer file name> /s:<WINXP Setup
Directory>" to install Windows* XP.
So...
Also from readme.txt "10. Verifying Installation of the Software and
Identifying the Software Version Number"
CODE
************************************************************
* 10. IDENTIFYING THE SOFTWARE VERSION NUMBER
************************************************************
The version numbers displayed by Device Manager for a given
device may not be the same as the Intel(R) Chipset Software
Installation Utility version.
The correct version number is shown at the top of this file.
* 10. IDENTIFYING THE SOFTWARE VERSION NUMBER
************************************************************
The version numbers displayed by Device Manager for a given
device may not be the same as the Intel(R) Chipset Software
Installation Utility version.
The correct version number is shown at the top of this file.
But if with your methods the drivers are installing ok then everything it's OK
i check the version numbers when i install my drivers.
Just copying them to Drivers/000_inf and using winnnt.sif works fine for me as posted earlier.
Just copying them to Drivers/000_inf and using winnnt.sif works fine for me as posted earlier.
Exactly what files should be copied?
I take it it's the content of the "XP" folder, but the XP folder has a subfolder called SP, there are .inf and .cat files in both XP and XP\SP.
I take it it's the content of the "XP" folder, but the XP folder has a subfolder called SP, there are .inf and .cat files in both XP and XP\SP.
QUOTE (BoardBabe @ Feb 27 2006, 09:02 AM)
Exactly what files should be copied?
I take it it's the content of the "XP" folder, but the XP folder has a subfolder called SP, there are .inf and .cat files in both XP and XP\SP.
I take it it's the content of the "XP" folder, but the XP folder has a subfolder called SP, there are .inf and .cat files in both XP and XP\SP.
Both XP and XP\SP
It's a safe mothod!
Ok. Thanks, ill try this method.
I've previously installed from .exe at cmdlines.txt.
I'll just rename the XP dir to 001_chipset and try that way
I've previously installed from .exe at cmdlines.txt.
I'll just rename the XP dir to 001_chipset and try that way
Don't forget to change the winnt.sif
Thanks, it's updated
QUOTE (BoardBabe @ Feb 27 2006, 04:05 PM)
Thanks, it's updated
you're safe now
remember to get the new releases in zip archive since its always easy to just extract them into your drivers folder instead of using switches to get the inf files in the exe release.
I just extracted the .exe using WinRAR
QUOTE
I just extracted the .exe using WinRAR
i said to get the developer release (in zip format) because i came into problems one time when using files extracted from the normal release.
also one time (for 845 chipset) i saw different filesizes on the files from exe and zip releases. so i just thougt to be safer is you use zip files instead.
just a suggestion.
glad you all (the ones with questions) now have them installed properly.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.