[nAFutro]

Adding Intel SATA Drivers to an Installation CD

IMPORTANT:
Follow the installation instructions in the order provided. Failure to complete these steps in the proper order can result in an unsuccessful or unstable installation.

This section provides guidelines for people who need to add Intel SATA AHCI of RAID support by creating a custom Windows XP Service Pack 2 Installation CD.
Why did i make this? I wasn't satisfied with the information many other people are writing on the Internet and there guidelines are to complex for beginners, intermediates and even experts to understand if they are unfamiliar with this stuff.

Steps to add SATA drivers to the CD
1) Copy all the directories and files from the Windows XP CD to a temporary folder (these guidelines will use c:\xpcd)
2) Download the Floppy Configuration Utility from Intel.com
3) Extract all the files from the downloaded file. You can use an extraction tool or if you choose just to run the setup installer the files will be located on a floppy. (these guidelines will use the floppy installer)
4) These files should be located on the floppy disk.
a. iaahci.cat
b. iaahci.inf
c. iastor.cat
d. iastor.inf
e. iastor.sys
f. license.txt
g. readme.txt
h. txtsetup.oem
5) Create the following path in the temporary folder: c:\xpcd\$oem$\$1\drivers\sata
6) Copy all the files from step 4 to the c:\xpcd\i386 folder. You could delete the readme.txt and license.txt if you want, they are not important for the installation.
7) Also copy all the files from step 4 to the c:\xpcd\$oem$\$1\drivers\sata folder.
8) Open the c:\xpcd\i386\txtsetup.sif file in Notepad.
9) Go to the end of the file. There will be several blank lines.
10) Move the cursor up a few lines. This is necessary because there is a hidden marker at the end of the file.
11) Add the following lines

[SourceDisksFiles]
iastor.sys= 1,,,,,,4_,4,1,,,1,4
iaAHCI.cat=1,,,,,,,20,0,0
iaAHCI.inf=1,,,,,,,20,0,0
iaSTOR.cat=1,,,,,,,20,0,0
iaSTOR.inf=1,,,,,,,20,0,0
[HardwareIdsDatabase]
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_25B0&CC_0104 = "iaStor"
[SCSI.Load]
iaStor = iaStor.sys,4
[SCSI]
iaStor = "Intel® 82801 SATA RAID/AHCI Controller (ICH5,6,7)"

12) Save the file and exit notepad.
13) Open the c:\xpcd\i386\winnt.sif in notepad
14) Under the section [Unattended], add the following lines:

OemPreinstall=yes
OemPnPDriversPath=drivers\sata
DriverSigningPolicy = Ignore

15) Burn the custom XPCD from the c:\xpcd folder.

[KRYOGENIUS]

Hello

Thanks for the newbies, but a automated tool is be better (nlite or other) than manual modifications.

++

[nAFutro]

KRYOGENIUS, on Jan 15 2007, 05:24 PM, said:

but a automated tool is be better (nlite or other) than manual modifications.
++

As an IT professional I can only say that you shouldn't edit files if there is a similar solution for the problem without editing the files. You will get bitten at a later point.

Of course I've tried nLite but that tool doesn't just add a driver, it completely changes the installation CD and that my friend is a big issue for me. My cooperation has a Microsoft Open License so we get updated Microsoft CD's. One thing is for sure, nLite doesn't generate files that are the same as Microsoft does.

I've got a great ending line for my comment, it is something my teacher said to me in my first years at school and he sure was right.

"Only monkey's use tools, you need to know the material itself"

[neo]

KRYOGENIUS, on Jan 15 2007, 09:54 PM, said:

Hello

Thanks for the newbies, but a automated tool is be better (nlite or other) than manual modifications.

++

Yes, its quite easy to use automated tool

go to http://www.msfn.org/...opic=59556&hl=#

[IcemanND]

Nice tutorial.

Yes, automated tools are nice but when they don't work then what are you going to do if you don't know how to do it the hard way.

