MSFN Forums > TEXTMODE MassStorageDrivers Method

Full Version: TEXTMODE MassStorageDrivers Method

MSFN Forums > Unattended Windows Discussion & Support > Device Drivers

Pages: 1, 2, 3

trainee

May 26 2004, 03:58 AM

RASOR IS CURRENTLY *NOT* AVAILABLE (NO ETA SET)
I have written a utility called RASOR that is able to slipstream drivers with this method. It can be found: HERE.

UPDATE: 10/15/2004

Guide updated to reflect new research from members, especially rcordorica
Known working list added
Previous update notices removed

KNOWN WORKING LIST:

3ware 7k/8k Driver
Silicon Image 3112r Driver

PREAMBLE
First, if there has already been a big post on this then I'm sorry for making another one. Second, I tend to have *very* verbose posts, so I will try to keep this short.
Disclaimer: I only claim that this will work for my hardware setup but I am posting this in the hopes that someone else can get theirs to work as well. I will try to help where I can, but I'm no expert.

INTRO
I have a complete (for all intents and purposes) XP PRO slipstream via XPCREATE *with* 3ware Raid 7k/8k drivers installed via the $OEM$\TEXTMODE Method; aka Method 2. From here on I'm calling this M2 because I'm tired of typing it out so much. I have tried the txtsetup aka Raskren's aka GM's aka RyanVM aka M1 method but was never able to get the 3ware drivers to load properly with that. It doesn't seem like too many people are running 3ware Raid cards, but if you are then *this* IS the method you should use. This should not be confused with the similar but more complex method outlined by Pure Krome (which I have not tried, but I do believe works) as listed here.

SETUP
I am using a XPCD slipstreamed with SP2, WMP10, Journal Viewer, .NET framework w/ SP1

THE PART YOU CARE ABOUT: EDITING DRIVER FILES
So how do you use M2 to get your raid drivers on the CD? There have been a lot of posts about this as well as the somewhat erroneous information provided in deploy.chm (part of the MS SP1/SP2 deployment pack). I will assume you have your driver files (the equivalent of a floppy driver disk). A driver file-list *might* look like this (where driver is some relevant driver name):

txtsetup.oem (this file sets the driver up for textmode)
driver.inf (may also be named something like oeminstall.inf)
driver.sys (1+ driver files)
driver.cat (WHQL signing)
driver.cpl (control panel file)
driver.dll/.exe/.vxd (other libraries/executables for your driver)
disk1 (a weird disk file may or may not be included; possibly plaintext)
readme (of some sort)

Many driver packages will NOT include .cpl, .dll, .exe, or .vxd files. There is nothing missing and this will usually make your install even easier to deal with. *IF* however you do have any of these files you *may* need to edit your txtsetup.oem file. Once again this is only for people who have files other than .inf, .cat, .sys and .oem in their driver packages. Okay you need to open up your txtsetup.oem file (notepad or any text editor will do) and change any reference to "DLL = " to "INF = " (thanks to rcordorica for figuring this out). For some reason textsetup chokes on these entries. These entries should be easy to find and replace in the file. Save the modified file and close it. Again if you don't have any "DLL = " references in your txtsetup.oem then you don't need to change anything and you read this entire section of the guide for nothing

.

THE PART YOU CARE ABOUT: COPYING DRIVER FILES
Now you are ready to copy the driver files to the proper locations. You *can* strip the disk1 type files and the readme however I usually copy them for good measure. I also do not compress any of the sys files, although you *probably* could. So I choose to copy ALL of the driver files to these 2 directories:

$OEM$\TEXTMODE\
I386\$OEM$\

If you have .cpl, .dll, .exe, .vxd files you need to copy these to a third location (A really big thank you goes to rcordorica for his tireless work figuring this out). Copy these additional files to:

$OEM$\$$\OemDir\

THE PART YOU CARE ABOUT: EDITING WINNT.SIF
Now 2 things need to be added to winnt.sif (if you don't know what that is, you really shouldn't have gotten this far in the post).

A new [MassStorageDrivers] heading with 2+ entries (New Controller & CD-ROM Driver)
A new heading [OEMBootFiles] which will list all of the files from the new driver

This is best illustrated with my own winnt.sif (the whole of which is presented here)

CODE

;SetupMgrTag
[Data]
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
DriverSigningPolicy=Ignore
Repartition=Yes
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
UnattendSwitch="Yes"
WaitForReboot="No"
TargetPath=\WINDOWS

[GuiUnattended]
AdminPassword=XXXXX
EncryptedAdminPassword=Yes
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="Trainee"
OrgName="Thunderwalker"
ComputerName=XXXXX

[Identification]
JoinWorkgroup=XXXXX

[Networking]
InstallDefaultComponents=Yes

[MassStorageDrivers]
"3ware Escalade 7000/8000 Series ATA RAID Controller" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]
TXTSETUP.OEM
oemsetup.inf
3waregsm.cat
3WDRV100.SYS
3WFLTDRV.SYS

For the [MassStorageDrivers] entry I have been told that the listing must *exactly* match the description in txtsetup.oem. I have not confirmed this but I opened up txtsetup.oem and copied the description out of it, it should be very easy to find under the [SCSI] heading. I am 99% sure you must also list the IDE controller for your CD drive. If you don't, I don't believe that the setup can continue after the first reboot. I do not know if order matters, however I chose to list my RAID controller first followed by my IDE cd-rom controller. Anyone who has an IDE cd/dvd drive can pretty much just copy my line. The new controller should be listed as "OEM" as in look around in OEM to find the drivers. Any other controller (like the cd-rom) that use already built-in drivers should be listed as "RETAIL" as in included with the retail cd.
Now the [OEMBootFiles] listings are basically the files from your driver disk. I do not know if order is important, but I chose to list the txtsetup.oem first, followed by any .inf, .cat, .sys and so on. I do not list the readme, or the crazy Disk1 type files.

COMMON MISTAKES/MISCONCEPTIONS

A number of posts list the TEXTMODE directory incorrectly as TXTMODE
Deploy.chm states that if a txtsetup.oem file does not contain the HardwareID (as listed in the .inf) that it must be added. I know for a fact that this is WRONG. I screwed up my own install many times trying to add this to my txtsetup.oem. The 3ware txtsetup.oem does not have the hardwareID and installs perfectly.
Make sure to list both your new controller AND your cd-rom controller under [MassStorageDrivers]
There have been claims that ntfs won't read the /'s and all /'s must be changed to .'s and visa versa. IMHO: WTF.
In most cases you shouldn't have to alter any of the driver files including txtsetup.oem (see next point).
If your txtsetup.oem file contains "DLL =" entries (without the quotes), you will need to change them to "INF =" to get around a textmode parsing error (thanks rcordorica).

NOW YOU TRY IT
While this post is very long, I think you will agree that this is a fairly simple method to add drivers to your slipstreamed XP CD *IF* it works. Right now the only drivers known to work are the 3ware 7k/8k drivers and the Silicon Image 3112Raid driver. Unfortunately I don't have the hardware to test any other drivers right now. If you have any questions please ask them here, or PM me and I will do my best to answer them.

ERRATA
I'm including links to the 3ware txtsetup.oem and oemsetup.inf for reference, however neither of these files were altered (note that these were changed to .txt files so they aren't a pain to open).

<--me, because I talk and talk and talk until even I'm bored!

Bâshrat the Sneaky

May 26 2004, 06:26 AM

Interesting post!

One remark, in fact an addition:

QUOTE (trainee)

driver.cat (I believe this is the PnP information)

I'm quite sure this is the WHQL license.

Further no remarks! Nice guide!

edmoncu

May 26 2004, 06:36 AM

hmm, interesting. this has been a long time stumper... i suppose, this guide will enlighten us further hopes that this method is still highly usable.

GreenMachine

May 26 2004, 05:52 PM

I wish I could do that ...

