ggg Posted February 22, 2006 Share Posted February 22, 2006 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 ? Link to comment Share on other sites More sharing options...
Mercury_22 Posted February 22, 2006 Share Posted February 22, 2006 Use PowerArchiver to extract files (or winrar) and copy all to %cdrom%\$OEM$\$1\Drivers\001_INF and to %cdrom%\$OEM$\$$\inf Link to comment Share on other sites More sharing options...
ajua Posted February 23, 2006 Share Posted February 23, 2006 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 $$\infi just use them in drivers\00_inf and is working well. Link to comment Share on other sites More sharing options...
ggg Posted February 23, 2006 Author Share Posted February 23, 2006 ok,thanks for the infos. Just wondering,does anyone know if the integration via Nlite works ? Link to comment Share on other sites More sharing options...
tap52384 Posted February 23, 2006 Share Posted February 23, 2006 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 Link to comment Share on other sites More sharing options...
Mercury_22 Posted February 23, 2006 Share Posted February 23, 2006 there is no need to extract them to $$\infi 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 Link to comment Share on other sites More sharing options...
ajua Posted February 24, 2006 Share Posted February 24, 2006 there is no need to extract them to $$\infi 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... Link to comment Share on other sites More sharing options...
Sonic Posted February 24, 2006 Share Posted February 24, 2006 You can also use silent post-install, I use that method and works great !Intel INF-------------1) Download last version from Intel.com2) Extract files into a new folder3) Repackage all in the new folder into a auto extractible archive (like winrar) and set run after uncompression : "setup.exe -OVERALL -S" Link to comment Share on other sites More sharing options...
Mercury_22 Posted February 24, 2006 Share Posted February 24, 2006 You can also use silent post-install, I use that method and works great !Intel INF-------------1) Download last version from Intel.com2) Extract files into a new folder3) 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************************************************************* 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$\$$\INF2. Copy the Windows* XP INF files from <INF Extract Directory>\XP to the directory created in Step 1 above: <WINXP Setup Directory>\$OEM$\$$\INF3. Create the following directory structure under the <WINXP Setup Directory>: \$OEM$\$1\drivers\IntelINF4. 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\IntelINF5. 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"************************************************************* 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 Link to comment Share on other sites More sharing options...
ajua Posted February 27, 2006 Share Posted February 27, 2006 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. Link to comment Share on other sites More sharing options...
BoardBabe Posted February 27, 2006 Share Posted February 27, 2006 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. Link to comment Share on other sites More sharing options...
Mercury_22 Posted February 27, 2006 Share Posted February 27, 2006 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. Both XP and XP\SP It's a safe mothod! Link to comment Share on other sites More sharing options...
BoardBabe Posted February 27, 2006 Share Posted February 27, 2006 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 Link to comment Share on other sites More sharing options...
Mercury_22 Posted February 27, 2006 Share Posted February 27, 2006 Don't forget to change the winnt.sif Link to comment Share on other sites More sharing options...
BoardBabe Posted February 27, 2006 Share Posted February 27, 2006 Thanks, it's updated Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now