Your quote, "You can manually install the drivers from Intel after extracting them from the installer executable or package" eludes me. Can you be more specific? Which, "installer executable or package?" If you can help me circumvent the Server OS on a PC blockage it would be IMMENSLY helpful not only to me but to others. Thank you.
Intel often provides its drivers in both .exe and .zip package, but sometimes a driver (or some particular version of it) is only offered in .exe package. While its a bit easier (a few less steps) when Intel provides the .zip package, its not a problem for those cases where they don't because the .exe can be opened and/or the files extracted just as though it were a .zip package using a
utility like 7-Zip that can handle executable installer packages.
It looks like all current/latest drivers for H67 are available in .zip package, except for the post-install Intel Rapid Storage driver (RAID and AHCI):
INF Installation (Chipset Device Software) Utility (all current Windows OS)
Intel HD Graphics Driver (32-bit Vista/7)
Intel HD Graphics Driver (64-bit Vista/7)
The gist of things is to extract the .INF and attendant driver files to some directory of your choosing (e.g. C:\Drivers\Intel), but preserve any sub-directory structure for individual/separate drivers. A good generic overview or guide on how to manually update the drivers for a device using the 'unpacked' INF and driver files can be seen here:
http://www.intel.com/support/chipsets/inf/sb/cs-009272.htm
Just use the instructions under Windows Vista or XP/2003 as a general guide to the process. You should be able to adapt the guide to Windows 7 or Server 2008 and figure the rest out, although the exact dialogue screens may be slightly different depending on the OS. Its pretty much the same dealio no matter which device type you need drivers for. e.g. chipset or core logic, storage controller, NIC, display drivers, et. al.
Typically, when using this 'update driver' method, it is best to use 'Let windows automatically locate the best driver' when its offered as an option (select the option to include sub-folders in the search), while also directing the Driver Wizard to the particular root folder where the driver files are located (i.e. narrow the search down a bit instead of permitting Windows to search the entire computer). But there may be times when this won't work and you may need to use the manual "have disk" method. Basically, this is where you opt-out of having Windows automatically locate the best driver and must point Windows to a particular INF file and manually select the correct device from a list of available choices. But this will be an exceptional case and I won't go into it unless you should have some problem with the more 'automatic' method.
Intel also provides similar instructions in the readme.txt file for most drivers. Here is the readme.txt file for the INF Chipset/Device Software Utility:
Reame.txt for INF Installation files (scroll down to section 9.F and 9.G)
The Rapid Storage Technology drivers for RAID or AHCI mode could be installed during OS setup (by selecting the option to provide third-party drivers) via Floppy or USB flash drive, or after OS installation:
Intel RST Drivers for Floppy or USB Install during OS Setup (32-bit)
Intel RST Drivers for Floppy or USB Install during OS Setup (64-bit)
Intel RST Drivers Post-Install Full Package for RAID or AHCI (all current Windows OS 32-bit and 64-bit)
The Floppy/USB package above could also be used post-setup, by extracting the files and using the same method above to update the storage drivers. Other onboard devices such as secondary (third-party) storage controllers, NIC or WiFi, USB3.0 controllers, and audio controllers are all manufacturing options that are going to vary with the make/model of motherboard - not too much to do with the chipset itself. There are too many such third-party device options to go into here so if you could provide the make/model motherboard, I could find out what those devices are.
Facebook
Twitter