Cpqcsissm Win2003

[butor]

Hello I have a problem. We are trying to upgrade several servers from NT4 to WIN2003 we would like to do it remotely (we have a remote board to acess the computer remotely) without using the floppy drive (not compatible with the remote board). The drivers for the Raid controler is cpqcissm.sys that exists in the WIN2003 CD but is not compatible. We tried to add the good driver using nlite but we always have a problem with the boot drive not found (error 0x0000007B)

The RAID controler is a HP SMART 641

We use the same procedure for another kind of server using the same driver but the RAID controler is an Embedded 5i that use the same driver and it works without any problem.

does anybody has a solution?

Thank you very much.

Jean-Marc

Belgium

[The-VOICE]

Have you considered using Sysprep and adding the Smart Array 5x and 6x Controller driver?

[tguy]

Try this:

Section II – Modifying the i386 directory & TXTSETUP.SIF file

This section will explain one method for adding driver support for newer drive controllers to overcome this issue.

Here is what you need to do:

A) Identify the appropriate driver files for the controller you are working with ie: Compaq Smart Array 5i (as will be discussed in this example)

B) The driver files can typically be obtained from the manufacturer’s website. Once obtained, expand/copy the files to a temporary directory, ie: C:\Temp.

C) Most driver file sets will consist of at least three files. For instance with the Smart Array 5i controller the files are:

a. CPQCISSM.CAT

b. CPQCISSM.INF

c. CPQCISSM.SYS

D) Copy the .SYS driver file into the root of the i386 directory where your source files are located.

E) Next, in the i386 directory, locate a file called TXTSETUP.SIF and open with Notepad or another text editor.

F) You will need to add the following entries for your driver to each of the four sections shown below:

a. [sourceDisksFiles]

cpqcissm.sys = 1,,,,,,6_,4,1,,,1,4 (Note: the first 4 listed indicates the file is to be copied to the ..\SYSTEM32\DRIVERS directory at the destination location) To identify the exact parameters to list after the = sign, first check a Windows Server 2003 CD to see if driver support for your controller is listed. Then copy the parameters from the TXTSETUP.SIF file on the Server 2003 CD to the TXTSETUP.SIF file for Windows Server 2003. If the driver is not listed, find a similar driver and mirror those parameters.

The [sourceDisksFiles] section lists all files for the installation. This section is critical for customization because it controls which files are copied during the installation. Using a text editor (such as Notepad), you can search for the [sourceDisksFiles] section to obtain a list of all Windows Server 2003 installation files.

These settings can be difficult to figure out. Below is a graphic example that helps to explain what this numeric string does.

The following line shows the syntax of each line in the [sourceDisksFiles] section:

filename_on_source=diskid,subdir,upgradecode,newinstallcode,spare,spare, newfilename

Extra fields specified by commas (,) are Windows NT—specific.

diskid is used when a floppy disk installation is used. (Or multiple CDs?)

subdir is the directory to which files are copied. Codes defined in the [WinntDirectories] section of the TXTSETUP.SIF file are used to identify the destination directory.

upgradecode is a single digit that is used if this is an upgrade from an earlier version. It specifies whether the file is copied during the text-mode portion.

Codes in the [Files] Section of TXTSETUP.SIF for File Copy

Status Code - Copy Action

0 - Always copies the file

1 - Copies the file only if it exists in the installation directory

2 - Does not copy the file if it exists in the installation directory

3 - Does not copy the file

newinstallcode is a single digit that is used if this is a fresh installation. It specifies whether the file is copied during the text-mode portion. The same codes are used as for upgrading Windows 2000 and are described in Table 4.3. The newinstallcode is optional; if it is not included, the file is not copied (code = 3).

newfilename is the name to which the file is renamed if it is copied. As an example, consider this line from the [sourceDisksFiles] section.

NOTE: In the above diagram, if the driver file you copy to the i386 directory is not compressed, you will need to replace the 3_ or 4_ with a _x. This tells the installation that the file is not compressed and to go ahead and copy it anyway without attempting expansion.

b. [HardwareIdsDatabase]

PCI\VEN_0E11&DEV_B060 = "cpqcissm"

PCI\VEN_0E11&DEV_B178&SUBSYS_40820E11 = "cpqcissm"

PCI\VEN_0E11&DEV_B178&SUBSYS_40830E11 = "cpqcissm"

PCI\VEN_0E11&DEV_B178&SUBSYS_40800E11 = "cpqcissm"

These hardware ID strings are typically found in the .inf files that accompany the actual drivers in the download package. Copy each string relative the driver you are installing to the TXTSETUP.SIF file in this section.

c. [sCSI.load]

cpqcissm = cpqcissm.sys,4

d. [sCSI]

cpqcissm = "Compaq Smart Array 53xx-series Controller"

ADDING DRIVERS TO THE BUILD:

In addition to the RAID disk drivers discussed above you may find it necessary to add additional LAN, VIDEO, MODEM or other OEM drivers to the .ISO image for compatibility with newer servers.

To accomplish this task:

1) Download the appropriate drivers from the manufacturer and expand to temp directory.

2) Open the $OEM$\$1\PnPdrvrs directory where the source files are located.

3) If the files you wish to update are Array, or LAN drivers simply copy the driver files from the temp directory into the existing directory. Be sure to repeat this process for each $OEM$ directory corresponding to the version of Windows server. For instance you will need to copy the files to the Enterprise Edition $OEM$ directory as well as the Standard and Web Editions $OEM$ directories.

4) If the driver files are for another piece of hardware for which there is not a current directory you will need to create one. The naming convention starts out with a series of numbers 000, 001 etc. This corresponds directly to the order in which the drivers are installed. Create the directory following the established convention noted in the path from Step 2.

5) Lastly, you will need to add the new directory to the OEMPnPDriversPath line in the [unattended] section of the WINNT.SIF