Integration of Intels AHCI/RAID drivers into a Windows XP

Hi,
I have just joined this forum in the hope of help. During the past few weeks I have tried a lot to install WinXP Pro 32-bit on my second hand Elitebook by means of the F6-method, but all in vain, unfortunately. Therefore, I would like to take advantage of this guide now. I know, I am a little bit clumsy and it will take a long way to reach this target.

My hard and software is as follows:

HP 2530p, HD: 1,8" SATA Toshiba 120 GB SSD,
Proc.: Intel LV Core 2 Duo SL 9400,
Chipset: Mobile Intel Express GS45
ICH9m-SFF-enhanced,
CD WinXP Pro SP3 (c) 2009 HP

Since in the past I haven’t found any driver, never at HP, Intel or anywhere in the www that matched the chipset: “ Intel ..... ICH9m-SFF-enhanced” exactly, I would like to know, before shouldering the burden, whether your tool

32bit Intel RST AHCI & RAID …0.1006 WHQL.7

is supposed to do this job successfully.

Please note that there is no possibility to make any changes in the BIOS from HP, Version 68PSU Ver: F.12, Date 05/28/2010.

I have already installed Suse Linux successfully. However, since I would like to use some old programs in WinXP too, I would like to install also this OS. As you are aware, Windows must be installed first. I do hope I will be able to bridge the gap with your generous help.

Your reply will oblige.

Happy Easter!

Zitat von Fernando im Beitrag #221

---

The device with the DeviceID DEV_8CA2 is the Intel 9-Series SMBus Controller and has nothing to do with the Intel 9-Series Chipset SATA AHCI/RAID Controller of your Z97 mainboard. The suitable information file for this device is named Chipset_SMBus.inf and part of the Intel Chipset Device Software v10.0.xx. Since I found this INF file within the Windows\INF directory of my Z97 system, I have attached it.

---

I open Device Manager and right-click on the “PCI Device” with the yellow questions mark; then click Driver/Update Driver/Search for a suitable Driver; then check “Specify Location” and “Microsoft Update” and browse to chipset_smbus.inf. The return is “Windows was unable to locate a driver for this device.” (This is the method that worked on Windows XP).

When I use the “Have Disk” method and locate the chipset_smbus.inf file the message returns, “The specified location does not contain information about your hardware.”

(Having determined “PCI Device” is actually the SMBus Controller by opening Computer Management/System Information/Components/Problem Devices and hovering over “PCI Device” and seeing “PCI\VEN_8086&DEV_8CA2 & SUBSYS…” which is the same information Windows XP gives for its problem device “SMBus Controller.”)

Yes, I have clicked on the INF file before receiving the response, "The specified location does not contain information about your hardware.”

W2k Pro does not really have a Details tab like Windows XP; hopefully this will suffice (curiously, the W2k error code has “evolved” from “28” to “1”):

I have attached the W2k screenshot from Device Manager/PCI Device/Properties.

Also, I uninstalled the “Intel Device” (formerly SMBus Controller) in Windows XP Device Manager, in hopes that I could show you that problem device ID in XP; however, on reboot XP apparently reinstalled the SMBus Controller (as “Intel Device”) on its own. I attach the screenshot here anyway, just for the information.

EDIT: Perhaps I should re-install Windows XP (it is not as much trouble as it seems), so that I may show "SMBus Controller" associates with ID 8CA2.

With the new file I receive the same message as before using the “Have Disk” approach, which I tried on all three yellow question mark entries in W2k Pro Device Manager. I also re-tried the Windows Update/specify location approach with all three problem entries. I also re-booted, and again tried the Have Disk approach, which again did not de-list the problem device.

To be sure I’m doing this right, could you please confirm: when I use the Upgrade Device Driver Wizard, and check “Display a list of known devices…” I am presented with “Select a hardware type”; am I correct that it does not matter which “hardware type” I select before clicking “Next” and “Have Disk” and double-clicking to select the newly extracted Chipset_SMBus.inf (I did try various entries there).

EDIT: And for the sake of certainty, I also deleted all Chipset_SMBus files from my W2k Pro machine, and re-downloaded your attachment in post # 311 on to a different USB stick, which I walked from my internet computer to the W2k machine, where I extracted it into a newly-made folder before trying again.

Oh, so close…

The latest “driver” did not de-list the PCI Device (SMBus) Problem Device in Device Manager using the “Have Disk” method, but it worked using Windows Update / Specify Location! or so I thought at first (see attachment “1st” ).

I then noticed the Problem Device had been shifted down to the system devices (see attachment “2nd and 4th”).

I disabled the PCI Device there (see attachment “3rd”) and re-booted; when the desktop loaded, a window opened that I had not seen before ( see attachment “Between 3rd and 4th”), where Windows now correctly names the device it’s trying to install

And then we were returned to the same situation as attachment “2nd” (see attachment “2nd and 4th”).

This is of course a custom W2k Pro OS, Fernando, as it must be in order to be able to install whatsoever on a hardware platform as new as the Z97. I have another variant of this OS which is slightly more conventional, and which I actually prefer; I will test when I re-install it (hopefully this evening) (I only have two practice HDDs to swap back and forth, one I’ve used here for XP and one for W2k Pro, so I can’t just plug in the more conventional W2k Pro version, or I would try it right now).

Thank you for your great efforts here.