I am trying to sort out the remaining issues regarding integrating the SATA drivers with XPCREATE. I have fixed all known bugs as of 3 March 2004, and attached to this post is the latest XPCREATE.CAB SATA Driver Informatin Database. Remember, these files only contain the information needed to associate identified hardware with driver files, you still need to provide the driver files yourself. For complete information, please refer to the XPCREATE website.

I would like to ask those who have successfully installed SATA / RAID to post here, and include the name of the hardware used (e.g. IASTOR on Motherboard, SATALink on PCI Card, etc.) Please post, even if you have already reported success (let me soak it up a bit, will ya?).

I would also like to ask those that are having problems to post here as well. If you are not using the latest version of XPCREATE (timestamped 03 MARCH 2004 in the title bar), please update. When reporting errors, please either post your XPCREATE.LOG file, or email to the address in the signature. All tests should be using the XPCREATE.CAB file attached to this post, and not that included in the download.

Drivers supported by attached XPCREATE.CAB:
(Drivers successfully installed in GREEN)
This list will updated regularly, both in terms of successfull installations, and as new drivers are added to the list. If your drivers are NOT on the list, please email your drivers to the address listed below, so I can add them. (SATA/RAID Drivers only, please.)

Well, Looks like whatever you did burned up my RAIDCore SATA Card

JK Worked Great GM, No errors here with the RAIDCore Drivers

One quick question dont figure it will but just wanted to make sure, It wont hurt anything to put all supported SATA drivers into the drivers folder instead of the current one being used will it? Thanks GM Great utility glad to say i helped perfect it Not much though

I have been able to succesfully integrate the Promise Fasttrak Family Driver Disk which is the Promise RAID controller integrated on the ASUS A7V266-E motherboard. Works like a charm

Blyster

It would be awesome if we can get all our drivers for our raid/sata posted here, with the .sy_ cab files to make the perfect disk that will work with any controller we come accross..... Never have to worry about F6 again.

Just a thought.

That's kind of the point of XPCREATE! Presently, posting drivers that would work WITHOUT XPCREATE is not in my own intererst, as I need as many people testing these drivers as possible. Once the "Master List" on the first post shows a majority of these drivers as successfully installed, I will reconsider.

Please check the first post for updates.

My XPCREATE install successfully included the drivers for the "Silicon Image SiI 3112 SATARaid Controller" integrated on my Abit NF7-S motherboard.

Matt

Hi there,

how about Promise Fasttrak HPT 378, like on the Asus P4C800 deluxe.

regards shortie

@green: You remember me using xpcreate for mass roll-out? We still do and it just works outstandingly. Anyway we can do you a favor?

Hi again,

sorry to aks that question, but.....

I downloaded the latest xpcreate.cab put it in the xpcreate folder, but what now? Where should I put my S-ATA drivers?

@green: maybe I'm stupid but your manual on your website is not clear to me

Thanks for an advice,

shortie

Hi,

forget my posting concerning the location of winnt.sif.


Stupid me!!!

Sorry,

shortie

@green: I tried that xpcreate.cab and it doesn't work. The RAID 0 is not detected.

Regards, shortie

@GM the cab file you posted this afternoon somehow reverted back to a lot of the oem files having the _3 instead of the _4 in them.

Blyster


edit: New cab file uploaded by GM, disregard message now

Hi green, hi all!!

Finally good news!!! It works!!

@green: you may update the list. The S-ATA controller on the ASUS P4C800-deluxe which is a Promise FastTrak 378 (not a TX4000, which has different vendor IDs) works with the lastest xpcreate.cab posted by green!!

Thanks you very much, it is a deep pleasure knowing that somebody and some other as well, work hard to make this thing work!!! better and better.

@green: If I got the time I will post what I actually did with xpcreate, in order to use it for a mass-rollout.

Regards, shortie

I had some minor issues with the RAID integration on the latest pass.

The documentation:
http://greenmachine.msfnhosting.com/XPCREATE/raid.htm

makes no mention that you need to have a directory $OEM$\$1\Drivers for this to work. Since my drivers are in $OEM$\$$\PnP, it just kept skipping integration and I couldn't figure out what was going on until I saw this in the code:

IF NOT EXIST FILESCD\$OEM$\$1\DRIVERS\ GOTO EOF

Since the driver search is on $OEM$\*.SYS, it makes no sense to have this $1\Drivers constraint.

Can it be removed in the next update?

Thanks

Welcome back, jcm! I had to stick a bug in to hear from you?!

Well ... " ... it makes no sense to have this $1\Drivers constraint. ... " is a bit strong. There is a bug in the logic, that is true, but the constraint is to allow SATA drivers to be present, without triggering integration. I mentioned that in THIS post.

Still, you are right in that it is not a pretty solution. I will change the logic to use the "$OEM$\$1\DRIVERS" value as default for driver placement, and allow userspecific values in the XPCREATE.INI file. How does that sound?

For the record ... which controller and motherboard did you get it to work on?

I'm happy to report a successful installation on a Silicon Image Ultra-133 RAID controller on a VIA P4X266 motherboard.

I'd like to add some info to the pool:

Make sure your drivers are in a folder created under \$OEM$\$1\Drivers\006\ (006 is an arbitrary number as far as I can tell)

Add the following code to your WINNT.sif file:



That should do it. Make sure your xpreate.ini file is right and run it.

My first post ever. I think I did pretty well.

Thanks for the input, jamhead. Welcome to MSFN, and the world of on line posting. You done good!

The 006 folder name is not quite random, but that is another story ...

I'll be updating the list on the first post once I get some software installed on this new installation I'm using, but that often takes me time: Hate to spoil a perfectly good installation!

I tried to install xp after I made the cd no go with the raid. Im using a Promise FastTrak TX2000 RAID pci card. Your software is awesome. Eric the tech over at www.tcwo.com swears by your software and I as well. Awesome job.

This is great software. Thanks so much for your help. I was finaly able to put my floppy drive to rest. Thanks

Well, I'm back from a little vacation and hadn't had a chance to look at the updates since full RAID integration was added. It's very smooth.

>Well ... " ... it makes no sense to have this $1\Drivers constraint. ... " is a bit
>strong. There is a bug in the logic, that is true, but the constraint is to allow
>SATA drivers to be present, without triggering integration. I mentioned that in
>THIS post.
>
>Still, you are right in that it is not a pretty solution. I will change the logic to use
>the "$OEM$\$1\DRIVERS" value as default for driver placement, and allow
>userspecific values in the XPCREATE.INI file. How does that sound?

I think you'd be better off just explicitly having your DOSATA=Y flag in the configuration file, then keeping your search as is. That makes it clearer, rather than have integration dependent on the (non-)existance of a directory. You'll never be sure where I want to keep these drivers and I may need to have them in a couple paths.

>For the record ... which controller and motherboard did you get it to work on?

Just rebuild on my home box, the Intel SATA RAID on the 865, after FBRing some file associations.

i was also successful loading the Silicon Image Si3112 SATA Raid controller that is integrated into the Epox 8RDA3+ motherboard. i was also successful on another epox motherboard, but i dont remember the model number. i swear by epox mobo's and your tool works well.

hope i helped

GM - I just wanted to let you know that yesterday evening I finally got around to actually using the CD I've been working on ( had been testing it for what seems like forever in VM ), and the "HPT374 UDMA/ATA133 RAID Controller for WinXP" works excellent

I figured you could put your little ticky mark beside one more successful test.

Thanks for creating such a great tool.

Tim

@brownbag: I wasn't fshing for more praise, I was just looking to add to the list of successfull installations. (I'll take the praise, anyway I can get it!). So, what is the final word? Working or not?

On the other hand, perhaps "Eric The Tech" swears by it, but my email to the sales department there remains unanswered ....

@jcm: As always, your points are taken into consideration. For the moment, I consider the workaround to be adequate, and I am insisting on only modifying the code for "critical" flaws, of versin changes. There is, no doubt, always room for improvement. and your feedback is certainly appreciated.


@bleach622 & Tim A: Thanks for the input. I'll be adding that hardware to the success list.

