[raskren]

Tests still show Intel's controller having lower cpu usage than SI so I'd still recommend it, even with PATA drives.

I've found that most of the major motherboard vendors take weeks if not months (if at all) to update their drivers, be it chipset, video, sound, etc.

[ack_thbbft]

I took your advice and checked Intel's site, and they seem to have a LOT of different driver updates for the 875P/ICH5R. It even seems to imply that their updated driver will enable RAID 1 on the Intel controller, which originally was only RAID 0 (the SI having both 0 and 1).

Have you found that to be the case?

[raskren]

The only driver you should need for this is the text mode driver and the chipset driver. On an 875P board, RAID 0 and 1 are enabled in the Intel boot ROM. You shouldn't need a driver to enable RAID 1.

[elusiveelf]

Thank you!! very much I have been going crazy trying to figure this one out

[mcslemon]

Well, it has to be said that this topic has helped massivly.. I've got XP Setup to run using my SATA drivers, so it doesnt say it can't see any installed hard disks..

Trouble starts when XP has finished setting up. It goes thru into the GUI screen where is detects and installs drivers - looking promising!

When it reboots and loads for the first time - it stops, and reboots! I get a flash of a BSOD but I couldnt tell you what it said!

My SATA is Promise 20378 running on a MSI Neo2 Motherboard... using an XP SP2 disk!

I've downloaded the most recent drivers off the MSI website and am going to slipstream them into the build (i'd used the original ones on the CD )... I'm also going to make a couple of changes which I found later on in this rather long topic!! (txtsetup.sif)

Firstly:

PCI\VEN_105A&DEV_3375.DeviceDesc="ulSata"

instead of

PCI\VEN_105A&DEV_3373 = "ulSata"

and

ulsata.sys = 1,,,,,,3_,4,1,,,1,4

instead of

ulsata.sys = 100,,,,,,3_,4,1,,,1,4

Any ideas what could be going wrong? I admit I didnt use the most up to date drivers off the site.. but I'll be doing that soon... and ideas in the mean time would be useful as I'm at a loss.

Thanks for any info.

[mcslemon]

Well, I've rebuilt the disk with the current drivers and it is still blue screening! Any help would be appreciated.

[raskren]

My comments in blue
Following code is wrong ->

PCI\VEN_105A&DEV_3375.DeviceDesc="ulSata"

instead of

PCI\VEN_105A&DEV_3373 = "ulSata"

and

ulsata.sys = 1,,,,,,3_,4,1,,,1,4

instead of

This code and the code above should produce the same results. ->

ulsata.sys = 100,,,,,,3_,4,1,,,1,4

Both of your PCI device IDs are different for the two lines you posted (PCI\VEN_...). You need to look in your txtsetup.oem file that should be included with your drivers for the correct id(s).

This post has been edited by raskren: 30 August 2005 - 07:22 AM

[dccb]

I just want to say that to this day, this is the only SATA guide that has consistently works for me for several different SATA drivers.

Great job, thanks raskren

[Bâshrat the Sneaky]

raskren, if I may ask, why do you still copy the driver files to the $OEM$\TEXTMODE folder? It's known to be unnecessary.

[Incroyable HULK]

A little precision for people using Multi-Boot CDs...

You will add the cab xxx.sy_ file to your boot folder, not to I386

cheers

[dccb]

Bâshrat the Sneaky, on Oct 2 2005, 12:33 PM, said:

raskren, if I may ask, why do you still copy the driver files to the $OEM$\TEXTMODE folder? It's known to be unnecessary.

He's right. I didn't copy the driver files to the TEXTMODE folder, and everything still works perfectly fine.

[FFA]

uhhh this is sound cool! i like that !

but one quastion!

if i have 2 raptor discs and i want to use them as a C:\ drive! and as raid0
does this CD do that automatic without inseting that stupid floppy disc ?

im asking because im not 100% sure !
please reply

[benitomdq]

