MSFN Forum: How to slipstream Intel INF updates - MSFN Forum

Jump to content



  • 6 Pages +
  • 1
  • 2
  • 3
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

How to slipstream Intel INF updates A guide - what do they really do? Rate Topic: -----

#1 User is offline   raskren 

  • I ♥ Longhorn
  • PipPipPip
  • Group: Members
  • Posts: 383
  • Joined: 11-September 03

Posted 19 January 2004 - 02:46 PM

I've seen some controversey here regarding the Intel INF "drivers" and their purpose under Windows. Let's start by examining how Windows installs drivers. Each and every device in your computer has its own PCI device Id. Let me clarify that: not every device does. Things like ram, hard drives, USB ports don't need drivers. Now let me clarify my clarification; The hard drive doesn't need drivers, the hard drive controller does...the USB ports themselves don't need drivers, the USB controller does. Each controller, slot, and card will have its own id. Windows polls all device ids during setup and determines what driver(s) match each device Id.

The reason Intel provides us with these INF updates is new Intel motherboards and chipsets contain device ids that are not recognized by Windows. For example, I have an i875P motherboard and during a normal Windows install my USB and AGP ports are not installed properly. They are detected but have a yellow exclamation next to them in the device manager - their device Ids were born after Windows Xp had already been finished. Adding the INF updates simply tells Windows which driver to use for these new devices.

That was the quick and dirty reason behind the INFs, now here is how to add them to your Windows CD.

I. Obtain drivers

http://downloadfinder.intel.com/scripts-df...43&DwnldID=6934
That's easy enough. Note that this what was recommended by Intel for an 875P chipset, but it also supports i810 through i875 and a few Centrino models. If you have a chipset older than 810 use the download finder to get the files your chipset.

II. Extract contents

You should now have a file named infinst_enu.exe or infinst_enu.zip. To get the drivers we need we will have to extract files from the archive in two phases. This process is the same using both the self-extracting and zip archives. First extract the contents using WinRar or WinZip to a temporary directory. Now we need to run setup.exe from the command line with a few extra switches. Open up a command prompt window and navigate to the extracted archive. Then run the following command:
setup.exe -A -S -P c:\intel

The -A switch tells setup.exe that we want to extract contents, -S does a "silent" extraction and -P c:\intel tells setup where to put the extracted files. "c:\intel" can be any location on any drive and you can also use the typical %systemdrive% and %systemroot% variables in place of c:\.

III. Organizing files
Now navigate to c:\intel. You'll see 8 folders, each corresponding to its own southbridge (ICH-ICH5). Each folder contains INF and CAT files for different versions of Windows. For this guide we'll focus on the Windows XP drivers but this is the same for Windows 2000. We'll also be copying ALL of the INF and CAT files for Windows XP. The files are small enough that space really isn't a concern and copying all the files allows your CD to work with many different Intel based boards.
Create a new folder within the c:\intel folder named "Intel_inf." Now, starting with the "ich2\xp" folder, copy all the CAT and INF files to "Intel_inf." Work your way through the ICH folders...ICH2...ICH3...and so on overwriting existing files where necessary. Note that "ICH" doesn't contain an Xp folder. This way we get the newest INFs for each chipset and we won't miss any files for older boards. See the attached image for the files you should have in the Intel_inf folder. I have 69 files totaling a whopping 350KB. You can safely delete INFAnswr.txt from this folder.

IV. Add files to the CD
Here is the easy part. Copy all files from Intel_inf to the PnPDriversPath located in Winnt.sif
[Unattended]
UnattendMode=Fullunattend
UnattendSwitch=Yes
OemPreinstall=Yes
ConfirmHardware=No
OverwriteOemFilesOnupgrade=No
OemSkipEula=Yes
TargetPath=WINDOWS
;Filesystem=ConvertNTFS
DriverSigningPolicy=Ignore
OemPnPDriversPath="DRIVERS\INTELINF"
CrushDumpSetting=1

If your Winnt.sif file looks like the one above then put the CAT and INF files in "c:\XPCD\$OEM$\$1\Drivers\INTELINF"

Normally, that would be it but there is one more thing we need to do. The INF files only need to be copied to the Windows\INF folder during installation. To accomplish this simply copy only the INF files from Intel_INF to c:\XPCD\$OEM$\$$\INF.

Now burn it and you're done!

Attached File(s)

  • Attached File  inf.gif (35.13K)
    Number of downloads: 3415



#2 User is offline   Shark007 

  • Repackaging Specialist
  • PipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 3,154
  • Joined: 07-January 04

Posted 19 January 2004 - 05:05 PM

thanks raskren

works for me - intel 865 chipset here.