I had some problems with the Adaptec 2010S but finally got it figured out. I actually had it working before using XPCREATE but after I got some help from the forum and adaptec. Since the dpti2o driver is already included on the Server 2003 CD there were already most of the entries required in the txtsetup.sif file. I only had to add to the [HardwareIdsDatabase] section. I also had to make the dpti20.sy_ file and replace the current file that was already there. The driver I needed had the same name but contained info for more devices than the driver on the Original Server 2003 CD. After initially using XPCREATE for this CD it made it through setup (1 minute left) and then rebooted. After it rebooted I got a blue screen that went by too fast for me to read. After that happened I did the following...

-Replaced DOSNET.INF with original. It already had entries for dpti20.
-Replaced dpti2o.sy_ with the new driver.
-Manually edited the txtsetup.sif file. Just added the rest of the entries to the [HardwareIdsDatabase] section.
I was wondering if the driver should also be added to driver.cab.

After all of this I have a Server 2003 CD with all of the updates that automatically installs a domain controller and configures DNS. XPCREATE seems to have no problems with Server 2003 hotfixes.

I'm having a little trouble figuring out where i am supposed to edit the OemPnPDriversPath I know its in winnt.sif but where do i put that file?

The docs for this software are pretty sketchy, someone should work on helping GM out and write a little more detailed ones.

for example the sites says...



But I read here that its actually FILESCD\$OEM$\$1\

Is that correct or no?

Actually the SATA/RAID drivers have to go into the FILESCD\$OEM$\$1\Drivers folder in order fo xpcreate to notice them and integrate them into the final cd. And as you mentioned, the OemPnPDriversPath would point to the folder containing the SATA/RAID drivers as well.

Blyster

Confirmed! the Promise FastTrak SX4000 drivers work!(for windows XP)

Has anyone been able to get the VIA SATA 3149 working? (Integrated with A7V600)

This is different (apparently) from the viaraid that's in the one already in the XPCREATE.CAB because it won't integrate it for some reason. (Unless you can only add one SATA driver into the install?) I'm trying to make a universal disk for me and my friends, all with different motherboard bios(s).

Here is the OEM file that came with the drivers and I'm trying to pick the appropriate stuff out, this just isn't exactly my forte.

#
# format for txtsetup.oem.
#
# General format:
#
# [section]
# key = value1,value2,...
#
#
# The hash ('#') introduces a comment.
# Strings with embedded spaces, commas, or hashes should be double-quoted
#


# This section lists all disks in the disk set.
#
# <description> is a descriptive name for a disk, used when
# prompting for the disk
# <tagfile> is a file whose presence allows setup to recognize
# that the disk is inserted.
# <directory> is where the files are located on the disk.
#

[Disks]
d1 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \winxp
d2 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \win2000
d3 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \winnt40
d4 = "VIA Serial ATA RAID Controller Driver ", \VT8237, \2003ia32


# This section lists the default selection for each 'required'
# hardware component. If a line is not present for a component,
# the default defaults to the first item in the [<component_name>]
# section (see below).
#
# <component_name> is one of computer, display, keyboard, mouse, scsi
# <id> is a unique <within the component> string to be associated
# with an option.

[Defaults]

scsi = VIARAID_VT3149_XP



# This section lists the options available for a particular component.
#
# <id> is the unique string for the option
# <description> is a text string, presented to the user in a menu
# <key_name> gives the name of the key to be created for the component in
# HKEY_LOCAL_MACHINE\ControlSet001\Services

[scsi]
VIARAID_VT3149_2003IA32 = "VIA Serial ATA RAID Controller(Windows 2003 IA32)",VT8237
VIARAID_VT3149_XP = "VIA Serial ATA RAID Controller(Windows XP)",VT8237
VIARAID_VT3149_2K = "VIA Serial ATA RAID Controller(Windows 2000)",VT8237
VIARAID_VT3149_NT = "VIA Serial ATA RAID Controller(Windows NT4)",VT8237


