[mark49]

Cunning1inguist, on Feb 4 2005, 04:55 PM, said:

Bâshrat the Sneaky, on Sep 24 2004, 11:48 AM, said:

If you want to integrate PATA/SATA/RAID drivers, you can try my DriverPack MassStorage, take a look at http://www.BTSunatte.../EN/DriverPacks !

Greetz,

Bâshrat the Sneaky

that doesn't work for the text portion of the setup, that only works for the gui portion, right?

you will need to copy some important xxx.sys files to \i386 folder

[RickSteele]

[SourceDisksFiles]
fasttx2k.sys = 1982,,,,,,,1982,0,0

[HardwareIdsDatabase]
PCI\VEN_105A&DEV_3376 = "fasttx2k"
PCI\VEN_105A&DEV_3373 = "fasttx2k"


[SCSI.load]
fasttx2k = fasttx2k.sys,4


[SCSI]
fasttx2k = "WinXP Promise FastTrak 376/378 ™ Controller"

Above are the entries in my txtsetup.sif for the Promise RAID controller on the ASUS P4C800E deluxe. I used nlite0997b to completely create my custom install package including integrating all drivers; but did not create an iso just yet. I've tried every method I could find, created countless bootable CD's and setup would always fail until now. The [SourceDisksFiles] section nlite writes correctly to txtsetup but the rest of the entries must also be inserted-above is mine, either just before the EOF marker or under the corresponding sections in the txtsetup.sif file. nlite already cabs all the sy_, dl_, in_, ca_, etc. in the nldrv folder during the create process but, the individually cabbed RAID/mass storage files/drivers must also be included in the I386 directory of your CD so that text mode can access them. The one exception-the cat file is copied as is, not cabbed. No other reference to these drivers is necessary anywhere, at least when using nlite. Also all the rest of my drivers seem to install correctly and completely using nlite's method; ie: nldrv folder and txt/dossetup etc....My automated install went perfectly.

[mark49]

Quote

[SourceDisksFiles]fasttx2k.sys = 1982,,,,,,,1982,0,0

?

[RickSteele]

mark49, on Mar 23 2005, 10:33 PM, said:

Quote

[SourceDisksFiles]
fasttx2k.sys = 1982,,,,,,,1982,0,0

?
<{POST_SNAPBACK}>

I left that as nlite had it because it worked and after so many disappointing attempts to finally get it so that everything goes perfectly.....well if it ain't broke don't fix it. I mean I can now install all completely unattended-no F6..etc. and my system is completely stable.

[raskren]

1982 is the custom target location that nLite uses to install drivers. I believe it is \Windows\nldrv.

[RickSteele]

raskren, on Mar 24 2005, 12:04 PM, said:

1982 is the custom target location that nLite uses to install drivers.  I believe it is \Windows\nldrv.
<{POST_SNAPBACK}>

Thanks; and you are correct about the NLDRV location but I have it deleted by nlite after it's used because I load all my setup files-winXp_pro cd, drivers, Office 2003 pro etc in my last partition and then using both policy editor and reg hacks point all to those locations if any program requires them in the future. Still, even though the RAID files are in my I386 folder I figure it can't hurt to leave them in NLDRV also. That nlite is one awesome app!

[Tangled]

Some help please:
After making the necessary changes in the txtsetup.sif and booting from the CD, I can see the textbased setup loading my controller (VIA SATA RAID Controller), but after the loading is done, setup still can't find 'any harddrive'.

I know the driver I use is correct. Only explanation I can think of is an incorrect device ID in txtsetup.inf causing textbased setup to not find my controller. So I doublechecked the device ID (PCI\VEN_1106&DEV_3149&SUBSYS_70201462, tried it with and without the SUBSYS_* part).

So what can be the reason setup still can't find an hdd? This is Windows XP 64 RTM btw, but just to be sure I've put all necessary files in both the I386 and AMD64 folder so it shouldn't be any problem.

Confused...

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

[HardwareIdsDatabase]
PCI\VEN_1106&DEV_3149 = "viamraid"

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

[SCSI]
viamraid = "VIA SATA RAID Controller"

viamraid.sy_ is in the I386 and AMD64 folder.

[RickSteele]

Tangled, on Apr 6 2005, 03:46 PM, said:

Some help please:
After making the necessary changes in the txtsetup.sif and booting from  the CD, I can see the textbased setup loading my controller (VIA SATA RAID Controller), but after the loading is done, setup still can't find 'any harddrive'.

I know the driver I use is correct. Only explanation I can think of is an incorrect device ID in txtsetup.inf causing textbased setup to not find my controller. So I doublechecked the device ID (PCI\VEN_1106&DEV_3149&SUBSYS_70201462, tried it with and without the SUBSYS_* part).