Shark007

#3 User is offline   enuffsaid 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 862
  • Joined: 26-December 03

Posted 19 January 2004 - 05:12 PM

Thanks Raskren,

for another fine tutorial. Will try this and let you know.

Kind regards,
enuffsaid

#4 User is offline   TheWave 

  • Newbie
  • Group: Members
  • Posts: 32
  • Joined: 13-January 04

Posted 19 January 2004 - 05:18 PM

Can something go wrong i i use it on non intel chipset motherboard?

#5 User is offline   raskren 

  • I ♥ Longhorn
  • PipPipPip
  • Group: Members
  • Posts: 383
  • Joined: 11-September 03

Posted 19 January 2004 - 05:58 PM

Not likely. If the INF files contain a device ID that isn't present on the system, the driver gets ignored.

#6 User is offline   RyanVM 

  • Like a big surly teddy bear.
  • PipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 2,661
  • Joined: 31-August 03

Posted 20 January 2004 - 01:03 AM

Why do they need to be copied into the INF folder? Aren't INFs used during driver installation copied automatically to that folder? It seems to me that putting the reference in winnt.sif is all that's necessary.

#7 User is offline   RyanVM 

  • Like a big surly teddy bear.
  • PipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 2,661
  • Joined: 31-August 03

Posted 20 January 2004 - 01:21 AM

Just for you guys, I created a RAR archive of all the WinXP INFs. You can download it here:
gone

I'll leave it up for a week or so.

#8 User is offline   XtremeMaC 

  • MSFN SuperB
  • PipPipPipPipPipPipPipPipPipPip
  • Group: Members
  • Posts: 5,070
  • Joined: 13-October 03

Posted 20 January 2004 - 01:57 AM

if the demand is high I can host it..

#9 User is offline   enuffsaid 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 862
  • Joined: 26-December 03

Posted 21 January 2004 - 05:13 PM

Hi Raskren,

Finally had time to try this. Unfortunately its not working for me, and frankly I don't think it will work at all.

I know the drivers don't get installed with my unattended installtion because if I check ATI SmartGART, the AGP slider and Fast Write are greyed out. Also if I run infinst.exe after the installation is done, new hardware is detected. And after a reboot I now CAN turn Fast Write on or off and the AGP slider is now available.

I think the problem is that although Windows does see the chipset, I think it sees them as a regular chipset and doesn't install the advanced features of the chipset. For example. If you would do a clean install and at first logon you would go to Device Manager and find new hardware, it wouldn't detect your chipset. But if you would install infinst.exe it WILL detect new hardware.

Now I'm not a techy and I may be technically incorrect, but I think you get my point.

Can you, Raskren, confirm the above is not true for you. With other words, after your unattended install is done you:

- CAN select Fast Write and the AGP slider in SmartGART (if you had a Radeon video card)

- if you were to run infinst.exe anyway, NO new hardware is detected.

I won't post my WINNT.SIF or stuff. I double checked all the steps, did them all correct. No typos or anything. I have done this before in fact, but I only used the IC4 inf files as those are the ones my board needs. It didn't work then, and I was hoping using ALL inf's as you do might do the trick for me.

Frankly I hope your method works. I have two barriers to take ATI control panel and Intel Chipset which are not working for me (auto detect and install). Could you please confirm what I've asked above?

Thanks,
eNuffSaid

#10 User is offline   Kagato 

  • Newbie
  • Group: Members
  • Posts: 13
  • Joined: 08-November 03

Posted 21 January 2004 - 05:47 PM

I'd been trying to find an easier way of installing these vs POST install. Thanks for the info, appears to have worked for me as when I run the install after a re-image, no new hardware is found on reboot. Was a good tryout to make sure I got the new Catalyst 4.10's installed as well - everything seems good - now I just need to start work in reducing the install size. :)

#11 User is offline   enuffsaid 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 862
  • Joined: 26-December 03

Posted 21 January 2004 - 06:07 PM

@ Raskren
Another thing,

In your documentation you extract the drivers to INTEL_INF. But in your:

"OemPnPDriversPath=" you have "DRIVERS\INTELINF" without an underscore. I take it this is a typo?

I also assume the folder name doesn't have to be INTEL_INT (or INTELINF) as long as the correct name is reflected it the OemPnPDriversPath, right?

@ Kagato:

What Mobo do you have? Which chipset is on it? Can you set Fast Write on right after your unattended install?

Thanks,
eNuffsaid

#12 User is offline   raskren 

  • I ♥ Longhorn
  • PipPipPip
  • Group: Members
  • Posts: 383
  • Joined: 11-September 03

Posted 21 January 2004 - 06:48 PM

