Anderz

Add/slipstream SATA drivers - A fully working solution

60 posts in this topic

Hi y'all!

What I'm about to explain is how you can add SATA/RAID drivers by editing only one file - TXTSETUP.SIF - which is placed in the I386 folder (C:\XPCD\i386\TXTSETUP.SIF). I've tested this method and it's bulletproof (atleast so far :whistle:)...

First of all I want to thank the guy that posted THIS several years back (and it was for Windows 2000 back then), without that posting I would still be pounding my head against a brick-wall.

This post should cover whatever SATA controller out there - just test for yourself. The guy in the original posting mentioned above, is talking about an IBM ServerRaid driver/controller. The SATA driver I want to install is for the Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH).

Follow this guide step by step:

1. Comment out or remove anything under MassStorageDriver and OEMBootfiles you might have in WINNT.SIF.

2. Download the latest drivers (I'm using the current v6.x driver from Intel) and extract them.

3. Copy only the .SYS file (iastor.sys) to the C:\XPCD\I386 folder. Keep the other files - you'll need some information from them a little later. Note that it's important that the .SYS file is uncompressed.

4. In the C:\XPCD\I386 folder you must now open the file TXTSETUP.SIF in your favorite text-editor and do the following:

4.1 Under the section [sourceDisksFiles] add:

iastor.sys   = 1,,,,,,_x,4,1

Remember to change the name of the sys file to the one you use! I put this on line 1653.

4.2 Under the section [HardwareIdsDatabase] add:

PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"

You will find the information for your specific controller in the file TXTSETUP.OEM that you extracted with the driver. I put this on line 18800.

4.3 Under the section [sCSI.Load] add:

iastor = iastor.sys,4

Change the names iastor and iastor.sys to your file's name. I put this on line 19244.

4.4 Under the section [sCSI] add:

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

Change the name iastor to your file's name. I think the name in "" can be whatever you like, but I used the same name used in TXTSETUP.OEM just in case. I put this on line 21586.

5. Save the file and exit. Burn the image and boot using the CD... Voila!

--------

Notes:

- No need to use the TEXTMODE folder. Just delete.

- No "The file txtsetup.oem caused an unexpected error (18)...blahblah" error message during installation. This is the real reason I'm now using this method.

- No need for ekstra files in the image - but you still need drivers defined in OemPnPDriversPath in WINNT.SIF. This explanation is only for the textmode and protected mode of the Windows XP Pro installation!

- No need for any entries in WINNT.SIF (except the one above).

- The only downside is that you actually have to edit the TXTSETUP.SIF file. :P

Tell me what you think - does it work for you as well?

@Philster: I think you can add all the different SATA drivers you want to, but I've only tested the one I documented here. Sharing is the thing!

@mjschug: You did what I said in number 3? I haven't tested this over a network installation, however, I will test this on RIS in a week or so (I hope). I will keep you updated on this.

@azaze1: Fixed! Thanks! :blushing:

@LispWarez: Hmmm .. didn't see it!

Edited by Anderz
0

Share this post


Link to post
Share on other sites

Will this method allow me to add SATA drivers for a number of PCs / laptops as i want an image i can use with a few devices?

0

Share this post


Link to post
Share on other sites

WOAH, dude. This is sweet. I will try it out...

0

Share this post


Link to post
Share on other sites

Just found this. I will try it and give feedback. :thumbup

0

Share this post


Link to post
Share on other sites

I recently started picking apart our Dell XP install images. They are a pretty standard unattended, but it has support for several RAID/SATA controllers built-in. I used WinMerge to find the differences, and the most changes where in the TXTSETUP.OEM file you are talking about. There are also some random entries in the various hive.inf's, but as you have found out most of it can be done in that one file! It's pretty swank, I didn't slim it down as you have, but I did use their files as a base to integrate the Intel SATA drivers onto a vanilla OEM WinXP, as well as a Server2K3 unattended.

One thing to comment on, in the Dell image there is no need for any OEMFiles part, as all the files are integrated into the source. I believe that's where the extra edits in the hive.inf's come in, helps complete the circle I guess. Instead of just the *.SYS file, the Dell image has all the support files for the drivers...inf's, cat's, dll's, etc. So in the end it's more work but cleaner in that you can (possibly) skip the OEMFiles.

0

Share this post


Link to post
Share on other sites

wow this has been covered in the past. i have been using this method for the last year or so. maybe the thread i got it from got lost in the history of these forums.

0

Share this post


Link to post
Share on other sites
Hi y'all!

What I'm about to explain is how you can add SATA/RAID drivers by editing only one file - TXTSETUP.OEM - which is placed in the I386 folder (C:\XPCD\i386\TXTSETUP.OEM). I've tested this method and it's bulletproof (atleast so far :whistle:)...

4. In the C:\XPCD\I386 folder you must now open the file TXTSETUP.SIF in your favorite text-editor and do the following:

I'm not posting this to point fingers in a negative way, but you started by saying this is going to be done by editing txtsetup.oem. It is even referenced twice, but then you specify editing the built in txtsetup.sif. In which case this method is covered already in the Drivers forum. It would be nice to just drop your drivers and 1 new text file into the I386 dir.... but that can't be done as initially suggested at the beginning of this post. Oh well.

0

Share this post


Link to post
Share on other sites
Hi y'all!

What I'm about to explain is how you can add SATA/RAID drivers by editing only one file - TXTSETUP.OEM - which is placed in the I386 folder (C:\XPCD\i386\TXTSETUP.OEM). I've tested this method and it's bulletproof (atleast so far :whistle:)...

First of all I want to thank the guy that posted THIS several years back (and it was for Windows 2000 back then), without that posting I would still be pounding my head against a brick-wall.

This post should cover whatever SATA controller out there - just test for yourself. The guy in the original posting mentioned above, is talking about an IBM ServerRaid driver/controller. The SATA driver I want to install is for the Intel® 82801GBM SATA AHCI Controller (Mobile ICH7M/DH).

Follow this guide step by step:

1. comment out or remove anything under MassStorageDriver and OEMBootfiles you might have in WINNT.SIF.

2. Download the latest drivers (I'm using the current v6.x driver from Intel) and extract them.

3. Copy only the .SYS file (iastor.sys) to the C:\XPCD\I386 folder. Keep the other files - you'll need some information from them a little later.

4. In the C:\XPCD\I386 folder you must now open the file TXTSETUP.SIF in your favorite text-editor and do the following:

4.1 Under the section [sourceDisksFiles] add:

iastor.sys   = 1,,,,,,_x,4,1

Remember to change the name of the sys file to the one you use! I put this on line 1653.

4.2 Under the section [HardwareIdsDatabase] add:

PCI\VEN_8086&DEV_27C5&CC_0106 = "iaStor"

You will find the information for your specific controller in the file TXTSETUP.OEM that you extracted with the driver. I put this on line 18800.

4.3 Under the section [sCSI.Load] add:

iastor = iastor.sys,4

Change the names iastor and iastor.sys to your file's name. I put this on line 19244.

4.4 Under the section [sCSI] add:

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

Change the name iastor to your file's name. I think the name in "" can be whatever you like, but I used the same name used in TXTSETUP.OEM just in case. I put this on line 21586.

5. Save the file and exit. Burn the image and boot using the CD... Voila!

--------

Notes:

- No need to use the TEXTMODE folder. Just delete.

- No "The file txtsetup.oem caused an unexpected error (18)...blahblah" error message during installation. This is the real reason I'm now using this method.

- No need for ekstra files in the image - but you still need drivers defined in OemPnPDriversPath in WINNT.SIF. This explanation is only for the textmode and protected mode of the Windows XP Pro installation!

- No need for any entries in WINNT.SIF (except the one above).

- the only downside is that you actually have to edit the TXTSETUP.OEM file.

Tell me what you think - does it work for you as well?

I followed your instructions to the T and did not work. Iam getting the following error during textmode setup.

"the file fasttx2k.sys could not be found. Press any key to continue"

I am using a combination of Linux Boot CD and a Unattended installation over a network.

Thanks

-$chug

0

Share this post


Link to post
Share on other sites
Will this method allow me to add SATA drivers for a number of PCs / laptops as i want an image i can use with a few devices?

Hi there, can anyone answer this question?

Thanks

Phil.

0

Share this post


Link to post
Share on other sites

Will this method allow me to add SATA drivers for a number of PCs / laptops as i want an image i can use with a few devices?

Hi there, can anyone answer this question?

Thanks

Phil.

It should, yes. :yes:

0

Share this post


Link to post
Share on other sites
Doesn't NLite do this?

Yes. NLite did exactly this with the SATA driver for HP laptop, except the iastor.sys is compressed as iastor.sy_.

0

Share this post


Link to post
Share on other sites

Doesn't NLite do this?

Yes. NLite did exactly this with the SATA driver for HP laptop, except the iastor.sys is compressed as iastor.sy_.

The _x here...

iastor.sys   = 1,,,,,,_x,4,1

... means the file is UNcompressed! :)

Edited by Anderz
0

Share this post


Link to post
Share on other sites

so what would we put if we wished to compress them?

0

Share this post


Link to post
Share on other sites

3_ I think it was, but I use the files uncompressed so I haven't tested it.

0

Share this post


Link to post
Share on other sites
so what would we put if we wished to compress them?

Use MakeCab and ModifyPE to compress the file and correct the Checksums

0

Share this post


Link to post
Share on other sites

I've seen directions similar to this here and the Beginner's PC site.

It's a thorough guide to adding your mass storage drivers to the txtsetup.sif file.

I've used it since for my ITRAID but it doesn't work for HPT 370/372. I think problem is HPT uses two files: hptpro.sys and hpt3xx.sys and it's not clear how you specify these two files.

Good luck.

0

Share this post


Link to post
Share on other sites

@Spacesurfer: Hmmm .. pretty good! :) Same method...

