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 )...

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:

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:

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:

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:

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.

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!

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

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?

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

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

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.

Doesn't NLite do this?

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.

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.

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

Hi there, can anyone answer this question?

Thanks


Phil.

It should, yes.

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

The _x here...



... means the file is UNcompressed!

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

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

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

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.

http://www.msfn.org/board/index.php?showto...mp;#entry536321

Founf that to be very useful

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

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

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?

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

@mjschug

Hi,

have a look at this:

http://www.msfn.org/board/lofiversion/index.php/t32594.html


The problem is you have to add the driver in dosnet.inf as well.

CU

appleseed

Yikes! Thanks man!

*having a looksie*

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)



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:



Cheers,

This took me a long time to figure this out because several years ago every Internet search resulted in telling you that you only need to add the entries into the TXTSETUP.SIF.

THAT IS NOT ENOUGH!

And for those who know, they are not willing to share, as if it was some commercial secrets or whatever.

I am glad MSFN.org is around. I learnt alot from this forum and the generous people here who are willing to share! Kudos to you all!


Anyways, how are you guys reading Kixtart scripts? It shouldn't be too hard to understand even if you don't know VB/VBS or Kixtart.

The RAID Slipstreamer was mainly written using Kixtart scripts; the GUI was written using VB6. I am really not a programmer. In fact I am terrible in programming.


This is just a small portion of the whole program. In this case, it was the IBM ServeRAID 8i/8k Controller subroutine:


PS. ALTER.EXE is a DOS program to search and replace text within a file. In this case, it searches for "d1=aacsas.sys" and replaces it with "d1,aacsas.sys"


1) Depending on the platform type, copy all the vendor-provided drivers to the user-provided "\$OEM$\$1\Drivers\RAID" path. Hence the reason why you need to specify the "OEMPnPDriversPath=Drivers\RAID" strings in the UNATTEND.TXT answer file

2) And then copy all the compressed .SYS files to the user-provided I386 path.

You don't really have to compress the .SYS files but I'd like to follow the Microsoft standard and I have to conserve disc space as I have to stuff 18GB operating system files into a 4.7GB DVD disc.



That's all, really.

For more information, refer to my other post elsewhere: http://www.msfn.org/board/index.php?showto...173&st=164#

I just wanted to say thank you Anderz for writing a sweet guide. I have the same exact S-ATA controller on a HP laptop and after reading up on tons of guides that did not work. Yours worked on the very first try! I used UltraEdit to find the exact lines where you added your entries to the txtsetup.sif file

Magic ISO to save the boot info. Then reload boot info after creating the modified Win XP ISO.

The S-ATA drive was automatically detected like an IDE drive!

Thank you MSFN and thank you Anderz!!

Yup yup,

My sata model is exactly the same, am glad I had allready some experience with msfn and that I know exactly how to make a nice unattended xp pro dvd. Now I really need to try tis, coz with my old dvd on my new notebook it doesn't work anymore.

Let's have a look,

Will give some more specs if it worked.

greetz
Jonathan

I am trying to setup the drives for the Dell precision 690
SAS 5lir drivers. The details are below. I have also included the dell drivers as an attachment.

I am not sure what numbers to use for the files... How do I determine all of the correct options? See my details below. Once I maded the changes to the system to my txtsetup.sif I get a windows stop error when it starts to load windows. Prior to the change I was getting an error saying no hard disk found.

eg... The drivers oemsetup.txt

has the following:
[Files.scsi.DELL_SAS_5X] (I copied the sys inf and cat files to the i386)
driver = d1,symmpi.sys,SYMMPI
inf = d1,symmpi.inf
inf = d1,delpseud.inf
catalog = d1,mpixp32.cat