[ubernerd]

nAFutro, on Jan 15 2007, 06:01 PM, said:

KRYOGENIUS, on Jan 15 2007, 05:24 PM, said:

but a automated tool is be better (nlite or other) than manual modifications.
++

As an IT professional I can only say that you shouldn't edit files if there is a similar solution for the problem without editing the files. You will get bitten at a later point.

Of course I've tried nLite but that tool doesn't just add a driver, it completely changes the installation CD and that my friend is a big issue for me. My cooperation has a Microsoft Open License so we get updated Microsoft CD's. One thing is for sure, nLite doesn't generate files that are the same as Microsoft does.

I've got a great ending line for my comment, it is something my teacher said to me in my first years at school and he sure was right.

"Only monkey's use tools, you need to know the material itself"

So true so true ... and a very nice tutorial

This post has been edited by ubernerd: 23 January 2007 - 06:02 AM

[bledd]

can anyone host the contents of the exe for me?

i dont have a floppy drive, and neither 7zip or universal extractor can get the files from it

[ubernerd]

WinImage or any other ISO opener tool will most likely work

[nAFutro]

bledd, on Jan 23 2007, 01:53 PM, said:

can anyone host the contents of the exe for me?

There is another way to obtain the files and it will also work in the feature with newer releases of the drivers.

You will need to download the Win32 setup of Intel Matrix Storage driverpackage from Intel.com instead of F6 floppy installer.
After that you can extract the files from the downloaded archive, this can be done by launching the iata.exe file from a prompt or the Windows run with the following parameters:
\iata621_enu.exe" -A -PC:\IATA
This way the files will be extracted to the C:\IATA folder without installing them on your system. the files located in the C:\Extracted\Driver\ folder are the same as the files you will find in the F6 floppy installer.

[Sgt_Strider]

I followed the method that you provided and it doesn't work . The notebook would just crash as it's loading the drivers. I did everything that you said including adding the entries to txtsetup.sif. I don't know if you would call it a marker, but there was an arrow at the end of the page. I went up a few lines and copy and paste what you provided and it doesn't work.

Is it possible that I didn't put the sata drivers as the first entry in the winnt.sif file? For the OEM drivers path, I placed my chipset drivers and several other drivers ahead of the sata drivers.

This post has been edited by Sgt_Strider: 29 January 2007 - 01:41 AM

[nAFutro]

Sgt_Strider, on Jan 29 2007, 08:39 AM, said:

The notebook would just crash as it's loading the drivers.

Hmm that is strange, I will PM you so we can troubleshoot it. Crashing is strange, if something wasn't added right it should just skip the driver i believe.

[Sgt_Strider]

nAFutro, on Jan 29 2007, 11:57 AM, said:

Sgt_Strider, on Jan 29 2007, 08:39 AM, said:

The notebook would just crash as it's loading the drivers.

Hmm that is strange, I will PM you so we can troubleshoot it. Crashing is strange, if something wasn't added right it should just skip the driver i believe.

Check your PM! Thanks.

[Sgt_Strider]

I tried this method again and it just crash and give me the following technical error code:

0x0000007B (0xF7A8A524, 0xC0000034, 0x00000000, 0x00000000)

[Sgt_Strider]

I think I know why it may not work. I checked the readme file from the Gateway driver and apparently this is the SATA chip on my motherboard, - Intel® 82801GH I/O controller Hub (ICH7DH). I don't see that entry in your file. Is that why it's not working?

Here is the link to the driver: http://support.gateway.com/support/drivers...mp;uid=14942519

This post has been edited by Sgt_Strider: 03 February 2007 - 02:42 AM

[chyronn]

nAFutro, on Jan 27 2007, 09:35 PM, said:

bledd, on Jan 23 2007, 01:53 PM, said:

can anyone host the contents of the exe for me?

There is another way to obtain the files and it will also work in the feature with newer releases of the drivers.