Before deciding to use the simplified raskren method, I attempted to get the [MassStorageDevices] with no luck. I do like that it does not require TXTSETUP.SIF modification, though the way it is done is still very clean (tacking on the OEM info at the end, but you know that ... ) As soon as I get some time, I may have to have another look at this.

Still, the XPCREATE way seems to work fine for for nearly everyone. The few that don't go off and post elsewhere ...

Nice job! Thanks!

trainee

May 26 2004, 06:41 PM

Thanks for the comments guys! I'm sure it will take a while for people to actually try the method out on different hardware setups, since it involves formatting their hard drive(s).

@Bashrat: Thanks for the .cat clarification. And I've been meaning to say: cool avatar.

@edmoncu: yeah I saw that you've been looking at this method for well over a year now.

@GM: XPCREATE is awesome! Unfortunately the 3ware drivers aren't digitally signed which I believe is a prerequisite for their inclusion with XPCREATE. I kept trying to integrate them at a lot of different points with XPCREATE (before, after, and I even tried hacking the xpcreate.cab to put the 3ware drivers in) but no dice. I was afraid of messing up the changes that XPCREATE makes to TXTSETUP.SIF, and ultimately I was unable to make M1 work. I agree that your simplified Raskren method is clean as well (and involves fewer copies of the driver files!), I just couldn't make it work (please see additional errata below). I absolutely think that having XPCREATE detect and add the drivers is the best way to go so any chance you want to add the 3ware's to it?

Additional Errata:
I think one of the weird things about the 3ware drivers is that there are 2 drivers, but only 1 PCI/VEN ID #. I know that some drivers associate with multiple PCI ID's, but I don't know of another example where a single PCI ID associates with multiple drivers. This left me kind of dumbstruck when it came to editing the TXTSETUP.SIF. Anyone else come across a similar situation?

I'm hopeful that someone will be able to confirm M2 with another driver just so the option exists.

GreenMachine

Jun 2 2004, 04:19 PM

Ah, now I remember the 3ware drivers. I did not include them, in part for the fact that, as you mention, there are two .sys file for one piece of hardware, and also because the file names did not fit in with my "conventions". There are other drivers that also list two .sys file, but not many. I am at a great disadvantage with neither hardware nor time to test these different configurations. But like I said, XPCREATE does work for the majority. Next time I pass through the SATA integration code, I'll see what I can come up with, but that is not for the near future.

Bilou_Gateux

Jun 4 2004, 12:55 AM

Windows 2000 Unattended install of mass storage drivers for HP/Compaq ProLiant Servers with SmartStart Scripting Toolkit:

uses a single TXTSETUP.OEM
sample WINNT.SIF sections for all Mass Storage Drivers supported by ProLiant Servers
cat files are not added to OEMBootFiles section when using this method to install Mass Storage Drivers.
The Windows setup program don't check Digital Signature during textmode part of install.

CODE

[MassStorageDrivers]
    "Adaptec Ultra160 Family Manager Set"=OEM
    "Smart Array 5300 Controller"=OEM
    "Smart Array 5i, 532, 5312 Controllers"=OEM
    "Smart Array 6i, 641, 642, 6400 EM, 6400 Controllers"=OEM
    "Compaq Smart Array Controllers"=OEM
    "Integrated Ultra ATA-100 Dual Channel Controller (Windows 2000)"=OEM
    "Integrated Ultra ATA-100 IDE RAID Controller (Windows 2000)"=OEM
    "LSI Logic Ultra320 1020/1030 Driver (Windows 2000)"=OEM
    "Carte h“te SCSI PCI Symbios Logic C8100"=RETAIL
    "Carte h“te SCSI PCI Symbios Logic C896"=RETAIL
    "Carte h“te SCSI PCI Symbios Logic C8xx"=RETAIL
    "CD-ROM IDE (ATAPI 1.2)/Contr“leur IDE PCI"=RETAIL
    "CSB-6 Ultra ATA-100 IDE RAID Controller (Windows 2000)"=OEM
[OEMBootFiles]
    ADPU160M.SYS
    CPQARRY2.SYS
    CPQCISSM.SYS
    MegaIDE.sys
    Symmpi.sys
    LsiCsb6.sys
    TXTSETUP.OEM

@BTS
Obtaining Digital Signatures for Windows Drivers
Driver Signing uses the existing Digital Signature cryptographic technology to store identifying information in a catalog file (*.cat, or CAT file). CAT files are stored in <Windir>\Catroot. This information identifies the driver as having passed testing by Windows Hardware Quality Labs (WHQL). No change is made to the driver binary itself. Instead, a CAT file is created for each driver package and the CAT file is signed with a Microsoft digital signature. The relationship between the driver package and its CAT file is referenced in the driver's INF file, and is maintained by the computer after the driver is installed.

INF File Changes
The digital signature is stored in a CAT file. The following modifications to INF files are required for IHVs/ISVs who want to obtain digital signature for their drivers:
In the [Version] section of the INF, the entry CatalogFile=<filename.cat> is added.
An entry for the CAT file in the [SourceDisksFiles] section is added. For example, an IHV submits a driver package to a WHQL that includes files named Sample.inf, Sample.drv, and Sample.txt.
If the package passes WHQL testing, WHQL will return the original Sample.inf, Sample.drv and Sample.txt with the addition of Sample.cat.

murk

Jul 8 2004, 02:13 PM

I'll try it next week with Silicon Image 3112r drivers.

my2001

Jul 9 2004, 02:41 AM

(removed)

Inferno

Jul 13 2004, 06:59 PM

@trainee: Are you using this method for a network install of the OS or a CD install? I asked because I have been successful using this method in the network installs at work (Windows 2003), but have not had success with a CD install of Windows XP at home. When I try to do a CD install I receive the following error:

File txtsetup.oem caused an unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c

Just to be thorough, here is my txtsetup.oem file:

[Disks]
d1 = "HPT3xx ATA RAID Controller Driver Diskette",\Disk1,\

[Defaults]
scsi = hpt3xx

[scsi]
hpt3xx = "HighPoint HPT3xx ATA RAID Controller",hpt3xx

[Files.scsi.hpt3xx]
driver = d1, hpt3xx.sys, hpt3xx
driver = d1, hptpro.sys, hpt3xx
inf = d1, hpt3xx.inf, hpt3xx
catalog= d1, hpt3xx.cat

[Config.scsi.hpt3xx]
value = "", Tag, REG_DWORD, 1
value = "Parameters\PnpInterface", 5, REG_DWORD, 1

[HardwareIds.scsi.hpt3xxXP]
id = "PCI\VEN_1103&DEV_0005","hpt3xx"
id = "PCI\VEN_1103&DEV_0004","hpt3xx"
id = "PCI\VEN_1103&DEV_0006","hpt3xx"

And, a portion of my winnt.sif:

[MassStorageDrivers]
"HighPoint HPT3xx ATA RAID Controller" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OEMBootFiles]
TXTSETUP.OEM
hpt3xx.sys
hptpro.sys
hpt3xx.inf
hpt3xx.cat
Disk1

I decided against posting the hpt3xx.inf file as I did not make any changes to it and it is rather large.

trainee

Jul 13 2004, 10:03 PM

@Inferno: see if this thread helps (link)

@Inferno: yes I have been successful using this method from CD. However very few people seem to have confirmed with their own hardware, so if you are up to it, lets try to get yours to work. And welcome to MSFN, I'm surprised your name wasn't taken!

First, the txtsetup.oem and your additions to the winnt.sif appear to be fine. You shouldn't need to post the .inf file however the following information / tips would be helpful:

When posting code / codelike files, please put them in [CODE] tags because it is much easier to read
If possible please post your entire winnt.sif (with personal stuff like product ID removed) because some of the other entries may be relevant
What is the exact hardware you are trying to install?
Where do you get the error? (ex. before drive format, after drive format, after first reboot, during file copy, etc)
What does your Disk1 file contain?