# This section lists the files that should be copied if the user
# selects a particular component option.
#
# <file_type> is one of driver, port, class, dll, hal, inf, or detect.
# See below.
# <source_disk> identifies where the file is to be copied from, and must
# match en entry in the [Disks] section.
# <filename> is the name of the file. This will be appended to the
# directory specified for the disk in the [Disks] section to form the
# full path of the file on the disk.
#=======================================#
[Files.scsi.VIARAID_VT3149_2003IA32]
driver = d4, viasraid.sys, viasraid
inf = d4, viasraid.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d4, viasraid.cat

[Files.scsi.VIARAID_VT3149_XP]
driver = d1, viasraid.sys, viasraid
#dll = d1, setupvia.dll
inf = d1, viasraid.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d1, viasraid.cat

[Files.scsi.VIARAID_VT3149_2K]
driver = d2, viasraid.sys, viasraid
#dll = d2, setupvia.dll
inf = d2, viasraid.inf
## Cat file directive. It should be marked with non-digital signed driver
catalog = d2, viasraid.cat

[Files.scsi.VIARAID_VT3149_NT]
driver = d3, viasraid.sys, viasraid
inf = d3, viasraid.inf

[HardwareIds.scsi.VIARAID_VT3149_2003IA32]
id = "PCI\VEN_1106&DEV_3149","viasraid"

[HardwareIds.scsi.VIARAID_VT3149_XP]
id = "PCI\VEN_1106&DEV_3149","viasraid"

[HardwareIds.scsi.VIARAID_VT3149_2K]
id = "PCI\VEN_1106&DEV_3149","viasraid"



# This section specifies values to be set in the registry for
# particular component options. Required values in the services\xxx
# key are created automatically -- use this section to specify additional
# keys to be created in services\xxx and values in services\xxx and
# services\xxx\yyy.
#
# <key_name> is relative to the services node for this device.
# If it is empty, then it refers to the services node.
# If specified, the key is created first.
# <value_name> specifies the value to be set within the key
# <value_type> is a string like REG_DWORD. See below.
# <value> specifies the actual value; its format depends on <value_type>

[Config.VT6420]

value = "", Tag, REG_DWORD, 1
#HP-Delete following line
#value = "Parameters\PnpInterface", 5, REG_DWORD, 1

I do believe it is included in the attached XPCREATE.CAB file. Perhaps it was you that sent it to me?

I don't think there has been a "failure" yet in this thread ... no reason to start now.

As for a generic CD that has all the drivers, the biggest risk would be in conflicts. One example is both the FASTTRAK and ULTRA drivers use hardware with the same PnPID (e.g. "PCI\VEN_1106&DEV_3149"). Another example would be drivers that are simply incompatible. However, I'm sure you can get at least "most" of them in if you work at it.

Fantastic. No, it wasn't me that sent it to you, but that new .CAB file definitely made it recognize the drivers that I put in my $OEM$ path.

I probably should have used a CD-RW for the first one, but I really thought it would work. Unfortunately, I made a XP Pro VM with VMWare and used my CD and it worked just fine... I guess it didn't need the SATA drivers.

Now I'm working on a TXTSETUP.INF issue (can't find it correctly for some reason and it's probably me just being an engineer and not reading everything to the last letter ) and I'll be 100% happy. I'm just 99.5% happy now.

has anyone tried the Silicon Image SiI 3112 SATARaid Controller on the abit nf7-s 2.0, not version 1, have they tried it with using raid, i dont want to mess my computer up as i am going to have to format in a few days and want to create a sp2 rc1 integrated that will last me until the final version is out in the summer.

No luck with my Promise s150 TX4. This is on an IwillDPI533. Everything works fine if I use my driver floppy, so I know the hardware side is ok.

I'm using the latest XP Create I could find from your website.

This looks strange, since it appears to be doing everything one would expect. I find a fasttx2k.sy_ in the /386 directory, and I find the added stuff in txtsetup.sif and my winnt.sif has the paths looking correct, at least to me:

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
TargetPath=\WINDOWS
Repartition=Yes
UnattendSwitch="Yes"
WaitForReboot="No"
DriverSigningPolicy=Ignore
OemPnPDriversPath="drivers\fast_trak;drivers\intel_chipset;drivers\ethernet;drivers\canon_gl2;drivers\intel_app_accel;drivers\sound_card;drivers\video_card"