@JuMz: Hehe .. you linked to this thread. :D

0

Share this post


Link to post
Share on other sites

This is the commonly used method. It's been in use for YEARS. And when you start setup through winnt.exe/winnt32.exe then 'your method' will fail, because you are forgetting to update the dosnet.inf file. ;)

0

Share this post


Link to post
Share on other sites
This is the commonly used method. It's been in use for YEARS. And when you start setup through winnt.exe/winnt32.exe then 'your method' will fail, because you are forgetting to update the dosnet.inf file. ;)

Do you mind informing us what the required entries would be in the dosnet.inf for his example?

0

Share this post


Link to post
Share on other sites
This is the commonly used method. It's been in use for YEARS. And when you start setup through winnt.exe/winnt32.exe then 'your method' will fail, because you are forgetting to update the dosnet.inf file. ;)

Yeah ... that would be of some interest for me too - although I won't use it! :) Thanks for the tip Bâshrat the Sneaky.

0

Share this post


Link to post
Share on other sites

Yikes! Thanks man! :D

*having a looksie*

0

Share this post


Link to post
Share on other sites

Yes, these are similar to the methods I used

If anyone is interested, I have recently updated the "RAID Slipstreamer" (for work) that integrates all known SCSI/RAID/SATA drivers used in my company into Windows XP, Windows 2000 and Windows Server 2003 I386 source, allowing for automatic detection of mass storage drivers (for use with unattended installation). Country IT staffs have been using this for several years already and they all seem very happy. And the best is that, I only need to update the package once every 1.5 to 2 years (IT support staffs hate change :) )