Okay, here is the weird thing about your error: the filename does not appear to be associated with the driver. The file "oemdisk.c" is not listed in your txtsetup.oem or winnt.sif oembootfiles. So I don't understand how these would be related.

So have you..

Compared your install to the one described in the guide?
Copied the driver files to ALL the locations described in the guide?
Tried NOT listing Disk1 in your [oembootfiles] entry?
Ensured that your CD isn't 'FULL'? I know this sounds stupid, but I was using 650mb CD-RWs and I couldn’t figure out for about half a day why I kept getting random errors. I never had a write error, but I had crazy error 18's and file read errors for hours, until I switched to 700mb CD-R's. (no comments from the n-lite crowd please)
tried installing with virtualpc from the CD image? You can try a failsafe this way too, without the driver files, to make sure it isn't something with the rest of the CD that is causing the problem and not the textmode driver.

I believe that a error (18) is a file not found error (but don't take my word for it). I also am not an expert on slipstreamed CD's but I use XPCREATE and the path you have listed is very different from anything I appear to have.

Hope this helps. If you tell me the exact driver I can try to replicate your problems with my slipstreamed CD in virtualpc.

Maelstorm

Aug 8 2004, 01:12 AM

QUOTE (Inferno @ Jul 13 2004, 06:59 PM)

File txtsetup.oem caused an unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c

Just to be thorough, here is my txtsetup.oem file:

[Disks]
d1 = "HPT3xx ATA RAID Controller Driver Diskette",\Disk1,\

I decided against posting the hpt3xx.inf file as I did not make any changes to it and it is rather large.

The problem is the d1 line. I'll bet that the directory \Disk1 does not exist on your CD? I'm not sure what that last field is for, but here's the line from my TEXTINFO.OEM file for my SCSI controller:

CODE

d1 = "SIIG AP-20/AP-40 SCSI Pro Windows XP MINIPORT DRIVERS",winxp\sc247xu.sys,winxp

In my $OEM$\TEXTMODE directory, I do have a WinXP directory. Note there is no leading backslash. I'm still working on getting my hardware to work, and this will be the first time that I try method 2. Method 1 flat refused to work.

trainee

Aug 8 2004, 02:08 AM

QUOTE (Maelstorm @ Aug 8 2004, 12:12 AM)

CODE

d1 = "SIIG AP-20/AP-40 SCSI Pro Windows XP MINIPORT DRIVERS",winxp\sc247xu.sys,winxp

@Maelstorm: I'm still around to help people try to make this method work, but in general I need some more info to go on that you have supplied in your previous post. What card do you have exactly? Just looking at the D1 line you quote it appears that you have either a SIIG AP-20 or AP-40 Ultra Wide Scsi controller card. Soooo.... I went over to the SIIG site to download the drivers myself. I'm guessing you have harware revision #2 with the acard chipset since hardware revision #1 already has its drivers built into winXP. I also assume that you have tried this with a floppy and everything was A-OK so you know the driver works. One of the craziest problems I ever had was when my driver download became corrupted and I didn't figure it out for hours. And again another assumption: your unattended XP cd actually does work.

Okay I don't see anything terrible awry with the TXTSETUP.OEM file but if you could tell me more about where the error occurs and what the exact error you encounter is that would be helpful. Believe it or not the wierd D1\Disk1\etc entries have yet to be the problem in the ohhhhh... two whole cases I've dealt with, but still.

I am going to go ahead and slipstream-up a set of the AP-40 using M2 and see where I can get in Virtualpc. I can't vouch for them actually working with the hardware, but I will be able to see if the TXTSETUP.OEM parses out correctly. I'll post my results ASAP, but like I said any additional information would help us both get this working for you.

trainee

Aug 8 2004, 03:36 PM

@Maelstorm:

Okay as far as i can tell windows doesn't have any problems parsing the TXTSETUP.OEM file with virtualpc. Even though it doesn't simulate the hardware, an XP install on virtualpc will choke if it doesn't like the file or can't find a file referenced from it (I know from experience) I have included the changes I made below for you (using M2)

Note: CDROOT\ indicates the root of you CD... so if your CD drive was D:\ then CDROOT\ would correspond to D:\ after you have created the cd.

I downloaded the driver zip from the SIIG website and unzipped it. There is a TXTSETUP.OEM file and a lot of subfolders. Since this is going to be an XP install (it is right?) we only need the TXTSETUP.OEM file and the WinXP directory. I copy the file and the whole directory to 2 locations.

CODE

CDROOT\$OEM$\TEXTMODE\TXTSETUP.OEM
CDROOT\$OEM$\TEXTMODE\WinXP\* <the entire folder resides inside the TEXTMODE folder>
CDROOT\I386\$OEM$\TXTSETUP.OEM
CDROOT\I386\$OEM$\WinXP\* <again the entire folder is copied>

Now a few additions need to happen in your winnt.sif:

CODE

[MassStorageDrivers]
"SIIG AP-20/AP-40 SCSI Pro Windows XP MINIPORT DRIVER" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
TXTSETUP.OEM
WinXP\Sc247xu.inf
WinXP\SC247XU.SYS

See how the [OemBootFiles] entry references the subdirectory?
this is actually one of the most basic TXTSETUP.OEM files I have seen (it only reference 2 files!) so I have high hopes that this will work for you.

Below is my entire winnt.sif (with personal information x'd out of course) so that you can see all of the options I have set. I am pretty sure that you must have OemPreinstall=Yes for this method to work. Just use this as a comparison to your own.

CODE

;SetupMgrTag
[Data]
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
DriverSigningPolicy=Ignore
Repartition=Yes
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
UnattendSwitch="Yes"
WaitForReboot="No"
TargetPath=\WINDOWS
OemPnPDriversPath="Sources\System\Microsoft;Sources\System\ATI\Driver"

[GuiUnattended]
AdminPassword=xxxxxxxx
EncryptedAdminPassword=No
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1
AutoLogon=Yes
AutoLogonCount=1

[UserData]
ProductKey=xxxxxxxx
FullName="xxxxxxxx"
OrgName="xxxxxxxx"
ComputerName=xxxxxxxx

[Identification]
JoinWorkgroup=xxxxxxxx

[Networking]
InstallDefaultComponents=Yes

[MassStorageDrivers]
"SIIG AP-20/AP-40 SCSI Pro Windows XP MINIPORT DRIVER" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
TXTSETUP.OEM
WinXP\Sc247xu.inf
WinXP\SC247XU.SYS

I hope that this helps and if you have any more problems OR SUCCESS! please post back here. If you see windows formatting your harddrive then you know that it worked! So if you have a problem subsequent to formatting then the error is somewhere else.

ponzandro

Aug 12 2004, 07:20 AM

this is my first post here, and i'm really impressed by this forum.

@inferno:

QUOTE

File txtsetup.oem caused an unexpected error (18) at line 1742 in d:\xpsp1\base\boot\setup\oemdisk.c

i got a similar error some month ago while adding drivers to a Powerquest V2i Boot-CD.
What helped me out (after a long time of googling.....) was a thread from the Techguide Forum.

@trainee

i will try your method in the next days, i'm very interested in that.
For the moment i have to correct some bugs within my BartPE CD after upgrading to SP2

trainee

Aug 12 2004, 06:24 PM

Thanks Ponzandro! I eagerly await the results of your test.

If anyone has tried this method and has problems or especially if you have been successful with this method Please Please Please post details here. I have responded to a number of posts but no one has yet told me if they were successful. I would really like to extend the known working list beyond the 3ware 7002. Thanks and good luck.

EDDI

Aug 31 2004, 12:04 AM

Thanks, first guide who works.

trainee

Sep 1 2004, 12:58 AM

@EDDI: Thanks, but what works? Please post what hardware you were able to successfully slipstream with this method so other people will know that it works. If you had to do anything special (different from the guide) please let us know that too. Thanks.

EDDI

Sep 1 2004, 12:41 PM

what i wanted to achive:

full unattended install of windows xp professional with slipstreamed service pack 2, on harddiscs connected to a 3ware escalade 7000-2 raid-controller.

hardware used:

MB: asus tusl2-c rev. 1.04 Bios 1012 final
CPU: intel celeron 1200 MHz
RAM: 512 MB sd-ram
NIC: 3com 905b-tx
RAID: 3ware escalade 7000-2 ata-raid-controller, using softwareset 7.7.1
HDD: 2x 20 GB ibm dtla-305020 connected to 7000-2
VGA: matrox millennium g200 agp 16MB
DVD: toshiba sd-1702, connected to primary master

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

software / tools used:

- windows xp cd-rom (german version)
- downloaded sp2 network install for german language (WindowsXP-KB835935-SP2-DEU.exe, ~ 260MB)
- bcd111.zip, wxp10.zip from nu2.nu page, wnaspi32.dll from ahead software, needed by bcd, is linked at nu2.nu near where bcd111.zip is located. (needed for creating iso file)
- setupmgr.exe from the windows xp support tools for sp2 (for creating winnt.sif)
- driver files from 3ware for the 7000-2 Controller (filename win2k3.zip ~ 65 kB)
--------------------------------------------------------------------------------------------

1)
create directory c:\bcd

2)
extract first bcd111.zip to c:\bcd (make sure subfolders are correct extracted), then followed by wxp10.zip.