Dear enuffsaid,

As a matter of fact, I have a Radeon 9600 Pro. I'm also using an Abit IC7-Max3 motherboard which has the Intel 875P chipset (ICH5R southbridge). So far I haven't integrated the Catalyst drivers into my unattended install but I will say that just like you, I also get problems with Fast Writes and AGP bus speed if the INF updates aren't done before the Catalyst drivers. Typically, I'll just run the Catalyst install utility after an unattended Windows install and I've never had a problem. The only thing my pea brain can think of either your drivers are being installed in the wrong order (not likely because SmartGart can't be installed from [OEMPnpDriversPath]) or the ICH4 folder doesn't have all the files necessary for a proper install. Like I said in the guide, I highly recommend that you add all the driver files.

Quote

@ Raskren
Another thing,

In your documentation you extract the drivers to INTEL_INF. But in your:

"OemPnPDriversPath=" you have "DRIVERS\INTELINF" without an underscore. I take it this is a typo?

I also assume the folder name doesn't have to be INTEL_INT (or INTELINF) as long as the correct name is reflected it the OemPnPDriversPath, right?


No, its not a typo. INTEL_INF and INTELINF refer to two separate folders. In the guide INTEL_INF sits within the Intel folder and contains a copy of each unique CAT and INF file. INTELINF was simply used as an example folder for a directory in [OEMPnpDriversPath] but, like you said, this can be anything you want i.e., "001_INF" or "Chipset", etc.

p.s. What is your chipset?

#13 User is offline   enuffsaid 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 862
  • Joined: 26-December 03

Posted 22 January 2004 - 09:30 AM

Hello Raskren,

Thanks for your reply and time!

My Catalyst Drives & WDM are detected automatically and are installed correctly. Like you said it is only the Control Panel (and therefore SmartGART) which are not installed.

I guess I must be doing something wrong then. I have used ALL inf files as you described in your fine tutorial. I guess I must double check.

I have an Asus P4G8X Deluxe with an Intel 7205 chipset.

Again, thanks for your time.

With kind regards,
eNuffSaid

#14 User is offline   Kagato 

  • Newbie
  • Group: Members
  • Posts: 13
  • Joined: 08-November 03

Posted 23 January 2004 - 08:33 AM

My setup is nearly identical to raskren's - no wonder it works for me :) I've got an Abit IC7-G Max II and ATI 9600XT. As far as getting the ATI drivers and Control Panel working with SmartGart during the Unattended install vs POST install, you just have to build your own custom ISS file for the install.

#15 User is offline   enuffsaid 

  • Friend of MSFN
  • PipPipPipPipPip
  • Group: Members
  • Posts: 862
  • Joined: 26-December 03

Posted 23 January 2004 - 09:35 AM

Did that. However, that method will NOT install SmartGart.

#16 User is offline   kenedy 

  • Member
  • PipPip
  • Group: Members
  • Posts: 123
  • Joined: 12-February 04

Posted 12 May 2004 - 12:50 AM

After using that method Intel CD shows that Inf update is not installed.
Is it expected or I just messed up something?

#17 User is offline   raskren 

  • I ♥ Longhorn
  • PipPipPip
  • Group: Members
  • Posts: 383
  • Joined: 11-September 03

Posted 12 May 2004 - 09:51 AM

Definitely not expected. Does device manager show an yellow exclamation? It could be that whatever program you're using for detection doesn't see the updates simply because you didn't run the normal EXE file.

#18 User is offline   GEnto 

  • Newbie
  • Group: Members
  • Posts: 33
  • Joined: 16-May 04

Posted 18 May 2004 - 10:54 AM

Hi great job !!!

Adding intel files, my windows instalation stops at minute 35

Is possible to check what is windows doing while the instalation is running.

(sorry for my bad english my native is spanish)

#19 User is offline   raskren 

  • I ♥ Longhorn
  • PipPipPip
  • Group: Members
  • Posts: 383
  • Joined: 11-September 03

Posted 21 May 2004 - 03:11 PM

Easy way to check...comment out the Intel driver path and try again.

#20 User is offline   No_Style 

  • Newbie
  • Group: Members
  • Posts: 20
  • Joined: 18-December 03

Posted 02 June 2004 - 09:17 AM

Great guide. I followed your instructions to the letter. I've been wondering how to do this for awhile by reading the readme.txt which comes with the Intel drivers and they forgot or assume the user knows the command to get the inf files extracted. :)

Thanks!

Share this topic:


  • 6 Pages +
  • 1
  • 2
  • 3
  • Last »
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users



All trademarks mentioned on this page are the property of their respective owners
Copyright © 2001 - 2011 msfn.org
Privacy Policy