The drivers are in "drivers\fast_trak" The "drivers" directory is right under $OEM$\$1

Everything else seems to work correctly. When I use this build in my VMware virtual computer, it does an unattended install with all my apps and regtweaks, etc., so I think that is all correct. Of course I can't test the drivers in VMware (That I know if) so I have to burn a DVD to try this out.

The error I get is that after windows setup starts, it goes through a process of copying files and then I get to a screen that says setup can't find a hard drive to install to.

After I little digging, I discovered a few differences in the txtsetup.sif from what I would think, if that is supposed to match what I find in the INF file for my driver. However, I am not an expert, and hesitate to mess with this before I get an opinion from the group.

in txtseup.sif I find

[HardwareIdsDatabase]
PCI\VEN_1103&DEV_0005 = "fasttx2k"
PCI\VEN_1103&DEV_0004 = "fasttx2k"
PCI\VEN_105A&DEV_3376 = "fasttx2k"

but in my fasttx2k.inf I find

PCI\VEN_105A&DEV_6629.DeviceDesc="WinXP Promise FastTrak TX4000 ™ Controller"
PCI\VEN_105A&DEV_3371.DeviceDesc="WinXP Promise FastTrak S150 TX2plus ™ Controller"
PCI\VEN_105A&DEV_3319.DeviceDesc="WinXP Promise FastTrak S150 TX4 ™ Controller"

Shouldn't the Hardware ID's match? Like I said, I am not an expert on this, so just tell me if I am totally wrong.

I'm going to look around the rest of the forums and see what people find.

--jn

@MajikUF: Told you we'd get it ... The TXTSETUP.SIF not found problem seems like a CDIMAGE switches issue, such as an UPPER/lower case issue. XPCREATE UPPERS all Windows XP file names.

@hajj_3: The SI 3112 has been sucessfully installed many times. You can make a CD, and start the installation. When you see the Drive Selection, you will know if the drivers have been recognized or not. Be sure you do not "Autopartition", and there is not risk involved.

@jjn1056: You do need a PnPID match (e.g. PCI\VEN_1103&DEV_0005). No need to look further ... and I don't think you will be the first failure in this thread. Please email me your drivers (email address in signature image), and we'll get you going.

So much for a quiet Sunday evening ...

@ jjn1056 - those "PCI\VEN_1103&DEV_0005" lines and the like, they are the plug n play IDs (PnPIDs as GM puts it). Every hardware device has one of these IDs and when it is detected, windows then searches for a driver with a matching PnPID, if none is found it then asks you to insert the driver disk provided by the manufacturer. The PnPIDs in your driver files not matching the ones inside the cab file explain perfectly why the XP setup CD does not recognize your hardware device: there is no driver in the database that has a PnPID that matches the PnPID of your promise hardware device...you will need to send GM your *.oem files from your driver disk, so that he can add your hardware to the database, just as GM said. hope i cleared it up a little bit or helped you to understand this a little bit better...

Wow, I've really learned a lot on this project! Creating this unattended install disk has made me feel like I am in control of Windows for the first time

I always wondered about how the PnP driver stuff worked, but I've always been into application software development, I've stayed away from hardware for the most part. So, yes, what was said above taught me something.

I think I still will wait for GM to take a look at the driver files I sent, and not mess around with is. I've been told that since vendors will sometimes take conflicting hardware ID's it's possible to damage your hardware by trying to force install a driver onto the wrong device. I'm not sure if that is true or an old wives tale, but since I am living in a remote location right now I don't want to chance it!

GM, you got mail.

Peace, jn

GREENMACHINE, how would i go about installing the sata drviers to automatically set it up as a raid configuration, prefer not to do it manually.

anybody know ?

installing the wrong drivers will NOT in any way shape or form damage your hardware...this actually is a frequent problem in windows...drivers will actually get associated with the wrong PnPID somehow and the wrong drivers will install, this is very hard to fix - its actually easier and usualy faster to just reinstall windows (if reinstalling the driver wont fix it), because windows will keep looking at the wrong driver and the hardware wont function properly anymore. now that i think about it, i could see how this would lead one to believe that the hardware was damaged by installing the wrong driver...