You will need to download the Win32 setup of Intel Matrix Storage driverpackage from Intel.com instead of F6 floppy installer.
After that you can extract the files from the downloaded archive, this can be done by launching the iata.exe file from a prompt or the Windows run with the following parameters:
\iata621_enu.exe" -A -PC:\IATA
This way the files will be extracted to the C:\IATA folder without installing them on your system. the files located in the C:\Extracted\Driver\ folder are the same as the files you will find in the F6 floppy installer.

the \iata621_enu.exe" -A -PC:\IATA part doesn't work for me, it asks me for a location where the iata621_enu.exe is then setup.dll

[Sgt_Strider]

I don't know what happened to the OP, but I'm really frustrated by the fact that I can't get this to work. I just bought a USB stick and I should receive it tomorrow.

How do I make my USB stick bootable like a floppy disk? Can I just place these files in the USB stick's main directory and then just press "F6" to load them and install Windows XP?

a. iaahci.cat
b. iaahci.inf
c. iastor.cat
d. iastor.inf
e. iastor.sys
f. license.txt
g. readme.txt
h. txtsetup.oem

[Sgt_Strider]

nAFutro, on Jan 27 2007, 01:35 PM, said:

bledd, on Jan 23 2007, 01:53 PM, said:

can anyone host the contents of the exe for me?

There is another way to obtain the files and it will also work in the feature with newer releases of the drivers.

You will need to download the Win32 setup of Intel Matrix Storage driverpackage from Intel.com instead of F6 floppy installer.
After that you can extract the files from the downloaded archive, this can be done by launching the iata.exe file from a prompt or the Windows run with the following parameters:
\iata621_enu.exe" -A -PC:\IATA
This way the files will be extracted to the C:\IATA folder without installing them on your system. the files located in the C:\Extracted\Driver\ folder are the same as the files you will find in the F6 floppy installer.

The command doesn't work for me too.

[iTwins]

That command-line doesn't work. Try this:

1) Download the F6Flpy32.zip file from Intel website
2) Extract F6FLPY32.ZIP to a temp directory
3) Extract the F6FLPY32.EXE using WinRAR or WinImage (with WinImage, you can skip Step 4)
4) Finally, extract the contents of TEMP.IMA using WinImage or UltraISO

In case you don't have the tools to do that, I've saved you the trouble. You can download v6.2.1.1002 (1/4/2007) from here: F6FLPY32.ZIP

This post has been edited by iTwins: 18 February 2007 - 09:33 PM

[Sgt_Strider]

iTwins, on Feb 18 2007, 07:30 PM, said:

That command-line doesn't work. Try this:

1) Download the F6Flpy32.zip file from Intel website
2) Extract F6FLPY32.ZIP to a temp directory
3) Extract the F6FLPY32.EXE using WinRAR or WinImage (with WinImage, you can skip Step 4)
4) Finally, extract the contents of TEMP.IMA using WinImage or UltraISO

In case you don't have the tools to do that, I've saved you the trouble. You can download v6.2.1.1002 (1/4/2007) from here: F6FLPY32.ZIP

Thanks!

[zetto]

Thanks op! Although a little bit of constructive criticism - I'm sure this method works for you but for others, with other Intel chipsets and drivers this may not be the best way. Also, note that this works for RAID setup just as well for the ACHI setup. In my case, I had raid and modified the hardware ids to match the ones in the driver's txtsetup.oem file (I did keep everything else the same). So, with the latest F6 Intel driver, I have the following:

PCI\VEN_8086&DEV_2822&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2821&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2682&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2681&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_27C3&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C6&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_27C1&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2652&CC_0104 = "iaStor"
PCI\VEN_8086&DEV_2652&CC_0106 = "iaStor"
PCI\VEN_8086&DEV_2653&CC_0106 = "iaStor"

Worked for me, on Asus P5W DH mobo with Intel 975 chipset (ICH7). Might help those, who had errors with the ops suggested setup.

This post has been edited by zetto: 13 March 2007 - 12:52 PM