none
Updated SATA drivers

    Question

  • Will the final release contain the updated intel Sata Drivers  (which most laptops require (press the F6  to install addtional drivers from floppy))   ?

     

     

    Monday, January 21, 2008 1:35 PM

Answers

All replies

  • There isn't a plan to add new SATA drivers to XP SP3.

     

    Tuesday, January 22, 2008 9:38 AM
  •  

    What steps do I need to take to get them added ?  Maybe I should start a petition.  Its a ball ache to add these manually when using microsoft deployment.
    Tuesday, January 22, 2008 10:54 AM
  • Or you can use the alternate way by integrating them in the install disk with nLite Wink

     

    Wednesday, January 23, 2008 6:32 AM
  •  

    Microsoft does not support images that have been created / altered with Nlite.  If Microsoft supported this method then I would use the tool.  Also (Microsofts) Business Desktop Deployment 2007 does not like cd's that have been created/altered with Nlite.

     

     

    Wednesday, January 23, 2008 9:27 AM
  • I have used nlite, but I have not been successful at adding the sata drivers for a laptop install.  Can you give me a link to get the correct drivers for an HP dv2500t laptop and a link on how to integrate the drivers with nlite?

     

    Thanks.

     

    Friday, February 08, 2008 7:56 PM
  •  

    So let me understand this. Microsoft is going to be releasing a service pack to bring XP up to date, thus XP SP3, but isn't going to add SATA drivers? Would you mind explaining the logic in this decision? Almost all of the business class PCs running now come with SATA drives and by the way, the standard procedure for adding drivers to Unattended installs does not work per articles on the Microsoft site!! There are workarounds but Microsoft does not support them. To me this seems like a problem that should be addressed.
    Friday, February 08, 2008 9:53 PM
  • I agree that the SATA drivers should be added to SP3. I use RIS mostly and working on WDS and the documentation for both are appauling. None of the ducumetation references itself and each one seems to tell you to do everything in a different way. It would be of great use to have them in the service pack.
    Saturday, February 09, 2008 12:02 AM
  •  

    I will tell you the logic behind this,  Micosoft want everyone to use Vista instead instead of XP.   Its a cop out. 

     

    Explain this Vista SP1 gets released with updated drivers.

    XP SP3 gets released with no updated drivers. hmmnnn

     

     

    Thursday, February 28, 2008 12:41 PM
  •  Le1 wrote:

    I have used nLite, but I have not been successful at adding the SATA drivers for a laptop install.  Can you give me a link to get the correct drivers for an HP dv2500t laptop and a link on how to integrate the drivers with nLite?

    Thanks.


    You will need the drivers for the Intel GM965 chipset.
    http://www.intel.com/support/chipsets/sb/CS-025753.htm

     mla1 wrote:

    Microsoft does not support images that have been created / altered with nLite.  If Microsoft supported this method then I would use the tool.  Also (Microsoft's) Business Desktop Deployment 2007 does not like CD's that have been created/altered with nLite.


    Microsoft will go so far as to give you guides posted online, and give you the ability to collect updates to integrate into an image - but that is as far as Microsoft will go regarding slipstreamed CD's unless you are willing to go to Pro Level Support for $259 per issue.  It is not classified as a consumer level issue as consumers typically will not ever think to, or need to, or want to, make such a thing.  It is classified internally as an advanced Pro issue.  Even at Pro Level Support, they are only supposed to assist updating online network share install sources which are typically Volume License network install sources for corporate LAN's mass deployment - as opposed to an actual bootable disk.  Technically, the creation of a backup disk, or the creation of a slipstreamed disk, or any bootable optical disk, is not supported by Microsoft.

    By not supported, that means Microsoft will not talk to you on the phone to help you make it (nor help via email correspondence with you personally to help you make it).  It doesn't mean that you can not legally make it and use it on your own.

    Therefore, the use of nLite is indeed not supported.  Neither is it supported, in the context of support implied here, if you make it manually as Microsoft's guides posted at various sites on its domain (Microsoft Knowledge Base, MSDN, Technet sites) suggest using the /integrate switch at the command line.

    Making and using them has no impact on your warranty and/or ability to use it for calling Microsoft for other issues that are within their support boundaries.

    When you call Microsoft, they will want to check "Control Panel->System Properties" to check your PID (Product ID number) and to see what Service Pack level you are at.  That way we can see if this copy has a warranty with Microsoft and make sure it is up-to-date enough (i.e. it is SP2 or later as installed at the moment - the SP level of the install source is irrelevant).

     ely67241 wrote:

    So let me understand this. Microsoft is going to be releasing a service pack to bring XP up to date, thus XP SP3, but isn't going to add SATA drivers? Would you mind explaining the logic in this decision? Almost all of the business class PCs running now come with SATA drives and by the way, the standard procedure for adding drivers to Unattended installs does not work per articles on the Microsoft site!! There are workarounds but Microsoft does not support them. To me this seems like a problem that should be addressed.


    Microsoft does not make drivers.  Drivers tell Windows how to communicate with the respective hardware said driver was written for.  The manufacturer of the hardware makes the driver.  Microsoft does provide DDK (Driver Development Kits) to hardware manufacturer's so that they can know what format a driver should be in to maximize efficiency communicating to a given OS (there are different DDK's for different OS'es).  Microsoft has the WHQL (Windows Hardware Quality Labs) program where hardware manufacturer's can voluntarily submit their drivers for a Microsoft review process - and if said drivers submitted pass inspection Microsoft can make them available on the Windows Update website - but this is only on a voluntary basis.

    Using nLite and the driver packs at Driverpacks.net you can make an install source with virtually all known drivers that will end up being a little over 1GB large - so it would end up being an installation DVD rather than a CD.  I've built them with great success.

    Microsoft, for their part, take no responsibility in the realm of drivers, and they really have no reason to EXCEPT WHERE IT CONCERNS THE HARDWARE MICROSOFT THEMSELVES MAKE.  For XP on a SATA system, you need the floppy with the drivers, or a slipstreamed disk with at least the SATA drivers added to it already.

     mla1 wrote:

    I will tell you the logic behind this,  Microsoft want everyone to use Vista instead instead of XP.   Its a cop out.

    Explain this Vista SP1 gets released with updated drivers.

    XP SP3 gets released with no updated drivers. hmmnnn



    Vista has SO MANY PROBLEMS that Microsoft is fighting an insane uphill battle to make it as appealing as possible.  MOST hardware has no Vista Drivers to speak of.  There have always been issues when Microsoft released a new OS - but never before on a scale like this.  Never before have OEM's demanded they downgrade back to a previous OS (they have forced Microsoft to allow them to go back to XP from Vista).  Never before have Microsoft's Pro and Premier customers demanded and petitioned Microsoft to extend the life-cycle of the previous OS (http://weblog.infoworld.com/save-xp/archives/2008/01/sign_the_save_x.html).

    It isn't a cop out that XP does not get drivers in SP releases - this has never been the case with XP or any other MS product - except for Vista.  I could fill a book with the reasons Vista is a failure, and why Microsoft can never admit it.
    Thursday, February 28, 2008 4:31 PM
  • They may decide not to include SATA drivers, but if they would at least update to allow the drivers to be loaded from somewhere other than Floppy Drive A.

    Ever heard of legacy free systems?  That 1st load building an image is a pain.

    Friday, February 29, 2008 1:27 AM
  •  JustAnotherHack wrote:

    They may decide not to include SATA drivers, but if they would at least update to allow the drivers to be loaded from somewhere other than Floppy Drive A.

    Ever heard of legacy free systems?  That 1st load building an image is a pain.



    Agreed.

    The first water-cooled system I built was in Jan. 2003 and it was on a Giga-byte 8KNXP booting from a Western Digital 120GB SATA drive.  The board had a Silicon Image 3112 SATA hard disk controller as well as the Intel 875 chipset controlling an additional 2 SATA ports.  SATA was brand-spanking-new just out of the gates and Giga-byte concluded that their board just couldn't boot from a SATA drive when I first tried to figure out why the XP CD didn't detect any drives...

    To top it off, Intel and Silicon Image hadn't posted a specific 3.5" floppy sized version of the drivers yet, nor did the motherboards CD include drivers that could fit on a floppy.  After a bit of a learning curve, I managed to pull the .inf files from the .exe drivers that were posted and on the CD and managed to home brew a floppy that XP would use.  I quickly became convinced of the slipstream virtues.

    Would it be fantastic if Microsoft even included as much as a generic SATA driver?  Of course.  Will they?  Not likely.  nLite and driverpacks.net is testimony to just how easy it would be to include them...  But there would be other legal issues and internal procedures for MS to implement it that would amount to enough P.I.T.A. to build a Greek Restaurant  (P.I.T.A. = Pain In The ***).

    Naturally, they will not do it.
    Friday, February 29, 2008 3:05 AM
  •  JustAnotherHack wrote:

    They may decide not to include SATA drivers, but if they would at least update to allow the drivers to be loaded from somewhere other than Floppy Drive A.

    Ever heard of legacy free systems?  That 1st load building an image is a pain.

     

    I agree 110%!  I've just been fighting with this very thing, and it's got me ticked!  It even seemed to see the USB as A drive, but still wouldn't read the *)&)(&*)(&( drivers!  Time to go try nLite Smile.

    Sunday, March 16, 2008 9:27 PM
  • If you want to add the intel sata drivers manually to your source cd follow these instructions.  (note these instructions were not copied from another site they were written from scratch by myself after a lot of trial and error). 

     

    Download the latest intel matrix Storage manager from Intels Website

    h***://www.intel.com/support/chipsets/imsm/index.htm

    download the F6 floppy configuration.

    The latest file at the time of writing this document is 7.8.0.1012

    Extract the file to a floppy it should contain the following files.

    iaahci.cat

    iaahci.inf

    iastor.cat

    iastor.inf

    iastor.sys

    license.txt

    readme.txt

    txtsetup.oem

    Copy the contents of a windows XP source to the root of C:\ and call the folder the same name as the source cd in which you are using in my case I have the following (for the purpose of this article mine is called CDNAME

    c:\CDNAME

     

    open c:\CDNAME\i386\txtsetup.sif

    We need to add the following line "iastor.sys=1,,,,,,4_,4,1,,,1,4" under [SourceDisksFiles] (scroll down to the last entry under [SourceDisksFiles and copy it to the bottom of the list. it.

    [SourceDisksfiles]

    entry1

    entry2

    entry300 odd

    iastor.sys=1,,,,,,4_,4,1,,,1,4

    The above states that its an original source cd and a new install code. ALSO ***note the above code will be the same even if a new sata driver is available

    Open up the txtsetup.oem from the floppy drive you should see a list of hardware id's for each sata driver.

    for example the ICH8M driver will look like this.

    [HardwareIds.scsi.iaStor_ICH8M]

    id = "PCI\VEN_8086&DEV_282A&CC_0104","iaStor"

    with c:\CDNAME\i386\txtsetup.sif still open

    Edit find [HardwareIdsDatabase] Scroll to the last record under [hardwareIdsdatabase] and paste each ID so it looks like the following.

     

     

    [HardwareIdsDatabase]

    entry1

    entry2

    entry3 etc....

    PCI\VEN_8086&DEV_282A&CC_0104="iastor"

    PCI\VEN_8086&DEV_2829&CC_0106="iastor"

    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"

     

    Next we need to find [Scsi.Load] scroll down to the last entry and add the following to the bottom a

    [Scsi.Load]

    iastor=iastor.sys,4

    Next Find [SCSI] scroll down to the bottom again and add the following

    [SCSI]

    iastor = "Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)"

    iastor = "Intel(R) 82801HEM/HBM SATA AHCI Controller (Mobile ICH8M-E/M)"

    iastor = "Intel(R) 82801HR/HH/HO SATA RAID Controller (Desktop ICH8R)"

    iastor = "Intel(R) 82801HR/HH/HO SATA AHCI Controller (Desktop ICH8R)"

    iastor = "Intel(R) 631xESB/632xESB SATA RAID Controller (Server/Workstation ESB2)"

    iastor = "Intel(R) 631xESB/632xESB SATA AHCI Controller (Server/Workstation ESB2)"

    iastor = "Intel(R) 82801GHM SATA RAID Controller (Mobile ICH7MDH)"

    iastor = "Intel(R) 82801GR/GH SATA RAID Controller (Desktop ICH7R/DH)"

    iastor = "Intel(R) 82801GR/GH SATA AHCI Controller (Desktop ICH7R/DH)"

    iastor = "Intel(R) 82801GBM SATA AHCI Controller (Mobile ICH7M/DH)"

    iastor = "Intel(R) 82801FR SATA RAID Controller (Desktop ICH6R)"

    iastor = "Intel(R) 82801FR SATA AHCI Controller (Desktop ICH6R)"

    iastor = "Intel(R) 82801FBM SATA AHCI Controller (Mobile ICH6M)"

     

    ***note the above was copy and pasted from the txtsetup.oem from the floppy you need to replace the name of the driver with Iastor for each driver (as shown above)..

     

     

    Save the txtsetup.sif ***Note at the bottom of the txtsetup.sif is an end of marker file, do not delete this line***

     

    We now need to copy create the drivers path and the drivers (from the floppy).

    Create the following file path.

    C:\CDNAME\$OEM$\$1\DRIVERS\SATA

    Copy accross the following files from the floppy

    IAAHCI.cat

    IAAHCI.inf

    IASTOR.cat

    IASTOR.inf

    IASTOR.sys

    the iastor.sys needs to be made into a cab file. to do this type the following command from a command prompt

    Makecab C:\CDNAME\$OEM$\$1\Drivers\SATA\iastor.sys C:\CDNAME\$OEM$\$1\Drivers\SATA\iastor.sy_

    you can now delete the file iastor.sys.

    In the C:\CDNAME\$OEM$\$1\Drivers\SATA you should now have the following files

    IAAHCI.cat

    IAAHCI.inf

    IASTOR.cat

    IASTOR.inf

    IASTOR.sy_

     

    Next we need to copy the iastor cab that you have just created into the c:\CDNAME\i386 folder. (iastor.sy_)

    Open Dosnet.inf IN NOTEPAD from the i386 directory

    EDIT FIND [Floppy.Files2] and copy the following "d1,iastor.sys" directly underneath

    like so

    [Floppy.Files2]

    d1,iastor.sys

    Do the same for [Files]

    [Files]

    d1,iastor.sys

    Save dosnet.inf

    now we need to create a winnnt.sif

    Open notepad and and enter the following text.

     

    [Unattended]

    OemPnpDriversPath="DRIVERS\SATA"

    OemPreinstall=Yes

    DriverSigningPolicy=Ignore

    NonDriverSigningPolicy=Ignore

    [Data]

    MsDosInitiated=No

     

    Save the file in C:\CDNAME\i386 called winnt.sif

    we now have the edited CD.

     

    Save the contents as a bootable iso, using magic iso.

     

    If you dont have magic iso you can use Iso buster to extract the Microsoft Corporation.img file and use your cd burning software to create  a bootable cd.

     

    Enjoy mla1.

    Monday, March 17, 2008 9:08 AM
  •  mla1 wrote:

    If you want to add the intel sata drivers manually to your source cd follow these instructions.  (note these instructions were not copied from another site they were written from scratch by myself after a lot of trial and error). 

    ...

    Enjoy mla1.

     

    LARGE Thank you, Mia1!

     

    This is exactly what I was looking for! 

     

     mla1 wrote:

    iastor.sys=1,,,,,,4_,4,1,,,1,4

    The above states that its an original source cd and a new install code. ALSO ***note the above code will be the same even if a new sata driver is available

     

    Will this same format work with other controllers?  Is there somewhere I can find out what each of those commas is supposed to delimit?  Also, why do all the SCSI entries get marked with IASTOR, while some of them have iaahci in the txtsetup.oem files?  This has got me so frustrated, I'm bound and determined to get it down pat before this is over!

     

    thanks again for your help!

     

    Derek

    Tuesday, March 18, 2008 1:50 AM
  •  

    In the scsi section you only need to have 1 line

    [scsi]

    iastor = "My intel sata raid controller" 

     

     

    It references the iastor.sys file (the only sys file in the download).

     

     

    Tuesday, March 18, 2008 8:14 AM
  • Am I suppose to type the section header along with the data??  [Scsi.Load] and [SCSI]

    [Scsi.Load]

    iastor=iastor.sys,4


    [SCSI]

    iastor = "Intel(R) 82801HEM SATA RAID Controller (Mobile ICH8M-E)"


    Wednesday, May 07, 2008 3:19 AM
  • Regarding that, I've got a catalog for a computer store that is advertising a downgrade CD from Vista to XP Pro with one of their acer laptops

    Wednesday, May 07, 2008 4:06 AM
  • I'm not the big tech guru and maybe the previous answers/solution is the better solution but in case of Intel's SATA drivers I suggest going the official way
    http://www.intel.com/support/chipsets/imst/sb/cs-020825.htm
    Wednesday, May 07, 2008 7:39 AM
  • There used to be a HP white paper on Sata

    http://h20000.www2.hp.com/bc/docs/support/SupportManual/c00765791/c00765791.pdf

    that explained it well. 

    Typically now I need it again, it is nowhere to be found. 

    I had no problem with xp sp2 but sp3 is giving me the following and it has me baffled.

    ERROR on unattended setup: TXTSETUP.OEM caused an unexpected error (18) at line 1742 in d:\xpsp3\base\boot\setup\oemdisk.c



    Tuesday, October 28, 2008 11:16 AM
  • The reasoning behind the SATA not being included

     is fairly straight forward. When Xp was introduced, SATA was only a glimmer on the horizon. And the base image Sp2, and 3 are designed around is centered on this image. Anything that drivers and additional hardware was was supported by the Manufactor. There is no contract to include any new drivers. But since floppys were supported by ancient operating systems. That portion of the OS is included.

    So things that are contracted and introduced with the original Gold Xp, like flash player. Are updated in the image. Adding a complexity to the Sp3 with any sort of generic image driver would introduce more timing issues.

      The answer my friends is the emulation of floppys that some motherboard systems do have. Bootable images can be created. And allow for a repair installation of Sp3. (see below)

      I do understand that booting off a CD, and having an driver available with a floppy sounds and is ancient design. But there are other resources, like msfn.org which has a clear tutorial about integrating SATA drivers. and the afore mentioned driver set in another posting. And of course different options available to address problems like the error you are receiving.

     

      But please always take this bit of advice to heart, and perform. Back up your system. Hard drives with just your important information will always save time. And more longer term storage like CD/RW disks are cheap and plentiful.

     

    Only takes about half an hour on slower systems to create a new installation disk. Even with slower processors. Mostly limited by the r/w drive speed present on your system.

     

    Keith

    Thursday, October 30, 2008 3:18 AM
  • Found a copy of the HP pdf document. Here is the extract for your information.

     

     

     

    Adding SATA Drivers to an Installation CD

    Where these guidelines are applicable

    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 customers who need to add SATA support by creating a custom Windows XP Service Pack 2 Installation CD.

    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 Intel SATA AHCI Controller Driver, SoftPaq SP32478.exe, from www.hp.com.

    3) Extract all the files from the SoftPaq. A USB floppy is necessary for this step. Run sp32478; this will create a floppy disk. The files will be located on this floppy.

    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.

    7) Also copy all the files from step 4 to the c:\xpcd\$oem$\$1\drivers\sata folder.

    6

    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(R) 82801 SATA RAID/AHCI Controller (ICH5,6,7)"

    12) Save the file and exit notepad.

    13) Extract the files from c:\xpcd\support\tools\deploy.cab to c:\deploytools

    14) Create a new winnt.sif:

    a. Execute setupmgr.exe (extracted from deploy.cab in step 13).

    b. Select "Create new answer file"

    c. Select "Unattended Setup"

    d. Select "Windows XP Pro"

    e. Select "User Interaction desired"

    f. Select "Set up from a CD"

    g. Enter desired information under each of the following Settings sections

    h. Save the file as c:\xpcd\i386\winnt.sif

    15) Open the c:\xpcd\i386\winnt.sif in notepad

    16) Under the section [Unattended], add the following lines: OemPreinstall=yes OemPnPDriversPath=drivers\sata DriverSigningPolicy = Ignore

    17) Save winnt.sif and close notepad

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

    a. Note that the volume label of the CD must be the same as from the original XP CD

    7

    b. The custom XPCD must be bootable (with the Microsoft bootblock). There are various 3rd party utilities which can accomplish this. Utilities from Microsoft are available, as detailed in the following section.

    Monday, November 03, 2008 4:43 PM
  • Yea, I have installed XP Pro on my HP laptop dv9535nr using nLite and it worked very slick. I have Service Pack 1 disk then I slipstreamed SP2 and the SATA driver and it burned the disk and all! Worked very slick. From what I've read you have to have atleast SP2 on the disk for it to recognize the SATA drivers. From there you can mabey find driver packs for your specific model. If it is a custom build you better go hunting. Do not slipstream the other drivers as they may not install properly just load them after the install rebooting after each one usually starting with the chipset, PCI, then the graphics and whatever you need from there.
    HP dv9535nr Triple Boot: XP Pro, Vista, Windows 7 RC1
    Thursday, June 11, 2009 1:13 AM