raskren, i`m your b***h now. Thanks for that awsome instructions.

[Br4tt3]

Pure Krome, on Jan 5 2004, 11:42 PM, said:

>>Why? Its only 10 or 12 lines that have to be added.

from what i understand with the Setup.sif file, there is a section called MassDrivers or something (it's been a few months since i last did any unattended stuff). MS added this section to make it QUICK and SIMPLE to add RAID/SATA drivers to an unattended install.

by QUICK and SIMPLE i mean :-
o) Dump the drivers in a Folder
o) Tell the installation (setup.sif) which driver to use.

there. done. simple.

anyways ...

Yeah, this approach is easier if u have one controller to handle. Downside, u will need multiple .sif unattend files to support multiple raid/scsi/sata controllers as the unattend.sif file will only try to boot onto the one listed in each winnt.sif. Now, for home users, oki, business with about 40 controllers, no way! Much better to have one txtsetup.sif file that supports all the controllers.

[Sgt_Strider]

I'm just curious. Since Intel no longer have the Intel Application Accelerator available, do I use the new Intel Matrix Stroage file to get the drivers? My notebook has the newer i945 mobile express chipset.

Guys, I'm also somewhat confused by this guide. I currently have a desktop with a SATA drive in which I have zero problems installing w/o modifying any files. I just followed the MSFN unattended guide and I put the chipset and all the other drives in the $OEM$ directory and everything installs. Yet, when I tried to use the following method with an Intel chipset, it doesn't work. Do I really need to modify those files in order to get the slipstream to work? If so, then what about the conventional method taught from the MSFN guide?

Btw, my desktop uses a Nvidia Nforce 4 chipset.

[MadBoy]

I was thinking since there is so many views and a lot of problems with it, i maybe could write program that would require you to scpecify like 5 things - Place for winnt.sif and some other crucial stuff and then the program would do all for ppl.

I think you guys overlooked some poor guy in this post that posted that he needs a place to put his program on that does all the work for you It would save you all a lot of time.

Oh well if it will be enough intrest maybe i can do simple program to do most work that is needed for you.

[the_doc735]

raskren, on Jan 6 2004, 03:43 AM, said:

IV. Putting the puzzle together
The first place to add a copy is to the TXTMODE folder of your CD. That is: "c:\xpcd\$OEM$\TEXTMODE" Here you can dump the 7 Silicon Image files and 4 Intel files.
Location number two is the location specified (or will be specified) in Winnt.sif for OEMpnpDriversPath. On my CD this is:

$OEM$\$1\Drivers\01
$OEM$\$1\Drivers\02
.
.
.
$OEM$\$1\Drivers\nn

I have added the Intel drivers (all 4 files) to folder 01 and the SI drivers (7 files) to 02. Here you need to have your SATA drivers in the lowest numbered folders. That is, don't have your printer drivers in 01 and SATA in 02.

The third and final location is in the i386 directory which will be located at the root of your CD. This time we only need to be concerned with the *.sys files of each driver set. That would be iastor.sys and si3114r.sys; you do not need SIWinAcc.sys for this step. I chose to compress these files and I recommend you do the same. Use the MAKECAB utility to do so. You'll end up with "iastor.sy_" and "si3114r.sy_" Now simply copy both of these files to the i386 directory. Now we're done copying files.

V. Modifying installation files
The first file to be modified is TXTSETUP.SIF which is in the i386 directory. This file tells Windows what files to load during the text-only portion of setup. We are going to modify the file to make Windows think that Microsoft put these new driver files in i386 and load them accordingly. Open up TXTSETUP.SIF and do a search for [SourceDisksFiles]. In my file it was on line 181. Now add this text EXACTLY AS SHOWN (except what's in the brackets).

[SourceDisksFiles]
iaStor.sys = 100,,,,,,3_,4,1,,,1,4
si3114r.sys = 100,,,,,,3_,4,1,,,1,4

Each driver listing needs to be on its own line...you'll get the format once you look in TXTSETUP.SIF. You can put this anywhere within the [SourceDisksFiles] section. I'm aware that there are multiple instances of [SDF]...I added my drivers to the first instance.

For a detailed explanation of what all those numbers and commas mean go here.

Still within TXTSETUP.SIF look for [HardwareIdsDatabase] around line 18270. These entries associate drivers with PCI device Ids detected on the machine. Within this section add these lines:

[HardwareIdsDatabase]
PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor"
PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_288510F1 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0 =  "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_90181695 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_F642270F = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_100415BD = "Si3114r"

As you can see there is only one Id for Intel and multiples for SI which is OK. Now remember the file "txtsetup.oem" that we extracted from both driver sets? That's a text file which can be opened in Notepad and it contains the device Ids. If you're trying this out with other drivers and don't know the proper Id, look in txtsetup.oem or the INF file associated with that particular driver.

We now need to find [SCSI.load] in TXTSETUP.SIF. Look around line 18725. Add the lines below to this section.

[SCSI.load]
iaStor = iaStor.sys,4
si3114r = si3114r.sys,4

One more section to go...

Find [SCSI] - around line 21059. Add this:

[SCSI]
iaStor = "Intel(R) 82801ER SATA RAID Controller"
si3114r = "Silicon Image SiI 3114 SATARaid Controller"

Here you can replace the text in quotes with anything you want. So if you want iaStor to be "Super Pimped hizard dizisk controllaz" then go for it.

That's it for TXTSETUP.SIF. The next file we need to create or modify is WINNT.SIF. If you're frequenting the unattended forums then you probably already know how to create or modify it. If you don't, check
this out.
Here all we need to do is point OEMpnpDriversPath to the locations we set up. Remember $OEM$\$1\Drivers\01? If that is the location of the Intel or SI files then WINNT.SIF should read like this...

OemPnPDriversPath="Drivers\01;Drivers\02;Drivers\03;Drivers\04;Drivers\05;Drivers\06"

If you have multiple folders like I do make sure that its all contained on ONE line (the forum software might wrap it here).

my txtsetup.oem looks like the attachment [herewith]

but I'm not sure how to convert this from silicon image to promise?

could you give me a walk through on the promise pcd20378 chipset contoller please?
[or anyone that knows]

very grateful.
THANK YOU!

Attached File(s)

•  TXTSETUP.JPG (91K)
  Number of downloads: 90

This post has been edited by the_doc735: 19 September 2006 - 08:02 PM

[the_doc735]

MadBoy, on Sep 14 2006, 04:50 PM, said:

I was thinking since there is so many views and a lot of problems with it, i maybe could write program that would require you to scpecify like 5 things - Place for winnt.sif and some other crucial stuff and then the program would do all for ppl.

I think you guys overlooked some poor guy in this post that posted that he needs a place to put his program on that does all the work for you It would save you all a lot of time.

Oh well if it will be enough intrest maybe i can do simple program to do most work that is needed for you.

...yes please

or help me with the promise PCD20378 raid chipset?

many thanks!

[MadBoy]

well i can't realy help you with that yet i would have to read it all, see how it works to be REALY able to help you. This project isn't for 1 day And why you don't try nlite ?

This post has been edited by MadBoy: 20 September 2006 - 06:34 AM

[the_doc735]

raskren, on Jan 6 2004, 03:43 AM, said:

The first place to add a copy is to the TXTMODE folder of your CD. That is: "c:\xpcd\$OEM$\TEXTMODE" Here you can dump the 7 Silicon Image files and 4 Intel files.
Location number two is the location specified (or will be specified) in Winnt.sif for OEMpnpDriversPath. On my CD this is:

$OEM$\$1\Drivers\01
$OEM$\$1\Drivers\02
.
.
.
$OEM$\$1\Drivers\nn

I have added the Intel drivers (all 4 files) to folder 01 and the SI drivers (7 files) to 02. Here you need to have your SATA drivers in the lowest numbered folders. That is, don't have your printer drivers in 01 and SATA in 02.

The third and final location is in the i386 directory which will be located at the root of your CD. This time we only need to be concerned with the *.sys files of each driver set. That would be iastor.sys and si3114r.sys; you do not need SIWinAcc.sys for this step. I chose to compress these files and I recommend you do the same. Use the MAKECAB utility to do so. You'll end up with "iastor.sy_" and "si3114r.sy_" Now simply copy both of these files to the i386 directory. Now we're done copying files.

V. Modifying installation files
The first file to be modified is TXTSETUP.SIF which is in the i386 directory. This file tells Windows what files to load during the text-only portion of setup. We are going to modify the file to make Windows think that Microsoft put these new driver files in i386 and load them accordingly. Open up TXTSETUP.SIF and do a search for [SourceDisksFiles]. In my file it was on line 181. Now add this text EXACTLY AS SHOWN (except what's in the brackets).

[SourceDisksFiles]
iaStor.sys = 100,,,,,,3_,4,1,,,1,4
si3114r.sys = 100,,,,,,3_,4,1,,,1,4

Each driver listing needs to be on its own line...you'll get the format once you look in TXTSETUP.SIF. You can put this anywhere within the [SourceDisksFiles] section. I'm aware that there are multiple instances of [SDF]...I added my drivers to the first instance.

For a detailed explanation of what all those numbers and commas mean go here.

Still within TXTSETUP.SIF look for [HardwareIdsDatabase] around line 18270. These entries associate drivers with PCI device Ids detected on the machine. Within this section add these lines:

[HardwareIdsDatabase]
PCI\VEN_8086&DEV_24DF&CC_0104 = "iaStor"
PCI\VEN_1095&DEV_3114&SUBSYS_61141095 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_288510F1 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_047AA0A0 =  "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_0478A0A0 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_0479A0A0 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_90181695 = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_F642270F = "Si3114r"
PCI\VEN_1095&DEV_3114&SUBSYS_100415BD = "Si3114r"

As you can see there is only one Id for Intel and multiples for SI which is OK. Now remember the file "txtsetup.oem" that we extracted from both driver sets? That's a text file which can be opened in Notepad and it contains the device Ids. If you're trying this out with other drivers and don't know the proper Id, look in txtsetup.oem or the INF file associated with that particular driver.

We now need to find [SCSI.load] in TXTSETUP.SIF. Look around line 18725. Add the lines below to this section.

[SCSI.load]
iaStor = iaStor.sys,4
si3114r = si3114r.sys,4

One more section to go...

Find [SCSI] - around line 21059. Add this:

[SCSI]
iaStor = "Intel(R) 82801ER SATA RAID Controller"
si3114r = "Silicon Image SiI 3114 SATARaid Controller"

Here you can replace the text in quotes with anything you want. So if you want iaStor to be "Super Pimped hizard dizisk controllaz" then go for it.

That's it for TXTSETUP.SIF. The next file we need to create or modify is WINNT.SIF. If you're frequenting the unattended forums then you probably already know how to create or modify it. If you don't, check
this out.
Here all we need to do is point OEMpnpDriversPath to the locations we set up. Remember $OEM$\$1\Drivers\01? If that is the location of the Intel or SI files then WINNT.SIF should read like this...

OemPnPDriversPath="Drivers\01;Drivers\02;Drivers\03;Drivers\04;Drivers\05;Drivers\06"

If you have multiple folders like I do make sure that its all contained on ONE line (the forum software might wrap it here).

PROMISE PDC20378:
...this is what I've done: continues next meesage or two [due to attachment size restrictions]....

IS IT RIGHT THOUGH?....

Attached File(s)

•  textmode_folder.JPG (31.51K)
  Number of downloads: 43
•  378_raid_drivers.JPG (22.51K)
  Number of downloads: 55
•  378_raid_drivers2.JPG (27.18K)
  Number of downloads: 35
•  378_ata_drivers.JPG (29.81K)
  Number of downloads: 30
•  378_ata_drivers2.JPG (25.84K)
  Number of downloads: 26
•  I368_folder_fasttrax.JPG (11.64K)
  Number of downloads: 29
•  I368_folder_ulsata.JPG (11.56K)
  Number of downloads: 26
•  sourcedisksfiles_txtsetup_sif.JPG (8.17K)
  Number of downloads: 9
•  hardwareIDsDataBase_txtsetup_sif.JPG (34.94K)
  Number of downloads: 50
•  scsi_load_txtsetup_sif.JPG (6.75K)
  Number of downloads: 7
•  scsi_txtsetup_sif.JPG (12.72K)
  Number of downloads: 34
•  pnp_code_winnt_sif.JPG (26.89K)
  Number of downloads: 35
•  prra1_folder.JPG (19.01K)
  Number of downloads: 25
•  prra2_folder.JPG (21.28K)
  Number of downloads: 23

This post has been edited by the_doc735: 20 September 2006 - 08:26 AM