Updated RAID/SATA Support

[GreenMachine]

I have added a couple of RAID/SATA drivers, at the request of a couple members. These are the MEGARAID and VIAMRAID drivers. I cannot remember who you were at the moment, so please download the XPCREATE.CAB file from here, and replace the current XPCREATE.CAB. I noted that the VIAMRAID driveres seems to use the same PnPID as other VIA drivers, so I would strogly recommend not trying to install both drivers.

If anyone uses these new drivers, please post how it goes. I will edit this post in the future for further updates to XPCREATE.CAB. The next version of XPCREATE will allow the user to add his own driver definition files.

As usual ... Happy XPCREATIONS

XPCREATE.CAB

[Bilou_Gateux]

Here the result of MEGARAID integration with XPCreate.

I have built a new install using Windows 2000 Server MUI + SP3 slipstream.

I run the installation from the flat CDROOT folder using winnt32.exe

After reboot, during the text mode setup, i have this message :

the file megaide.SYS could not be found

the solution to solve the problem is to manually edit dosnet.inf and add this to section

[FloppyFiles.2]
d1,megaide.sys

That way, megaide.sys is copied from the source CDROOT\MEGAIDE.SY_ to the target C:\$WIN_NT$.~BT\MEGAIDE.SY_

Edited October 16, 2005 by Bilou_Gateux

[GreenMachine]

... FloppyFiles ...

That's a new one on me. I wonder why ... I'll have to check this out when I get back, but I've never seen the need before. Could it be due to a "flat" install?

[Bilou_Gateux]

Maybe the problem is with this syntax

Switches in TXTSETUP.SIF , Here's what "1,,,,,,,,,_x,4,0" means

txtsetup.sif

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

I will try to change this to

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

Syntax may differ between 2K and XP ?

2K = 4 setup boot disks

XP = 6 setup boot disks

3_ = file on 3rd disk in 2K

4_ = file on 4th disk in XP

When we launch an install from a flat folder (other partition or network share) rather than boot from the CD, it's a kind of same installation as booting from the 1st disk and then insert 2nd 3rd and 4th ?

I have modified the syntax in txtsetup.sif to see if it can solve the problem but it doesn't change anything. Only the other solution (add a line in section [FloppyFiles.2] of dosnet.inf works for me).

It's not really a problem for me because i've found the workaround.

May be can this info contributes to make XPCreate more versatile and works with all possible cases.