So what can be the reason setup still can't find an hdd? This is Windows XP 64 RTM btw, but just to be sure I've put all necessary files in both the I386 and AMD64 folder so it shouldn't be any problem.

Confused...

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

[HardwareIdsDatabase]
PCI\VEN_1106&DEV_3149 = "viamraid"

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

[SCSI]
viamraid = "VIA SATA RAID Controller"

viamraid.sy_ is in the I386 and AMD64 folder.
<{POST_SNAPBACK}>

Are these drivers specifically for winXP pro 64-bit?-32-bit drivers will not work at all. I have no experience at all with 64-bit yet; or VIA-another 2 months or so to upgrade my hardware and then.... Apparently 64-bit windows is extremely particular and will not recognize anything not specifically developed for it. Check this out:
http://www.winxpcent...inxp64first.php
written by Digital Dave.

Also, did you cab all your files first before copying them to I386?-all except the *.cat files and did you double check your BIOS settings. I'm sorry I can't be more help right now.

[tkenn1s]

raskren, and others...

I just have to say you guys ROCK!

I wanted to create a automated, slipstream CD for my new Dell. You could imagine my frustration when I first got the "no hard drives found" error message. (Only have an SATA HD in the machine) Anyway, found this thread (thanks for linking to it GreenMachine!) and I'm now happily installing WinXP on my SATA disk.

Thank you imensely for saving so much of my time and hair. (since I now don't have to pull it out)

[nazz]

I cannot get my Promise SATA150 TX working. I1m not sure , but I think the problem is here:

[SourceDisksFiles]
ulsata.sys = 1
ptipbm.dll = 1

Where most others is driver.sys = 1,,,0,0,1,4 etc.

Can anyone help

[Bâshrat the Sneaky]

Please read the guide properly...

Use this indeed:

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

[nazz]

It still does not detect any drives attached to the card. Below are the entries in my txtsetup.sif:

[SourceDisksFiles]
ulsata.sys = 1,,,,,,4_,4,1

[HardwareIdsDatabase]
PCI\VEN_105A&DEV_3375.DeviceDesc="WinXP Promise SATA150 TX Series ™ IDE Controller"

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

[SCSI]
ulsata = "WinXP Promise SATA150 TX Series ™ IDE Controller"

In my $OEM$ folder drivers\ulsata (drivers) and the ulsata.sys file in my i386.

What am I doing wrong?

[Bâshrat the Sneaky]

TRIPLE POST

Sorry mate, but this isn't acceptable!

[Marthax]

Thanks raskren for this guide! I used your method with the Si3112r and it works great!

[ack_thbbft]

Wow.... not sure what else I can say about this thread.

Unfortunately, it's a "wow, am I confused," kind of "wow."

I built my IC7-G rig (not IC7-Max3, though I hope it will work just the same) two years ago without a floppy drive, but after skimming through this thread, I think it may be easier to go out and get a floppy drive for $10.

What brought me to this thread is that I'm about to replace my 160GB 8MB cache drive (which has been accumulating bad sectors) with two 250GB 16MB cache drives, and was considering a RAID configuration (still not sure if I'll do 0 or 1; would be nice if I could afford to do 0+1, if it is even possible).

What really gets my goat is that Microsoft and the mobo manufacturers are not taking floppy-less systems into account when it comes to things like this in the first place, particularly how increasingly common they are. Even Dell has gone floppy-less.

Making a nice unattended-install CD or DVD with SP2, my latest drivers, SATA RAID configuration, etc, would be a dream come true. At the very least, I want to set up RAID without a floppy, even if I must do an attended install.

[RickSteele]

Try using nlite 99.9b and do not modify anything manually after. The Promise RAID-ich5r-and Intel drivers-875P-P4C800E-Deluxe, along with all other drivers I require all installed unattended-using winnt.sif-with no problems at all. Integrate WMP 10, all your post SP2 hotfixes manually though before using nlite making sure you have the updated Windows Installer 3.1 Redistributable_v2_KB893803 in there; I integrate mine using .cmd files; updating them monthly, or as required.

[RickSteele]

nazz, on Apr 15 2005, 01:06 AM, said:

It still does not detect any drives attached to the card. Below are the entries in my txtsetup.sif:

[SourceDisksFiles]
ulsata.sys = 1,,,,,,4_,4,1

[HardwareIdsDatabase]
PCI\VEN_105A&DEV_3375.DeviceDesc="ulsata"

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

[SCSI]
ulsata = "WinXP Promise SATA150 TX Series ™ IDE Controller"

In my $OEM$ folder drivers\ulsata (drivers) and the ulsata.sys file in my i386.