It's really nothing more than what you may already know but for [lazy] people who don't feel like doing it themselves...

email me if you are interested = itwins@gmail.com. It's only 3.6MB small and it slipstreams these drivers (the editor attachment doesn't work!)

Download RAID Slipstreamer v2.0 from Rapidshare

(Work email excerpt to global IT support staffs)

untitledyv1.png

Raid Slipstreamer v2.0 supports:

- All models of IBM System X servers

- All models of IBM eServer xSeries servers

- All models of Dell PowerEdge servers

- All models of Dell Precision Workstations

- All models of Dell desktops with SATA/RAID Controllers and AHCI enabled

Raid Slipstreamer v2.0 supports the following Mass Storage Devices:

Windows 2003

- IBM ServeRAID 8i/8k SAS Controller

- Intel 82801FR/GHM/GR/GH/GBM/FBM AHCI/SATA RAID Controller

- Adaptec Ultra320 SCSI Controller / IBM ServeRAID 7e SCSI Controller

- IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i/7k Controller

- LSI Logic PERC 4e/Di,4e/Si,4e/DC,4/Di,4/DC,4/SC,3/QC,3/DC,3/DCL,3/SC

- LSI Logic SAS 5x RAID Controller

- LSI Logic Perc 5e/i Raid Controller

- Adaptec 39160 Family SCSI Controller