3)
copy wnaspi32.dll to c:\bcd\bin\wnaspi32.dll.

4)
copy from your original Windows XP-CD-ROM the folder "I386" including subfolders to c:\bcd\cds\wxppro\files, so that the new structure is the following:

c:\bcd\cds\wxppro\files\I386.

5)
to slipstream sp2 into your setup files execute

CODE

"WindowsXP-KB835935-SP2-DEU.exe /integrate:c:\bcd\cds\wxppro\files"

; wait for it to finish.

6)
create the following folders:

CODE

c:\bcd\cds\wxppro\files>
mkdir $OEM$
mkdir $OEM$\Drv
mkdir $OEM$\Drv\000_3ware
mkdir $OEM$\TEXTMODE
mkdir I386\$OEM$

7)
extract the driver files into the following folders:

c:\bcd\cds\wxppro\files\$OEM$\TEXTMODE\
c:\bcd\cds\wxppro\files\$OEM$\Drv\000_3ware\
c:\bcd\cds\wxppro\files\I386\$OEM$\

8)
use setupmgr.exe to create your unattend.txt file.

9)
rename the created unattend.txt to winnt.sif

10)
I list my winnt.sif for reference:

CODE

;SetupMgrTag
[Data]
AutoPartition=1
MsDosInitiated="0"
UnattendedInstall="Yes"
AutomaticUpdates=yes

[Unattended]
UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
UnattendSwitch="yes"
TargetPath=\WINDOWS
DriverSigningPolicy=Ignore
OemPnPDriversPath="Drv\000_3ware"

[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
AutoLogon=Yes
AutoLogonCount=1
OEMSkipRegional=1
TimeZone=110
OemSkipWelcome=1

[UserData]
ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
FullName="Unattended"
OrgName="Unattended"
ComputerName=XYZ

[Display]
BitsPerPel=32
Xresolution=1024
YResolution=768
Vrefresh=85

[TapiLocation]
CountryCode=49
AreaCode=0123

[RegionalSettings]
LanguageGroup=1
SystemLocale=00000407
UserLocale=00000407
InputLocale=0407:00000407

[Branding]
BrandIEUsingUnattended=Yes

[URL]
Home_Page=about:blank
Search_Page=http://www.google.de

[Shell]
DefaultStartPanelOff=Yes
DefaultThemesOff=Yes

[Proxy]
Proxy_Enable=0
Use_Same_Proxy=1

[Identification]
JoinWorkgroup=HOME

[Components]
msmsgs=off
msnexplr=off
freecell=off
hearts=off
minesweeper=off
pinball=off
solitaire=off
spider=off
zonegames=off
hypertrm=on

[Networking]
InstallDefaultComponents=No

[NetAdapters]
Adapter1=params.Adapter1

[params.Adapter1]
INFID=*

[NetClients]
MS_MSClient=params.MS_MSClient

[NetServices]
MS_SERVER=params.MS_SERVER

[NetProtocols]
MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]
DNS=Yes
UseDomainNameDevolution=No
EnableLMHosts=Yes
AdapterSections=params.MS_TCPIP.Adapter1

[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=Yes
WINS=No
NetBIOSOptions=0

[MassStorageDrivers]
"AMCC 3ware 7000/8000 Series ATA RAID Controller" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE-Controller" = "RETAIL"

[OemBootFiles]
TXTSETUP.OEM
oemsetup.inf
3wManage.inf
AmccDrv7.cat
3wDrv100.sys
3wFltdrv.sys

be sure to make no typos, especially at the [MassStorageDrivers] section. the german version has a hiphen between IDE and Controller, the english not, can be very bad, because no accessible cd-rom at the gui-setup part leads to failure.

11)
two ways now:

way one:

put the final winnt.sif to c:\bcd\cds\wxppro\files\I386\winnt.sif and create the iso file by typing the following at prompt:

CODE

c:\bcd>bcd wxppro -b

this iso file burned to a cd-rw can be used to install without a floppydrive.

way two:
put the final winnt.sif to a floppy.
create the iso file by typing the following at prompt:

CODE

c:\bcd>bcd wxppro -b

this way you can have more than one preconfigured floppies for use with that cd-rw.

12) burn the iso file to a cd-rw, i used nero burning rom for this.

13)
boot search order at bios:

1. cd-rom
2. harddisc (3ware)
3. floppy

be sure that floppy is behind both of the first.

14)
Insert the cd-rw and floppy into their drives and go for it.
you will only be prompted once for creating a partition to install to
and how to format her, the rest wents completely from alone.

PS: I know how to create a formatted partition with a BartPE cd,
then you will not even be prompted once.

Enjoy !

rcordorica

Sep 2 2004, 04:03 AM

Your method works! I have a Si3112r and your method allowed me to install windows onto my raid installation. However, during the GUI install portion where windows normally searches for drivers, a window pop up and tells you that it can't find the .cpl file. (actually, i am not to sure exactly which file it is). To correct the problem i just pointed to my install CD with the file. Maybe i forgot to include it in the windows $OEM$ path in the first place.

I noticed that during my first attemp at your method, i copied the wrong 3112 files (i got the 3112, not the 3112r) and the textmode setup complained that it couldn't find i386/$OEM$/si3112r.sys. So I guess that is where windows is looking for files. I think the rest of the directories you posted aren't really needed. I fixed that, but then i forgot to remove the dll= line so i got an illegal file type message.

thanx

Spinman

Sep 4 2004, 02:07 PM

If I may hijack this thread - I'm totally confused about RAID and PCI Hard Disk Controllers....

From reading bits and pieces, I've setup my ATA/133 controller as follows:

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = OEM
"Primary IDE Channel" = OEM
"Secondary IDE Channel" = OEM

[OEMBootFiles]
idechndr.inf
IdeBusDr.sys
IdeChnDr.sys
Txtsetup.oem

[Unattended] OemPnPDriversPath="Drivers\000_Intel_Inf;Drivers\001_Promise_FullRaid;Drivers\002_Intel_AppAcc;Drivers\004_Intel_Lan;Drivers\005_Nec97f;Drivers\009_Maxtor_ATA

In 009_maxtor_ATA -I've included:
readme.bat
txtsetup.oem
ulcoins.dll
ultra
ultra.cat
ultra.inf
ultra.sys

I am installing windows on Drive C:\
I am installing my Documents and Settings Directory on D:\ (mirror raid)

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = OEM
"Primary IDE Channel" = OEM
"Secondary IDE Channel" = OEM
"WinXP Promise FastTrak TX2000 ™ Controller (PDC20276)" = OEM