What am I doing wrong?
<{POST_SNAPBACK}>

Write the [HardwareIdsDatabase] as above and Bob's your uncle

[ack_thbbft]

I found a MaximumPC article (link here) describing how to do pretty much what this guide describes, but I have a few questions.

Let me start off by saying I've already upgraded my install CD files with SP2, which I was very fortunate to finish, since the CD drive scratched a nice gash into my original XP Pro w/SP1 CD when I ejected it after copying the contents. I've already made a backup of the SP2 version, though I did forget to add the boot image file, but I can always reburn it with the .img file added, as long as I have the files.

Also, I don't plan on using the Silicon Image SATA controller, unless there is a particular reason (other than RAID 1 support) why I should use it over the Intel controller built into the southbridge. In my previous post, I said I hadn't decided on RAID 0 or 1, but I think I'll be going with 0 unless, again, someone has good reason to talk me out of it. After all, giving up half my storage space is a big pill to swallow over having a backup, and the files I work with take a LOT of space.

So, on to the questions...

1. I've found multiple [SourceDisksFiles] sections in my TXTSETUP.SIF file. Will it matter which one I use for the iaStor.sys entry?

2. The [SourceDisksFiles] entry on this guide says to use a value of "100,,,,,,3_,4,1,,,1,4" whereas the MaxPC article says to use "1,,,,,,_x,4,1". Does either value work, or does it have to do with MaxPC's folder structure versus the one used in this guide?

3. The iaStor.inf file (from the current version 1.33 on the Abit website) actually has three PCI entries:
PCI\VEN_8086&DEV_2652&CC_0104
PCI\VEN_8086&DEV_24DF&CC_0104
PCI\VEN_8086&DEV_25B0&CC_0104
Should I include all three entries, or is only the "24DF" listed in this guide necessary?

More questions to follow, I'm sure.

[raskren]

ack,

RAID0 does not halve your storage space. RAID1 does. RAID0 usually offers twice the performance of RAID1.

Two 80 GB drives:
RAID0 = 160 GB really fast array
RAID1 = 80GB redundant array

If your motherboard uses the ICH5R southbridge you should use the Intel SATA ports. This is because there is a direct connection between the SATA ports and the southbridge. The Silicon Image ports go through the PCI bus to the southbridge which limits them to 133 MB/s (SATA RAID speeds can be faster). I believe the link between the north and southbridges is 533 MB/s so there won't be a bottleneck.

1.) You can use any section you wish.

2.) http://www.msfn.org/board/index.php?showtopic=14852&hl=

Follow that link for info on the txtsetup.sif numbers and commas. I recommend using the numbers I have specified in this thread.

3.) Use the Intel IaStor drivers instead of Abit's. Intel's are usually newer.

[ack_thbbft]

raskren, on May 25 2005, 04:02 PM, said:

ack,

RAID0 does not halve your storage space.  RAID1 does.  RAID0 usually offers twice the performance of RAID1.

Two 80 GB drives:
RAID0 = 160 GB really fast array
RAID1 = 80GB redundant array

That's exactly what I was saying, that going with RAID 1 is a big pill to swallow (I'd be going from 500GB to 250GB). Many people on other boards say the threat of losing all your data isn't worth the increased performance of a RAID 0 setup, but losing half my total space by going with RAID 1 would really limit me, as well. (My current hobby is editing videos transferred from my TiVo, and they can be 5+ GB in size, each.)

Quote

If your motherboard uses the ICH5R southbridge you should use the Intel SATA ports.  This is because there is a direct connection between the SATA ports and the southbridge.  The Silicon Image ports go through the PCI bus to the southbridge which limits them to 133 MB/s (SATA RAID speeds can be faster).  I believe the link between the north and southbridges is 533 MB/s so there won't be a bottleneck.

Actually, I'm using a couple 133 PATA drives connected via Serillel2 SATA converters, so I'll still be limited to 133 MB/s, even on the Intel controller. Even my original drive is connected that way. I got a really great deal on two 250GB drives with 16MB cache for $99 each, and figured that outweighed the price difference of going with true-SATA drives.

Quote

1.) You can use any section you wish.

2.) http://www.msfn.org/board/index.php?showtopic=14852&hl=

Follow that link for info on the txtsetup.sif numbers and commas.  I recommend using the numbers I have specified in this thread.

3.) Use the Intel IaStor drivers instead of Abit's.  Intel's are usually newer.
<{POST_SNAPBACK}>

1.) Sounds good.

2.) I've seen that thread and couldn't make much of it, but I'll give it another gander.

3.) I assume the Intel drivers on Abit's site are the current version, but I'll check out Intel's site to see if there's a difference, anyway.