Jump to content

Installing highpoint RAID with RIS


Recommended Posts

Hi, MSFN

I am in a desperate need of help. I am trying to install Windows XP Pro with RIS

I have the same problem as http://www.msfn.org/board/lofiversion/index.php/t46469.html

I have my drivers in

$OEM$

-> $1

-> Driver

-> RAID

I have only problems with the raid driver and I have tried a lot of deferent things.

------------------START OF TXTSETUP.OEM-------------------------------------

#

# TXTSETUP.OEM for RocketRAID 154x/1640 Controller

#

[Disks]

d1 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \

d2 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \win_nt

d3 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \win_2000

d4 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \win_xp

d5 = "RocketRAID 154x/1640 Controller Driver Diskette", \Disk1, \AMD64

[Defaults]

scsi = hpt3742K

[scsi]

hpt374NT = "RocketRAID 154x/1640 Controller for WinNT 4.0", hpt374

hpt3742K = "RocketRAID 154x/1640 Controller for Win2000", hpt374

hpt374XP = "RocketRAID 154x/1640 Controller for WinXP/2003", hpt374

hpt374amd64 = "RocketRAID 154x/1640 Controller for Windows AMD64", hpt374

[Files.scsi.hpt374NT]

driver = d2, hpt374.sys, hpt374

inf = d2, hpt374.inf

[Files.scsi.hpt3742K]

driver = d3, hpt374.sys, hpt374

inf = d3, hpt374.inf

catalog= d3, hpt374.cat

[HardwareIds.scsi.hpt3742K]

id = "PCI\VEN_1103&DEV_0008","hpt374"

[Files.scsi.hpt374XP]

driver = d4, hpt374.sys, hpt374

inf = d4, hpt374.inf

catalog= d4, hpt374.cat

[HardwareIds.scsi.hpt374XP]

id = "PCI\VEN_1103&DEV_0008","hpt374"

[Files.scsi.hpt374amd64]

driver = d5, hpt374.sys, hpt37464

inf = d5, hpt374.inf

catalog= d5, hpt374.cat

[HardwareIds.scsi.hpt374amd64]

id = "PCI\VEN_1103&DEV_0008","hpt374"

[Config.hpt37464]

value = "", Tag, REG_DWORD, 1

value = "Parameters\PnpInterface", 5, REG_DWORD, 1

------------------END OF TXTSETUP.OEM--------------------

------------------START OF *.SIF FILE---------------------------------

;SetupMgrTag

[data]

floppyless="1"

msdosinitiated="1"

OriSrc="\\%SERVERNAME%\RemInst\%INSTALLPATH%"

OriTyp="4"

LocalSourceOnCD=1

AutoPartition=1

UnattendedInstall="Yes"

[setupData]

OsLoadOptions="/noguiboot /fastdetect"

SetupSourceDevice="\Device\LanmanRedirector\%SERVERNAME%\RemInst\%INSTALLPATH%"

[unattended]

OemPreinstall=Yes

FileSystem=LeaveAlone

ExtendOEMPartition=0

TargetPath=\WINDOWS

OemSkipEula=Yes

InstallFilesPath=\\%SERVERNAME%\RemInst\%INSTALLPATH%\%MACHINETYPE%

LegacyNIC=1

UnattendMode=FullUnattended

;;UnattendMode=GUIAttended

NtUpgrade=No

OverwriteOemFilesOnUpgrade=No

OemPnPDriversPath="Drivers\DRIVER\raid;Drivers\DRIVER\raid\d1;Driver\test\"

;OemPnPDriversPath="Drivers\EVO800c\Audio;Drivers\EVO800c\Nic;Drivers\EVO800c\video;Drivers\EVO800c\Modem;Drivers\EVO800c\USB2SER\"

DriverSigningPolicy=Ignore

[Components]

msnexplr=Off

;Installation af Mediaplayer

;VMAccess=Off

[PCHealth]

;Styres via GroupPolicy

;RA_AllowFullControl = 0

;RA_AllowToGetHelp = 1

;RA_AllowUnsolicited = 1

;RA_MaxTicketExpiry = 30

[userData]

FullName="%USERFIRSTNAME% %USERLASTNAME%"

OrgName="%ORGNAME%"

ComputerName=%MACHINENAME%

ProductKey=XXXXX-XXXXX-XXXXX-XXXXX-XXXXX