Update on that Promise s150 TX4. The file I was emailed worked, and I was able to install windows properly! Thanks a lot for your help, and you can add my controller to the list of ones that work.

Now I have to figure out the problems in a couple of other drivers, but that is for a different forum!

Peace, JN

Good deal! You are quite welcome.

You guys should know by now I don't take no for an answer ...

hey if you have issues with your other drivers....i may be having the same issues. i added my video drivers (nvidia) extracted folder contents to the <filescd> folder. it looks like some of my files we recompressed that were in this folder. because some of the extensions of the files were *.sy_ istead of *.sys. and i was wondering why the display driver wasnt updated (and yes i had the driversigning=ignore option in the winnt.sif file added in there). so i tried to manually update the display driver and when i did it asked for a file and i pointed it to the directory c:\drivers\00x_video\*.* folder and it kept asking for a file that was there(but the extension was *.sy_ instead of *.sys) and it wasnt working so i redownloaded the files from the nvidia site again(without canceling the "new hardware found" whizard and pointed it to the default nvidia driver folder c:\nvidia and it found all files and sucessfully installed the driver. so i think XPCREATE it recompressing driver files found in the <filescd>\drivers folder and then copying to the final ISO.

just a thought.....is it doing the same for you?

You kiddin'? That's extra work! It's just an XCOPY ...

let me look into this....i think ill start looking at your batch code before i post

Just to confirm (and I don't think it was) but the VIA VT8237 SATA RAID controller works fine with XPCREATE.

Can edit this post and place the directory structure if needed...but I'm sure it isnt.

The only change I made to the driver was to strip the unneeded OS drivers from the file/dir i.e. Win98, ME, NT, etc.

Regards,
N.

Basics of my system:
Chaintech Znf3-250 754skt mobo
Silicon Image SiI 3114 SATARaid Controller
AMD Athlon64 3200+
WD 36GB x2 HDD
(If you want to know anything more, just ask.)

Hello everyone,

Sounds like this is great software that will be very convenient once XP is installed. However right now I'm trying to reinstall from scratch and I'm having problems with my raid controller. I was running windows a few months ago, (and didn't have this much trouble installing XP) then I switched to Linux. Great OS, however I didn't know it and had a hard time finding the right info on what I was running, so now I'm back to XP.

After some searching I found some RAID drivers (Silicon 3114 Raid driver V0.0.0.4 For 9x/Me/2k/XP from the Chaintech website. www.chaintechusa.com/tw/eng/Download/dl_LI.asp?DISNo=416 ) that got me through the first start installation screen. During the windows installation I received a message that said my RAID drivers were not digitally signed (or however they phrase it.) I stopped the install and decided to come looking for more info.

I'm wondering how I can use your software before windows is installed. I don't want to connect my computer to the Internet until after I install SP2. If you could help me with specific instructions on using your software during the XP install process or if you could just point me to digitally signed drivers it would be greatly appreciated.

Thanks for being here and good luck with your ventures.

Aaron

Hi dude,

glad it worked for you - could you post the solution ?

Welcome to MSFN, Nicepen!

I have not had any time latley to add new SATA/RAID drivers to the collection. Hopefully I will in January ...

hi don 379 fast track raid msi ms-6565 board works ok too

I hope that it is OK to bump this topic! I need help with my SATA150 TX4 PCI Card. I need to include the drivers with my XP SP2 disk. I am having difficulty incorporating the correct lines in my TXTSETUP.SIF file. I really need someone to help please!
I hope that I am in the right place here, please move this if it is not correct, thanks!

I understand this is an OLD topic, but I have something new to ask. I'm using one of bashrat's driver packs for sata, but it looks like all the .sys files are still in the .sy_ format. XPCREATE checks for the existence of .sys files in order to integrate SATA. Would I be ok renaming these to .sys or is there something I need to do for these to integrate correctly?

Edit: actually, it looks like in the driverpack itself they are .sys, but once I run his batch files to integrate into the disc it sets them to .sy_ I guess I can just rename them then, but I'll look into why it's renaming them in the first place.

They're being CABbed... You'll have to decompress them.