- Adaptec PERC 2, 2/Si, 3/Si, 3/Di SCSI Controller

- QLogic QL40xx iSCSI Controller

- QLogic QL2300 Fiber Channel Controller

- Adaptec AIC-94xx SAS/SATA Controller

- Adaptec ASC-48300 SAS/SATA Host Adapter

- Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller

- VMware SCSI Controller

Windows 2000

- IBM ServeRAID 8i/8k SAS Controller

- Intel 82801FR/GHM/GR/GH/GBM/FBM AHCI/SATA RAID Controller

- Adaptec Ultra320 SCSI Controller / IBM ServeRAID 7e SCSI Controller

- IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i/7k Controller

- LSI Logic PERC 4e/Di,4e/Si,4e/DC,4/Di,4/DC,4/SC,3/QC,3/DC,3/DCL,3/SC

- LSI Logic SAS 5x RAID Controller

- LSI Logic Perc 5e/i Raid Controller

- Adaptec 39160 Family SCSI Controller

- Adaptec PERC 2, 2/Si, 3/Si, 3/Di SCSI Controller

- QLogic QL40xx iSCSI Controller

- QLogic QL2300 Fiber Channel Controller

- Adaptec AIC-94xx SAS/SATA Controller

- Adaptec ASC-48300 SAS/SATA Host Adapter

- Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller

- VMware SCSI Controller

Windows XP

- IBM ServeRAID 8i/8k SAS Controller

- Intel 82801FR/GHM/GR/GH/GBM/FBM AHCI/SATA RAID Controller

- Adaptec Ultra320 SCSI Controller / IBM ServeRAID 7e SCSI Controller

- IBM ServeRAID 4M/4Mx/4L/4Lx/5i/6M/6i/7k Controller

- QLogic QL2300 Fiber Channel Controller

- Dell SAS 5x RAID Controller

- LSI Logic Perc 5e/i Raid Controller

- Adaptec AIC-94xx SAS/SATA Controller

- Adaptec ASC-48300 SAS/SATA Host Adapter

- Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller

- VMware SCSI Controller

Raid Slipstreamer v2.0 has been tested to work on the following servers:

- IBM ServeRAID 8i SAS Controller (IBM System X x3650 server - Windows XP and Windows 2003)

- Intel 82801FR SATA Raid Controller with AHCI enabled (Dell Precision Workstation 390)

- Home-Built server (Promise Technologies Ultra 33/66/100/133 TX2 IDE Raid Controller)

- VMware Workstation v5.5.x (virtual LSI Logic 1020/1030 Ultra320 SCSI Controller)

PS. During slipstream, it will create and copy all the RAID drivers to the "\I386\$OEM$\$1\Drivers\RAID" folder. You may need to add this string in your UNATTEND.TXT answer file:

[Unattended]
OEMPnPDriversPath=Drivers\RAID;

Cheers,

Edited by iTwins
0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.