so I added the following to [SourceDisksFiles] (I am not sure how or what options I select here. Again the drivers are uncompressed and are sitting in the I386 directory. Note I also have the drivers in my $oem$ so once out of text mode Windows can install the correct driver.
symmpi.sys = 1,,,,,,_x,4,1
symmpi.inf = 1,,,,,,_x,4,1
delpseud.inf = 1,,,,,,_x,4,1
delpseud.inf = 1,,,,,,_x,4,1

and I added the list below to [HardwareIdsDatabase]
PCI\VEN_1000&DEV_0054&SUBSYS_1F041028, "symmpi"
PCI\VEN_1000&DEV_0054&SUBSYS_1F061028, "symmpi"
PCI\VEN_1000&DEV_0054&SUBSYS_1F071028, "symmpi"
PCI\VEN_1000&DEV_0054&SUBSYS_1F081028, "symmpi"
PCI\VEN_1000&DEV_0054&SUBSYS_1F091028, "symmpi"

I added the following to [SCSI.Load]
symmpi = symmpi.sys,4

Under [SCSI]
I added symmpi = "DELL PERC5 RAID Controller Driver (Windows XP)" but I also see symmpi = "LSI Logic PCI Fibre Channel Host Adapter"

Thanks for the guide, but I'm confused. Where do you place the drivers then? In the $OEM$\$1\drivers folder? Your post doesn't mention anything about placing the drivers. Or maybe I don't have to since this is modified and Windows XP will install its own driver?

Actually Anderz already mentioned it here:



Keep in mind this method only works for simple drivers that only comes with a SYS file. For more complex drivers in which it comes with its own GUI for configuring the controller in Windows, you will need to slipstream/integrate the DLL and other files that come with the driver as well. It gets complicated in these cases.

He only said that I need the information from the other files, but what do I do with them after I use those information? Do those files go into a folder inside the $OEM$\$1\drivers directory or what? That is what I have been asking.

where did you downloaded latest Intel drivers? I can't find it on Intel site. I'm on IBM ThinkPad R60e

yes, put 'em in $OEM$\$1\drivers directory, you can create also a new folder in it

for compressed its

It failed for me, third CD-R wasted today trying to slipstream SATA drivers. :[

For the record, I tried using the latest version of Intel's drivers for ICH8R. Followed the guide on e

i did everything the guide said and even edited the dosnet.inf and all went well until the first boot into windows then bluescreened. i have an HP laptop and it had the same drivers as this guide.

Well,

I know different ways to do this have been beaten to death.

Bashrat would remember but about 2 years ago we spent about 4 Months developing a method of creating an additional Driver CAB File with more Drivers for Windows and it would RETAIN the drivers in Windows AFTER Install so lets say you have a bunch of USB items or do a Hardware change the Drivers were already present and the Windows Driver Auto-Detect would find the drivers in Windows and install them automatically.

We also used this method for RAID Drivers as this method added drivers to the heart of Windows.

This was a HUGE break through and the research led to several new Methods being developed for Integrating drivers based on the original method.

It might be advisable to take a trip down memory lane and visit the thread (That is now closed).

Windows Keeping The Drivers Method

thanks this is just what the doctor ordered.

I Strongly suggest the read through of the entire thread.

It has the entire development process and covers a great deal of testing. The information is INVALUABLE and will give you a great insight into how Windows works during install.

Somewhere in there I wrote an entire Tutorial on how to do it (The Integration). It is WELL worth the time and it is a GREAT read!

i read through, it's all very informative. can those ideas be use on an already installed windows. i like the idea of the *.cab driver file.

I have never tried to Integrate into an existing install....

As I said, if you are doing a fresh install it is FANTASTIC!

The reason I wonder is that many of the entries are then integrated into the Registry and configuration files.

I may do a quick look into the possibility but I would not hold my breath (At least it will be much more difficult to make it work).

I admit it would be a fun to give it a try....

This thread is a life saver!

I was attempting to downgrade from Vista to XP on a Gateway MT6840 use the f6 method and a USB floppy drive, which just wouldn't work.

This method worked the first time! Thank you, thank you, thank you.


UPDATE: I spoke too soon. I was able to get XP installed up until the first re-boot. Now it is stuck in a BSOD loop. I am going to try to use the raid slipstreamer application and see how far I get with that.

i always use this format to install mostly all raid i can find...
via .. intel ... simage.. sis ... jmicron.. ITE .... High Point...
and last problem with nvidia...
using beta version of nvraid drivers at the moment...
just wish to have a solution to intergrate nvdia raid to compartible with all nforge 2 3 4 5 6
**** nvidia drivers sux.

Hi "242", did you managed to get win XP working on your Gateway MT6840 laptop?, if so could you please let me know how did you managed to do it?, I have an exact Gateway laptop model as yours and I want to downgrade to XP as well.....



edit: So, I managed to slipstream the drivers with "nlite" and it was VERY easy, way much better than the method described here, so don't even bother with this thread and instead integrate any drivers with "nlite", not a single problem and it can be done in just a few minutes

I followed the directions and when I try to install windows, almost right away it says can't find viamraid.sys and I have no choice but to restart the computer.

I have copied all the files from my floppy disk (from other computer on the network) that I know work and will let me install xp on this current machine.

txtsetup.oem
viamraid .cat, .sys, no extension, .in_, .inf, .sy_, .ca_

I copied all these files to:

root dir
i386
i386\nldrv
i386\nldrv01
" 002
" 003

Where the hell is windows looking for this file? Or am I missing something completely stupid?

Tried nlite, then before it burnt swapped out the txtsetup.sif, but on boot didn't like that (since initially couldn't find my sata hd...)


[SourceDisksFiles]
viamraid.sys = 1,,,,,,,4,1

[HardwareIdsDatabase]
"PCI\VEN_1106&DEV_3349","viamraid"
"PCI\VEN_1106&DEV_0591","viamraid"
"PCI\VEN_1106&DEV_3249","viamraid"
"PCI\VEN_1106&DEV_3149","viamraid"
"PCI\VEN_1106&DEV_3164","viamraid"

[SCSI.Load]
viamraid = viamraid.sys,4

[SCSI]
viamraid = "VIA VT8251/8237/8237A/6421/6410 SATA RAID Controller(Windows 2K/XP/SRV2003)"

Hey Everyone,

Here are the steps I took to get the MT6840 downgraded to XP from Vista. Please note, this presumes you're comfortable with the concepts of installing an operating system and its device drivers. If you aren't, print this and give it to someone who is

If you're computer blows up, catches fire, or otherwise does something you don't like because of these suggestions, take it back to the manufacturer but DON'T assume that I am responsible for anything. I've just spent 15 hours of a holiday weekend compiling this. It should take you a couple of hours to accomplish on your own following this information.

Enjoy!

-----------------------
1. Log into the Gateway Support Site and provide your serial # to get SOME (not all) XP drivers. Do NOT use Model Number as they won't provide the files you need.

2. Use NLite (http://www.nliteos.com/) to slipstream an XP installation with the Text Mode drivers for the SATA install onto a new CD. The textmode drivers are provided by Gateway in the "F6 Floppy X86" directory.

3. Install XP

4. Install XP SP2 (off of a CD, thumbdrive, etc...) - download it here - http://www.microsoft.com/downloads/details...;displaylang=en

---Begin Installing Devices - I don't remember the order but it shouldn't be TOO important---

5. WIFI Driver - From Previous Gateway Download site (using your serial number) - Yes, you need to have downloaded this first

File Description: Intel Wireless Driver
Version: 11.1.0.86

Run AUTORUN

6. AUDIO Driver - Downloaded from http://support.gateway.com/support/drivers...p;uid=167551212

File Description: Audio Driver
Version: SigmaTel 5.10.4946.0

Run SETUP


7. MEDIACARD READER Driver - From Previous Gateway Download site (using your serial number) - Yes, you need to have downloaded this first

File Description: Windows XP and Vista (32/64-bit) TI Media Card Reader Driver
Version: 2.0.0.6


Run SETUP

8. LAN Driver - NOT the one from the Gateway Download Site - Not even an INTEL LAN Device - go to MARVELL

Marvell Yukon 88E8038 PCI-E Fast Ethernet Controller Drivers

http://www.marvell.com/drivers/driverDispl...d=175&pId=6

Decompress and RUN Setup

9. Install BLUETOOTH if you want - It doesn't do anything right now

10. MODEM Driver - Motorola Driver - Get it from the Motorola Site (SoftModem 56 or SM56)

http://www.motorola.com/softmodem/public_d...6.12.07_DFV.zip

RUN SSetup

11. VIDEO Driver - Download from Intel (for the Intel 945GM Chipset)

http://downloadcenter.intel.com/detail_des...amp;prdmap=2529

http://downloadcenter.intel.com/T8Clearanc...e=&lang=eng

You can search on Win2K_XP1431 (as of this writing) and find the download + readme

--LAST STEP--

Lastly...you will likely have an SM Bus Device Issue in Device Manager...to correct it you'll need the correct chipset drivers.

12. Go to the Intel Site and Search on

http://downloadcenter.intel.com/Product_Fi...x?ProductID=816 (Intel Chipset Software Installation Utility)

If you are running XP Pro (not HOME), just go to the below...

http://downloadcenter.intel.com/filter_res...mp;submit=Go%21

Run SETUP


-------------------------

At this point, you should have all of the drivers installed and NO unknown devices in Device Manager. If you still do have issues, get into an online chat session with Gateway. If you ask nicely and are persistent, they'll try to help you although they don't have an obligation from a Warranty perspective to do so.

Good Luck...my experience with XP has been BLAZING FAST on the Gateway MT6840 after installing everything. (Sorry Vista but you need to lose some weight and become more stable). I hope your experience is great, too!

So, where the heck are the Gateway SATA drivers in the "F6 Floppy X86" directory? I've put in my serial number on Gateway's website and have been searching all over with no luck.

Thanks in advance for any clues

I have just tried this procedure with XP Pro x64 (with SP2 which I manually integrated with the /integrate switch) and the ICH8R Intel RAID driver (7.6.0.1011) and it wasn't successful. My RAID partition was seen and the installation seemed to go OK (both the textmode part and the GUI part), but after the first reboot (ie. after installation had finished), it brought up the Windows XP x64 boot screen but immediately reboots again (ie. the progress bar bit does not even start moving), only now it brings up the "Windows was not shutdown properly" boot screen, "Do you want to (a) Start Windows Normally, ( Start Windows in Safe Mode" etc. It will then keep going in this cycle.

Because it's x64, TXTSETUP.SIF is placed in the AMD64 folder. Here's exactly what I added:









As you can see, I added the new lines immediately after the section header, and before anything else in that section. Is that OK ?

Where am I going wrong ?


BTW, I also tried adding the Intel ICH8R ACHI driver, which is actually the same as the RAID driver (ie. iastor.sys). To do this, I simply modified the relevant sections to:





Is this correct for also adding the ACHI driver ?

bripab007

http://support.gateway.com/support/drivers...le.asp?id=20974

Down load this SATA driver, will install to C:/cabs/xxxxxxx
Read the readme.txt file and it will tell you to run a floppy make exe to A: disk.
When windows CD starts and you see F6 for drivers, hit F6 and then when at screen "S" enter then continue.

Phil