[OEMBootFiles]
idechndr.inf
IdeBusDr.sys
IdeChnDr.sys
Txtsetup.oem
Fasttrak.sys
Fasttrak.inf
Fasttrak.cat
TXTsetup.oem

In 001_Promise_FullRaid I've included:

fasttrak
fasttrak.cat
fasttrak.inf
fasttrak.sys
readme.txt
txtsetup.oem

Because the raid is not being used for windows installation, but only for D & S setup - will I be able to install the drivers this way?

Do I have a problem with (2) txtsetup.oem references under [oembootfiles]?

I'm totally confused---

trainee

Sep 4 2004, 10:35 PM

Hey, I know there has been quite a bit of activity in this thread and I want to respond to all of your posts ASAP, but I'm on vacation through the end of the long weekend (Monday = labor day in the USA). I am reading the posts, but I don't know if I will be able to respond or research them until Tuesday at the earliest. Sorry

trainee

Sep 6 2004, 01:41 PM

@EDDI: Thanks for posting all of your installation details. As far as I know this is the only method that will work for the 3ware card so I'm glad you found it! Your experience is another great reference! Thanks again.

@rcordorica: Great! We now have the first confirmed non-3ware driver case! I am going to list the confirmation for the SiL 3112r drivers at the top of the thread. The .cpl file is the control panel file that is installed in GUI mode. This is a little utility that shows up in the control panel in windows. This is actually the same file that the TXTSETUP.OEM chokes on and why you have to remove the "dll=" line. If you could provide us with a copy of your winnt.sif and some more information on what files you put in each directory we might be able to better address this problem.

QUOTE

I think the rest of the directories you posted aren't really needed.

Which directories are you referring to? If you are installing from a CD you absolutely need to have a $OEM$\TEXTMODE and a I386\$OEM$\ directory. I know that you don't have to have a $OEM\Driver\* directories or reference the drivers in the winnt.sif oempnpdriverspath variable for the 3ware cards. However if properly referenced this might fix the .cpl file problem with the SiL3112 drivers. Anyway thank you for confirming the relative working state of this method with your hardware.

@Spinman: Don't worry about hijaking, your post is quite pertinent to this thread. And thank you for posting so much information, but please, please use CODE tags around your winnt.sif and other file information, it is *much* easier to read. And please post your entire winnt.sif (with personal information removed) and the TXTSETUP.OEM file (which is just plain text) so we can see if your problem is somewhere else and not directly with the driver files/setup. Okay first you have some problems with your [MassStorageDrivers] section. You don't need the primary/secondary channel stuff and you haven't listed your CD. (I am assuming you are doing a CD based install).

CODE

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = OEM
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
Txtsetup.oem
idechndr.inf
IdeBusDr.sys
IdeChnDr.sys

As long as this is the complete file list (under oembootfiles), you have copied the files to the appropriate locations, and the supplied TXTSETUP.OEM doesn't have any invalid entries this should work for your primary drive. No one is exactly sure how important case-sensitivity is so it is best to try and use the *exact* naming of the files and sections.

QUOTE

In 009_maxtor_ATA -I've included:
readme.bat
txtsetup.oem
ulcoins.dll
ultra
ultra.cat
ultra.inf
ultra.sys

Are these files for your Intel controller, or for your maxtor HD? Does the maxtor need them to function, or do they just improve the performance/stability of the HD? If they are neccesary to the installation and are referenced in the TXTSETUP.OEM then they need to be with the other drivers in $OEM$\TEXTMODE and I386\$OEM$ directories and referenced in the [OemBootFiles] section.

QUOTE

I am installing windows on Drive C:\
I am installing my Documents and Settings Directory on D:\ (mirror raid)

Now, the real question is how many of your Hard drive controllers don't have built-in drivers? Do you have to install/update drivers for both your Intel controller and your fasttrack controller? I believe that you do need a floppy for your fasttrack, but it is quite possible that you don't need additional drivers for the onboard intel (if it is in fact onboard). So you might try something like this:

CODE

[MassStorageDrivers]
"Intel® 82801BA Ultra ATA Controller" = "RETAIL"
"WinXP Promise FastTrak TX2000 ™ Controller (PDC20276)" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

[OemBootFiles]
TXTsetup.oem
Fasttrak.sys
Fasttrak.inf
Fasttrak.cat

You cannot have more than 1 TXTSETUP.OEM file! If you follow the guide in the 1st post you will see that you would have to copy over 1 TXTSETUP.OEM file in the $OEM$\TEXTMODE and I386\$OEM$ directories to do this! If you have more than 1 raid/sata controller that requires additional drivers you will have to 'marry' the TXTSETUP.OEM files together to achieve this. It is quite do-able but requires more work on your part so it is best to figure out if you actually have to do this, before you go ahead and try to do it. Hope this helps, post back here with more information/questions/etc.

big poppa pump

Sep 7 2004, 02:16 AM

I keep getting an error saying:

The Manufacturer provided file that setup is trying to use is corrupted or invalid:

Line1 contains a syntax error.

I even deleted the txtsetup.oem file from the iso and tried installing xp and still end up getting the same error.

I am literally banging my head on the wall trying to figure out what the hell this error means and which file it is talking about.

Edit.....an update

I deleted winnt.sif from I386 and it went through without an hitch.

Trying to sort out my winnt.sif file now.

trainee

Sep 7 2004, 02:24 AM

@big poppa pump: sounds like you are on the right track. Why don't you post your winnt.sif and see if we can help you find the problem? (Don't forget the code tags

) I usually recommend using a very basic winnt.sif when trying to get the drivers working, so you may try to cut your winnt.sif down to basics if it has a lot of special settings. Hope this helps.

big poppa pump

Sep 7 2004, 02:31 AM

QUOTE

[Unattended]UnattendMode=FullUnattended
OemSkipEula=Yes
OemPreinstall=Yes
AutoActivate="no"
FileSystem=LeaveAlone
TargetPath=\WINDOWS
Repartition=No
UnattendSwitch="Yes"
WaitForReboot="No"
NoWaitAfterTextMode=1
NoWaitAfterGUIMode=1
DriverSigningPolicy=Ignore
OemPnPDriversPath="\drivers\001_chipset;\drivers\002_network;\drivers\003_gart;\drivers\004_video\Driver\2KXP_INF;\drivers\005_sound;\drivers\006_monitor;\drivers\007_usb"
includecatalog=KB826939.cat

[Data]
UnattendedInstall="Yes"
AutoPartition=0
MsDosInitiated="0"
AutomaticUpdates=Yes

[GuiUnattended]
AdminPassword="god"
EncryptedAdminPassword=NO
AutoLogon=No
OEMSkipRegional=1
TimeZone=20
OemSkipWelcome=1

[Shell]
CustomDefaultThemeFile = "%WinDir%\Resources\Themes\Crystal.Theme"
DefaultStartPanelOff=No
DefaultThemesOff=No

[UserData]
ProductKey=xxxxxxxxx
FullName="xxxxx"
OrgName="xxxxxx"
ComputerName=xxxxxxxx

[Display]
BitsPerPel=32
Xresolution=12804
YResolution=1024
Vrefresh=85