The second "problem" i have to solve is to replace the old adaptec adpu160m.sys driver integrated in 2K original CD with a new one and add the new supported controllers (Adaptec Ultra160 ASIC's PCI\VEN_9005&DEV_008F.DeviceDesc = "Adaptec AIC-7892 - Ultra160 SCSI") integrated on my server mobo.

Edited August 26, 2004 by Bilou_Gateux

[Bilou_Gateux]

TOSHIBA Magnia Z310

Maybe these infos may help others msfn members to solve their RAID unattended installs :

At the moment, i use M$ recommended method with $OEM$\TEXTMODE folder

Directory of D:\XPCREATE\CDROOT\I386\$OEM$\TEXTMODE

26/08/2004  14:48       <DIR>          .
26/08/2004  14:48       <DIR>          ..
20/06/2002  17:47                8ÿ081 ADPU160M.CAT
03/06/2002  18:17                6ÿ351 ADPU160M.INF
14/05/2002  17:10               92ÿ650 ADPU160M.SYS
19/08/2002  19:49                7ÿ409 MEGA2K.CAT
26/12/2000  15:17                    9 MEGAIDE
09/08/2002  14:21                2ÿ624 MEGAIDE.INF
17/06/2002  15:30              100ÿ251 MEGAIDE.SYS
16/11/2000  15:35                1ÿ407 NODEV.INF
25/08/2004  19:03                1ÿ627 TXTSETUP.OEM
29/03/2002  13:33                   58 U160DSK1

content of the TEXMODE folder :

one device driver image (.sys) file for each RAID component

one or more information (.INF) files for each RAID component

an optional driver catalog (.CAT) file for each RAID component

one text-mode setup information file (txtsetup.oem)

in my case

ADPU160M.* are Adaptec Ultra160 Family Driver files

MEGAIDE.INF MEGAIDE.SYS MEGA2K.CAT NODEV.INF are LSI Logic MegaRAID IDE 100 Driver files

MEGAIDE and U160DSK1 are tag files found in the downloaded driver package from the manufacturer. The reference to these files appears in TXTSETUP.OEM file, that's why i keep them although I'm not sure it's needed.

some driver packages also contains driver library (.dll ) files but i can't say if they're needed for TEXTMODE install method.

D:\XPCREATE\CDROOT\I386\WINNT.SIF

[OEMBootFiles]
ADPU160M.SYS
ADPU160M.INF
ADPU160M.CAT
MegaIDE.sys
MegaIDE.inf
Mega2k.cat
nodev.inf
TXTSETUP.OEM
[MassStorageDrivers]
"LSI Logic MegaRAID IDE 100 Driver With Backplane Support (Windows 2000)" = "OEM"
"Adaptec Ultra160 Family PCI SCSI Controller (Windows 2000)" = "OEM"
"IDE CD-ROM (ATAPI 1.2)/PCI IDE Controller"=RETAIL

D:\XPCREATE\CDROOT\I386\$OEM$\TEXTMODE\TXTSETUP.OEM

####################################################################################
#
#This txtsetup.oem file can be used for unattended installs of Windows 2000 only.
#
####################################################################################
[Disks]
d3 = "LSI Logic MegaRAID IDE Driver",.\MEGAIDE,""
d4 = "Adaptec Ultra160 Family Driver",.\U160DSK1,""

[Defaults]
scsi = MegaIDE_NT5

[scsi]
MegaIDE100_NT5 =   "LSI Logic MegaRAID IDE 100 Driver With Backplane Support (Windows 2000)", MegaIDE
adpu160m = "Adaptec Ultra160 Family PCI SCSI Controller (Windows 2000)", adpu160m

# 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.MegaIDE100_NT5]
driver  = d3, MegaIDE.sys, MegaIDE
inf     = d3, MegaIDE.inf
inf	= d3, Nodev.inf
catalog = d3, Mega2k.cat

[Files.scsi.adpu160m]
driver = d4,adpu160m.sys, aic7892
inf    = d4,adpu160m.inf
catalog = d4,adpu160m.cat

[HardwareIds.scsi.MegaIDE100_NT5]
id="PCI\VEN_1095&DEV_0649&SUBSYS_0649101E", "MegaIDE"

[HardwareIds.scsi.adpu160m]
id = "PCI\VEN_9005&DEV_008F","adpu160m"

[Config.MegaIDE]
value = "", Tag, REG_DWORD, 1

[Config.adpu160m]
value = "",tag,REG_DWORD,20

[GreenMachine]

Thanks again, Bilou! Looks like I'll need to revise the SATA stuff when I get back to work. I'll get back to you then.

I was under the impression that 3_ or 4_ did not really mater, as well as the ending letters. I guess I should really break down, and get the Microsoft TEXTMODE stuff working.

[Bilou_Gateux]

... FloppyFiles ...

That's a new one on me. I wonder why ... I'll have to check this out when I get back, but I've never seen the need before. Could it be due to a "flat" install?

look at the Tbone2 post.

Tbone2

He adds lines to section [FloppyFiles.2] for RAID drivers

The position of $OEM$ in the folder tree differs when you install from CD :

CDROOT\$OEM$

or from flat or network share :

CDROOT\I386\$OEM$

Creating OEM installations for Windows

Some notes and review:

You have to put the $OEM$ folder alongside the i386 folder for 2000 CD's and not under the i386 folder (this is a bug MS will not be fixing).

[GreenMachine]

Thanks Bilou. I've added this to my review list for when I work on the SATA drivers next. However, I think that will be the next, next release: I already have my list for the next release.