[GuiUnattended]

OemSkipWelcome=1

OemSkipRegional=1

TimeZone=%TIMEZONE%

AdminPassword=top

EncryptedAdminPassword=No

AutoLogon=Yes

AutoLogonCount=1

[Display]

BitsPerPel=32

XResolution=1400

YResolution=1050

VRefresh=60

[Networking]

InstallDefaultComponents=Yes

ProcessPageSections=Yes

[identification]

JoinDomain=%MACHINEDOMAIN%

DoOldStyleDomainJoin=Yes

[RemoteInstall]

Repartition=Yes

UseWholeDisk=Yes

[OSChooser]

Description="Windows Professional – NAME "

Help="Dette vil installere Windows XP Pro"

LaunchFile="%INSTALLPATH%\%MACHINETYPE%\templates\startrom.com"

ImageType=Flat

Version=5.1

[TapiLocation]

CountryCode=45

AreaCode=0045

[RegionalSettings]

LanguageGroup=2,1

[branding]

BrandIEUsingUnattended=Yes

Home_Page=http://bsdnet

[Proxy]

Proxy_Enable=0

Use_Same_Proxy=0

----------------END OF *.SIF FILE---------------------------------------

Link to comment
Share on other sites

  • 1 month later...

Michael,

I myself was in the same boat less than 1 hour ago. I ran across this site and was able to get it to work with my IBM Intellistation ZPRo

http://web.mit.edu/ist/topics/windows/serv...du/whatsRIS.htm

Here is the good stuff you need though, if you follow it to a T you will be working perfect

Configuring a RIS image to load a SCSI Mass Storage Device driver in textmode

In some instances systems require an OEM SCSI Mass Storage Device driver to begin the installation. The reason for this is if the controller of the boot drive is not supported by drivers included in the Windows 2000 CD, an OEM driver must be loaded before setup can access the disk. This is regardless of whether the controller has BIOS loaded or not. The user can either hit F6 and use drivers from an OEM floppy during the install, or we can configure the RIS image to load the driver.

Microsoft has documented a process for loading a Mass Storage Device driver in the textmode portion of setup for unattended installations. I did not see specific instructions for this pertaining to RIS, so I substituted the unattended.txt file for the .sif file in their documentation, and the installation was successful.

The second change made was to add the driver files to i386 in case RIS would only look there and not in the OEM path. Additional testing need to be done to see if this was necessary. It was done only as an insurance measure to get the Building 37 cluster image ready without too many iterations of testing.

What we found was that setup did not try to detect this device, it merely forced the driver to load regardless of the hardware of the system, so if another machine without this controller were to use this image, the result would be the infamous BSOD, with the message, "Inaccessible boot device". This means any time we need to have RIS load such a driver during textmode there must be a dedicated RIS image for that hardware, or at least that disk controller.

See the following URL for Microsoft's documentation [this particular doc was for XP, but the same applied to 2000. I used it because it was much more brief and to the point of what I needed than the 2000 doc]:

http://www.microsoft.com/resources/documen...bc_cai_qcxl.asp

Here is the procedure as it applied to RIS after you create a new image for this hardware:

1). In the distribution folder, create the Textmode folder in the \$OEM$ folder.

2). Copy the driver files into the Textmode folder.

3). Copy the driver files to \$OEM$\1\Drivers\SCSI

4). In the beginning of the .sif file, add an [OEMBootFiles] section and then the following entries:

oemsetup.inf

driver.sys [substitute the name of the driver]

txtsetup.oem

5). Add a [MassStorageDrivers] section to the .sif file and determine the device name From the txtsetup.oem. For example for the LSI Logic Ultra 320 you will find the this line:

SYMMPI = "LSI Logic PCI SCSI/FC MPI Miniport Driver",symmpi

The name you would use here will be "LSI Logic PCI SCSI/FC MPI Miniport Driver"

So the syntax you will use in the sif file under [MassStorageDrivers] will be look like:

"LSI Logic PCI SCSI/FC MPI Miniport Driver" = "OEM"

6). In the [unattended] section of the .sif file, make sure the DriverSigningPolicy = Ignore entry exists. Also verify that the OemPnpDriversPath includes \Drivers\SCSI.

7). Stop and restart the Boot Information Negotiation Layer (BINL) service on the RIS server.

This step is required for these changes to take effect.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...