[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=210

[SystemFileProtection]
SFCQuota=0
SFCDisable=2

[URL]
Home_Page=about:blank

[IEPopupBlocker]
AllowedSites=http://www.microsoft.com
BlockPopups=Yes
FilterLevel=Medium
ShowInformationBar=No

[Identification]
JoinWorkgroup=WORKGROUP

[MassStorageDrivers]
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
"Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003" = "OEM"

[OEMBootFiles]
TxtSetup.oem
Si3112r.inf
si3112r.cat
si3112r.sys
siwinacc.sys
siisupp.vxd
silsupp.cpl

[Networking]
InstallDefaultComponents=No

[NetAdapters]
Adapter1=params.Adapter1
Adapter2=params.Adapter2

[params.Adapter1]
INFID="pci\ven_8086&dev_1229&subsys_10158086"
NetCardAddress = 0x0002b3961595
PciBusNumber = 2
PciDeviceNumber = 5
PciFunctionNumber = 0
ConnectionName = "Number 1"

[params.Adapter2]
INFID="pci\ven_8086&dev_1229&subsys_10158086"
NetCardAddress = 0x0002b3961596
PciBusNumber = 2
PciDeviceNumber = 4
PciFunctionNumber = 0
ConnectionName = "Number 2"

[NetProtocols]
MS_TCPIP=params.MS_TCPIP

[params.MS_TCPIP]
DNS=Yes
UseDomainNameDevolution=No
EnableLMHosts=Yes
AdapterSections = params.MS_TCPIP.Adapter1,params.MS_TCPIP.Adapter2

[params.MS_TCPIP.Adapter1]
SpecificTo=Adapter1
DHCP=No
IPAddress=192.168.1.68
SubnetMask=255.255.255.0
DefaultGateway=192.168.1.1
DNSServerSearchOrder=xx.xx.xx.xx,xx.xx.xx.xx
WINS=No
NetBIOSOptions=2

[params.MS_TCPIP.Adapter2]
SpecificTo=Adapter2
DHCP=No
IPAddress=192.168.1.69
SubnetMask=255.255.255.0
DefaultGateway=192.168.1.1
DNSServerSearchOrder=xx.xx.xx.xx,xx.xx.xx.xx
WINS=No
NetBIOSOptions=2

[Homenet]
Bridge = Adapter1,Adapter2
EnableICS = No
;ExternalAdapter = MyAdapter3
;InternalAdapter = MyAdapter4
;InternetConnectionFirewall = MyAdapter3
;InternalIsBridge = No
;ShowTrayIcon = Yes

[WindowsFirewall]
Profiles = WindowsFirewall.TurnOffFirewall

[WindowsFirewall.TurnOffFirewall]
Mode = 0

[Components]
msmsgs=off
msnexplr=off
Media_Utopia=off
OEAccess=Off
WMAccess = Off

[GuiRunOnce]
%systemdrive%\apps\bootlogo.cmd

Bâshrat the Sneaky

Sep 7 2004, 09:08 AM

I see several errors in your winnnt.sif:

1.

CODE

;SetupMgrTag
[Data]

CODE

UnattendMode=FullUnattend

CODE

[GuiUnattended]
AdminPassword=god

CODE

[GuiRunOnce]
Command0=%systemdrive%\apps\bootlogo.cmd

Hope this helps.... (I compared to my winnt.sif, which is working)

big poppa pump

Sep 7 2004, 09:25 AM

I have been using this for past few months and never once had a problem. Why would I start having problems all of a sudden?

Bâshrat the Sneaky

Sep 7 2004, 09:39 AM

QUOTE (big poppa pump @ Sep 7 2004, 05:25 PM)

I have been using this for past few months and never once had a problem. Why would I start having problems all of a sudden?

dunno then... Just try it...

big poppa pump

Sep 8 2004, 08:15 AM

Update.....

Finally managed to get Textmode working using a slightly different method than the one posted above.
The CD boots and finds my Raptors and then the installation goes thru without a hitch all the way....not really!

All files get copied over and on the first reboot get that stupid message "Disk Read Error. Press CTRL+ALT+DEL to Reboot.

trainee

Sep 9 2004, 01:45 AM

@big poppa pump: Sounds like you are making progress. I would definetly review Bâshrat's suggestions since he is very knowledgeable about these things. I still think that your winnt.sif is overly complex to try and diagnose your textmode problems, you can easily remove those additional settings and put them back in when textmode is totally working. With that said your problem sounds either bios or cd-rom related. Make sure your cd-rom entry is correct under [MassStorageDrivers]. I have provided mine below directly from my own winnt.sif.

CODE

"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"

I don't think this is your problem however.

QUOTE

2*74 WD Raptors on SATA Raid 0
2*250 Maxtors 8mb on PATA Raid 0

You should take a close look at your boot order and then make sure that you are trying to boot from the same array as you are installing your files to. If you don't see anything 'windows-like' after the first reboot then I very much suspect that you are booting to your PATA array after installing to your SATA array or visa-versa. If you see something *briefly* 'windows-like' then it is not finding your cd-rom drive after the first reboot (i have experienced this before). I suspect it is the former. Also what do you mean by "slightly different method"?

big poppa pump

Sep 9 2004, 07:53 AM

http://www.msfn.org/board/index.php?showto...&hl=Pure+Chrome

I used this one which is a slight variation to the one state here.

Anyway I got it working with this method too. So basically I have sata drivers slipstreamed working with 3 different methods. But neither method lets me install xpsp2 unattended on a raid 0 setup on a si3112r raid setup %#$^%^$%. However I am easily able to install windows on a single SATA drive off the si3112r chipset.

Bâshrat the Sneaky

Sep 9 2004, 10:23 AM

@big poppa pump: I agree with trainee. Please disconnect (not remove!) the other RAID array when installing Windows. After installing re-connect the cables. There's a good chance it will work then. (or just try to change your boot order).

big poppa pump

Sep 9 2004, 10:54 AM

The ide drives are disabled and the boot order is also changed when I am installing windows on my SATA Raid array.

EDDI

Sep 10 2004, 07:41 AM

QUOTE (big poppa pump @ Sep 7 2004, 02:31 AM)

QUOTE

[Display]
BitsPerPel=32
Xresolution=12804
YResolution=1024
Vrefresh=85

Hello,

i think you should overthink your Xresolution

12804 is very much too high.

rcordorica

Sep 10 2004, 09:55 PM

ok, i've been working on this stuff trying to get it work with my different controllers. I think I have made a few "breakthroughs"!

1. You asked to see my winnt.sif:

CODE

[Data]
AutoPartition=0
MsDosInitiated="0"
UnattendedInstall="Yes"

[Unattended]
UnattendMode=DefaultHide
OemPreinstall=Yes
TargetPath=\WINDOWS
UnattendSwitch="yes"
FileSystem=*
OemSkipEula=Yes
WaitForReboot="No"
DriverSigningPolicy=Ignore
OemPnPDriversPath="Drivers\nvidia;Drivers\intelv92;Drivers\nforce440\;Drivers\nforce440\ide;
Drivers\nforce440\gart;Drivers\nforce440\ethernet;Drivers\nforce440\smbus;Drivers\nforce440\memctl;
Drivers\nforce440\AudioUtl;Drivers\nforce440\AudioDrv;Drivers\canons750;Drivers\006_MassStorage;
Drivers\006_MassStorage\acard;Drivers\006_MassStorage\acard\6280;Drivers\006_MassStorage\acard\6290;
Drivers\006_MassStorage\acard\67160;Drivers\006_MassStorage\acard\671x;Drivers\006_MassStorage\acard\6880;
Drivers\006_MassStorage\acard\6890;Drivers\006_MassStorage\acard\68x5;Drivers\006_MassStorage\adaptec;
Drivers\006_MassStorage\adaptec\aac;Drivers\006_MassStorage\adaptec\aar1210;Drivers\006_MassStorage\adaptec\i2o;
Drivers\006_MassStorage\adaptec\u160;Drivers\006_MassStorage\adaptec\u320;Drivers\006_MassStorage\adaptec\u320r;
Drivers\006_MassStorage\ali;Drivers\006_MassStorage\amd;Drivers\006_MassStorage\highpoint;
Drivers\006_MassStorage\highpoint\hpt366;Drivers\006_MassStorage\highpoint\hpt371;
Drivers\006_MassStorage\highpoint\hpt374;Drivers\006_MassStorage\highpoint\hpt3xx;
Drivers\006_MassStorage\highpoint\rr182x;Drivers\006_MassStorage\intel;Drivers\006_MassStorage\intel\eide;
Drivers\006_MassStorage\intel\sataraid;Drivers\006_MassStorage\intel\u320r;Drivers\006_MassStorage\ite;
Drivers\006_MassStorage\lsilogic;Drivers\006_MassStorage\lsilogic\megaide;Drivers\006_MassStorage\lsilogic\mraid35x;
Drivers\006_MassStorage\lsilogic\mylex;Drivers\006_MassStorage\lsilogic\symmpi;Drivers\006_MassStorage\nvidia;
Drivers\006_MassStorage\promise;Drivers\006_MassStorage\promise\fasttrak;Drivers\006_MassStorage\promise\fasttx2k;
Drivers\006_MassStorage\promise\sx4000;Drivers\006_MassStorage\promise\sx6000;
Drivers\006_MassStorage\promise\ulsata;Drivers\006_MassStorage\promise\ultra;Drivers\006_MassStorage\qlogic;
Drivers\006_MassStorage\qlogic\12160;Drivers\006_MassStorage\siimage;Drivers\006_MassStorage\siimage\3112r;
Drivers\006_MassStorage\siimage\3114;Drivers\006_MassStorage\siimage\3114r;Drivers\006_MassStorage\siimage\3124;
Drivers\006_MassStorage\siimage\3124r;Drivers\006_MassStorage\siimage\649r;Drivers\006_MassStorage\siimage\680;
Drivers\006_MassStorage\siimage\680r;Drivers\006_MassStorage\sis;Drivers\006_MassStorage\sis\eide;
Drivers\006_MassStorage\sis\raid;Drivers\006_MassStorage\via;Drivers\006_MassStorage\via\eide;
Drivers\006_MassStorage\via\ideraid;Drivers\006_MassStorage\via\miniport;Drivers\006_MassStorage\via\sataraid"

[GuiUnattended]
AdminPassword=*
EncryptedAdminPassword=NO
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1

[UserData]
ProductKey=xxxx
FullName="Microsoft"
OrgName="Windows"

[TapiLocation]
CountryCode=1
Dialing=Tone

[RegionalSettings]
LanguageGroup=1

[Identification]
JoinWorkgroup=WORKGROUP

[Networking]
InstallDefaultComponents=Yes

[URL]
Home_Page = http://www.google.com

[TapiLocation]
Dialing=Tone

[Display]
BitsPerPel=16
Xresolution=1024
YResolution=768
Vrefresh=60

[MassStorageDrivers]
"Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller" = "RETAIL"
"NVIDIA RAID CLASS DRIVER" = "OEM"
"NVIDIA NForce Storage Controller" = "OEM"

[OEMBootFiles]
TxtSetup.oem
Si3112r.inf
si3112r.cat
Si3112r.sys
SiiSupp.vxd
SilSupp.cpl
SIWinAcc.sys
idecoi.dll
nvatabus.inf
nvata.cat
NvAtaBus.sys
nvide.nvu
nvcoi.dll
nvraid.cat
nvraid.inf
nvraid.sys
nvraidco.dll
NvRaidEnu.dll
nvraidservice.exe
NvRaidSvEnu.dll
NvRaidWizard.dll
NvRaidWizardEnu.dll
nvuide.exe
RegRaid.bat

Next you asked about my txtsetup.oem:

CODE

[Disks]
disk1 = "Silicon Image SiI 3x12 SATARaid Driver Installation Disk",\Si3112r.sys,\
d1 = "NVIDIA RAID DRIVER (SCSI)",\disk1,\

[Defaults]
SCSI = Si3112r_XP
scsi = RAIDCLASS
scsi = BUSDRV

[SCSI] ; HwComponent section
Si3112r_XP = "Silicon Image SiI 3x12 SATARaid Controller for Windows XP/Server 2003"
RAIDCLASS = "NVIDIA RAID CLASS DRIVER"
BUSDRV = "NVIDIA NForce Storage Controller"

[Files.SCSI.Si3112r_XP]
driver = disk1,si3112r.sys, Si3112r
driver = disk1,SiWinAcc.sys, SiFilter
inf = disk1,Si3112r.inf
catalog = disk1, Si3112r.cat

[Files.scsi.RAIDCLASS]
driver = d1,nvraid.sys,RAIDCLASS
inf = d1,nvraid.inf
catalog = d1,nvraid.cat
inf = d1,nvraidco.dll

[Files.scsi.BUSDRV]
driver = d1,nvatabus.sys,BUSDRV
inf = d1, nvatabus.inf
catalog = d1, nvata.cat
inf = d1,idecoi.dll

[HardwareIds.scsi.RAIDCLASS]
id = "GenNvRaidDisk","nvraid"
id = "*_NVRAIDBUS","nvraid"

[HardwareIds.scsi.BUSDRV]
id = "PCI\VEN_10DE&DEV_008E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0085", "nvatabus"
id = "PCI\VEN_10DE&DEV_00D5", "nvatabus"
id = "PCI\VEN_10DE&DEV_00EE", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E3", "nvatabus"
id = "PCI\VEN_10DE&DEV_00E5", "nvatabus"
id = "PCI\VEN_10DE&DEV_0035", "nvatabus"
id = "PCI\VEN_10DE&DEV_0036", "nvatabus"
id = "PCI\VEN_10DE&DEV_003E", "nvatabus"
id = "PCI\VEN_10DE&DEV_0053", "nvatabus"
id = "PCI\VEN_10DE&DEV_0054", "nvatabus"
id = "PCI\VEN_10DE&DEV_0055", "nvatabus"

[HardwareIds.SCSI.Si3112r_XP]
id = "PCI\VEN_1095&DEV_3112&SUBSYS_61121095", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_611215D9", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_34228086", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_B0031458", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0111019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0121019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0131019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0141019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A0151019", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1014147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_100B147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1402147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1404147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1802147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1804147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_1C00147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_5930107D", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_249510F1", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_809D1043", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0270A0A0", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_044DA0A0", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_044CA0A0", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_92011905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_92151905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_904C1905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_904B1905", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A41810FD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A41910FD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_A71910FD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_90171695", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_C2001297", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_C2011297", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_15D40035", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_340217F2", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_100415BD", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_F641270F", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C0F105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C13105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C58105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C40105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C41105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C42105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C43105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C44105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C22105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_0C2A105B", "Si3112r"
id = "PCI\VEN_1095&DEV_3112&SUBSYS_2A1E103C", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_65121095", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_B0031458", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1014147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1021147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_100B147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C06147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C00147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C03147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1C04147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1406147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_1407147B", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_90191695", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_C2021297", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_C2031297", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_C2041297", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_534D108E", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_02B71014", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_02C51095", "Si3112r"
id = "PCI\VEN_1095&DEV_3512&SUBSYS_2A1E103C", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_436E1002", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_0A44174B", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_0A45174B", "Si3112r"
id = "PCI\VEN_1002&DEV_436E&SUBSYS_00301462", "Si3112r"
id = "PCI\VEN_1002&DEV_4379&SUBSYS_43791002", "Si3112r"
id = "PCI\VEN_1002&DEV_437A&SUBSYS_437A1002", "Si3112r"

[Config.Si3112r]
;value = Parameters, NT40WorkAround, REG_DWORD, 1
;value = Parameters\PnpInterface, 5, REG_DWORD, 1
value = ProblemDevices, "", REG_SZ, ""
value = ProblemDevices, "Maxtor 4D060H3 DAK05GK0", REG_SZ, "MaxMode = UDMA-5"
value = ProblemDevices, "ST320012AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST330013AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST340017AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST360015AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST380023AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST3120023AS", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST340014ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST360014ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST380011ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST3120022ASL", REG_SZ, "Mod15Write"
value = ProblemDevices, "ST3160021ASL", REG_SZ, "Mod15Write"

[Config.RAIDCLASS]

[Config.BUSDRV]

Now here are some things I discovered along the way.

1. You can combine more than one set of textmode drivers into a single txtsetup.oem file. So what I did is use the same headers as the orignal file, and just copied over the info under the headers into a single txtsetup.oem file. In my example, I merged together my 3112r and NVRAID/NV Storage txtsetup.oem file to create a single file.

2. You can integrate DLL = files into your TEXTMODE installtion. In fact, this is necessary for some things like the NVRAID files that refuse to work without the .dll's. So what I did is simply rename the DLL = to INF =. Why? Because INF and DLL get copied to the same folder: %systemroot%/system32. The Textmode setup allows the use of INF, but not the DLL header.

3. You only need the /i386/$OEM$ and /$OEM/TEXTMODE folders to work. I didn't copy to the /i386 or other directories.

4. If you notice, I am using your method as well as the Storage driver pack method. They work nicely together. I consider your method good incase of stubborn drivers that don't work with RyanVM's method.

There are some other things I need to go over, as well as some pics that i have. I'll get back to you shortly.

(running off my NVRAID happily right now on a new system).

rcordorica

Sep 10 2004, 11:18 PM

Part two:

Well, at least I got it working, but there were some problems. Similar to what happened with the si3112r. I got these kind of errors.

Now, maybe the 3112r can be fixed by adding the .cpl file using the INF method I described above, but I don't know because I don't want to reinstall my system right now. But the nvidia drivers still has the above problem. To allow the installation to continue I had to point to my install CD where the .dll was located. Even then, I had to manually type in the .dll extention or else it would not continue (simply clicking on the missing file didn't work). I had to do this about 4 times.
it says it can't find it in OEMDir. Where do we need to place the files in order for it to get there?

Now I know that by adding the INF it at least allowed me to get into the windows installation with the NVRAID where as before I would only come to a black screen stating my disk configuration was wrong. So I did something right, although it may not be the best way.

trainee

Sep 12 2004, 06:19 AM

@rcordorica: First let me say thank you for all of your effort working on this, especially for taking the time to post your experience and insight. I think most people figure out how to get things to work and then never bother to try and help other people out. Now for the *bad* news: I have no way of diagnosing this problem. I have been trying and to recreate a scenario like this with dummied up txtsetup.oem files but haven't had any luck with it yet. I simply don't have access to any nvraid/silicon image/etc. hardware.

QUOTE

it says it can't find it in OEMDir. Where do we need to place the files in order for it to get there?

YES! I think this is absolutely the key to it. Probably the biggest breakthrough I made with this method was when I made an I386\$OEM$\ directory. A network installation doesn't require this additional directory, but a CD based install does. Similarily I have no Idea why using a floppy allows DLL lines to be processed correctly and using M2 slipstreaming doesn't. You might try searching for those files now that windows is installed just to see where they are copied to. If you still have a floppy drive and are willing to do an attended install (in the name of science?), you might see if it copies the files to any different/additional locations when using the drivers from the floppy instead of M2 slipstreaming.

I could come up with directory suggestions until I'm blue in the face, but I would have no way of testing them. I would probably try to generate about 50+ directories that seem plausible and just stick the dll files there. An example would be $OEM$\OemDir\*.dll or I386\$OEM$\OemDir\*.dll. This is how I found I386\$OEM$\. By putting it in so many different directories you can find out if it works very quickly and then later find out which was the actual directory that made it work. I will keep searching and thinking about this problem, but until then best of luck and thanks again.

cfeedback

Sep 13 2004, 10:56 AM

QUOTE (trainee @ Sep 12 2004, 06:19 AM)

I could come up with directory suggestions until I'm blue in the face, but I would have no way of testing them. I would probably try to generate about 50+ directories that seem plausible and just stick the dll files there. An example would be $OEM$\OemDir\*.dll or I386\$OEM$\OemDir\*.dll. This is how I found I386\$OEM$\. By putting it in so many different directories you can find out if it works very quickly and then later find out which was the actual directory that made it work. I will keep searching and thinking about this problem, but until then best of luck and thanks again.

XPCD\I386\$OEM$\$$\System32\ is where I had to put my DLLs for NV RAID (MSI K8N Neo Platinum) in order to get past the error 18 oemdisk.c problem mentioned by others earlier in this thread. Still not making a lot of progress though.

rcordorica - your posts have been very helpful. I will share my experiences to see if they offer any insight after I have a chance to get some sleep - been working on this for a good 12 hours.

-cfeedback

big poppa pump

Sep 13 2004, 11:10 AM

What really surprises me is that the **** error 18 crops up randomly.

trainee

Sep 13 2004, 12:36 PM

@cfeedback: do you have the same problem as rcordorica now? In other words does nvraid install but you have to point it to the DLL files during gui-install? I think that the two of you solved the same problem in different ways: you by copying the DLL's to XPCD\I386\$OEM$\$$\System32\ and rcordorica by changing his TXTSETUP.OEM 'DLL=' entried to 'INF='. Hopefully this is the case so that everyone is now working on the same problem.

@big poppa pump:

QUOTE

What really surprises me is that the **** error 18 crops up randomly.

What really surprises me is that **** Microsoft couldn't give us a few more numbers to troubleshoot this problem. What about error 19 & 20?

They must be assigned to something really important!

cfeedback

Sep 13 2004, 07:30 PM

QUOTE (trainee @ Sep 13 2004, 12:36 PM)

I might've jumped the gun a bit there - I was desperate for any ray of hope after working this for a day and a night. I don't remember the exact error but it wouldn't get very far in the GUI install (VPC).

It now seems to me that the GreenMachine's txtsetup.sif method is the way to go, even with NV RAID and their multitude of DLLs. Everything looks good in VPC, so it's time to format....again.

I've been using some info from the DriverPack thread so I'll post my results there.

trainee

Sep 13 2004, 08:29 PM

@cfeedback: Okay I'm a little disappointed that you won't be working on this method but I wish you the best of luck. It appears that rcordorica was able to get the NVRaid working, but only with some 'locate file' dialogs. This method (M2) is currently the least understood and I think most people are working on it to try and find a single way to install *all* drivers and edit as few files as possible. There is no known way to get the TXTSETUP.SIF method (M1) to work for 3ware drivers, so for people with 3ware cards this is currently the only way to slipstream.

On a related note: this thread has seen a lot of activity recently and some significant progress forward, and I hope that people stay interested in making the method work for as many drivers as possible. As always I will be here to provide as much help as I can to those who try.

cfeedback

Sep 13 2004, 08:38 PM

QUOTE (trainee @ Sep 13 2004, 08:29 PM)

FWIW when I get a sec I will certainly let you know everything I tried.

hell I might be trying this again in 30 minutes if this doesn't work...

rcordorica

Sep 22 2004, 02:48 AM

update:

I added the drivers into the %OEM%\$$\OemDir directory and everything installed perfectly using the method i posted before. No more errors about missing files.

Bâshrat the Sneaky

Sep 22 2004, 05:51 AM

QUOTE (rcordorica @ Sep 22 2004, 10:48 AM)

update:

I added the drivers into the %OEM%\$$\OemDir directory and everything installed perfectly using the method i posted before. No more errors about missing files.

Good job!!!

P.S.: I think I'll use this method in DriverPack MassStorage!

big poppa pump

Sep 22 2004, 07:52 AM

I think I will have another go at this method when I get back home from work this evening.

rcordorica

Oct 1 2004, 06:12 PM

i think somebody should stickey this thread. And update it to reflect the new info

trainee

Oct 1 2004, 08:36 PM

@rcordorica: woah...hint, hint, hint to me? Did you get my email? I am looking to update the guide but I was hoping you could help me create/debug a utility I have been writing. If you didn't get my email: Congrats on moving the TEXTMODE method to the next level. My email is shown in my signature, drop me a line.

rcordorica

Oct 1 2004, 11:03 PM

oh, i haven't gotten any email from you. I've just moved into my college and it's been my first two weeks there. Sorry, my parents probably intercepted the email, i'll have to dig it up somewhere.

btw, i didn't mean for you, but maybe one of the mod's could stick the topic; seeing how there are a lot of people out there who try this method, but without a really good guide as this one. I owe my success to the method you laid out.

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.