Microsoft KB Archive/313447

= PRB: Windows 2000 Text Mode Setup Stops Responding When You Use a QLogic SCSI Controller =

Article ID: 313447

Article Last Modified on 2/12/2007

-

APPLIES TO


 * Microsoft Win32 Device Driver Kit for Windows 2000, when used with:
 * Microsoft Windows 2000 Standard Edition

-



This article was previously published under Q313447



SYMPTOMS
You install Windows 2000 on a computer that has a QLogic QLA12160 64-bit peripheral component interconnect (PCI) dual small computer system interface (SCSI) host bus adapter and an American Megatrends Inc. (AMI) MegaRAID Enterprise 1600 redundant array of inexpensive disks (RAID) controller. After you supply the OEM drivers, the computer displays the message &quot;Setup is starting Windows 2000,&quot; but the system stops responding (&quot;hangs&quot;).



CAUSE
The PCI device and vendor IDs of the QLogic chips that are used by the QLogic HBA and the AMI RAID controller are the same. Therefore, the QLogic driver will be installed for the QLogic chips that are used by the AMI RAID controller. The QLogic driver cannot be used with an AMI RAID controller, so the QLogic driver will continuously reset the QLogic chips. This will make the system stop responding.



RESOLUTION
You can modify the AMI Txtsetup.oem file to add another section for the QLogic chips that contains the QLogic chips' hardware ID, which includes both the subsystem ID and the subsystem vendor ID. You must associate the AMI SCSI miniport driver with this device. As a result, the AMI driver will be installed for this device.

After you press F6 to install the third-party SCSI or RAID driver, insert the AMI driver disk that contains the modified Txtsetup.oem file. Press S to specify &quot;additional device,&quot; select MegaRAID Enterprise 1600 RAID Controller, and then press ENTER to load the driver. Next, press S again and select the entry that you added for the QLogic chips to load the AMI driver for the QLogic chips in the AMI RAID Controller.

After you load these two drivers, insert the QLogic driver disk and press S again. Select QLogic QLA12160, 64 bit PCI DUAL 160M SCSI HBA, and then press ENTER to load the QLogic driver. Setup will continue without any problem.

You must load the drivers in the order that is described in this section. If you load the drivers in a different order, the system will stop responding. When you load the AMI driver before the QLogic driver, the AMI driver will be installed for the QLogic chips that are used by the AMI RAID controller. This will prevent the installation of the QLogic driver for the QLogic chips that are used by the AMI RAID controller.



MORE INFORMATION
The AMI Enterprise 1600 RAID controller uses an AMI microprocessor and two QLogic QLA12160 chips. The AMI-supplied Txtsetup.oem file only refers to the AMI microprocessor. Because there are no associated drivers for the QLogic chips, the driver that QLogic supplies for the SCSI HBA is installed for the QLogic chips also.

If you add another entry in the AMI Txtsetup.oem file for the QLogic chips, the AMI driver will be associated with those chips. When you run Setup, the AMI driver will be loaded for these devices.

Instead of altering the contents of the AMI Txtsetup.oem file, you can simply replace it with the following: [Disks] MegaRAID1CH = &quot;MegaRAID Express 500 RAID Controller Driver&quot;, \mraid2k.sys, \ MegaRAID2CH = &quot;MegaRAID Elite 1600 RAID Controller Driver&quot;, \mraid2k.sys, \ MegaRAID4CH = &quot;MegaRAID Enterprise 1600 RAID Controller Driver&quot;, \mraid2k.sys, \ QLogic     = &quot;QLogic SCSI Controller&quot;, \mraid2k.sys, \

[Defaults] scsi = MegaRAID4CH

[scsi] MegaRAID1CH = &quot;MegaRAID Express 500 RAID Controller Driver&quot;, mraid2k MegaRAID2CH = &quot;MegaRAID Elite 1600 RAID Controller Driver&quot;, mraid2k MegaRAID4CH = &quot;MegaRAID Enterprise 1600 RAID Controller Driver&quot;, mraid2k QLogic     = &quot;QLogic SCSI Controller&quot;, mraid2k

[Files.scsi.MegaRAID2CH] driver = MegaRAID2CH, mraid2k.sys, mraid2k inf    = MegaRAID2CH, oemsetup.inf, mraid2k inf    = MegaRAID2CH, nodev.inf catalog = MegaRAID2CH, mraid2k.cat

[Files.scsi.MegaRAID1CH] driver = MegaRAID1CH, mraid2k.sys, mraid2k inf    = MegaRAID1CH, oemsetup.inf, mraid2k inf    = MegaRAID1CH, nodev.inf catalog = MegaRAID1CH, mraid2k.cat

[Files.scsi.MegaRAID4CH] driver = MegaRAID4CH, mraid2k.sys, mraid2k inf    = MegaRAID4CH, oemsetup.inf, mraid2k inf    = MegaRAID4CH, nodev.inf catalog = MegaRAID4CH, mraid2k.cat

[Files.scsi.QLogic] driver = QLogic, mraid2k.sys, mraid2k inf    = QLogic, oemsetup.inf, mraid2k inf    = QLogic, nodev.inf catalog = QLogic, mraid2k.cat

[Config.mraid2k] value = &quot;&quot;, Tag, REG_DWORD, 20 value = &quot;&quot;, DriverVersion, REG_SZ, &quot;MegaRAID Express 500; Enterprise 1600; Elite 1600 RAID Controller Driver&quot; value = parameters\PnpInterface,5,REG_DWORD,1

[HardwareIds.scsi.MegaRAID4CH] id = &quot;PCI\VEN_101E&DEV_1960&SUBSYS_0471101E&quot;, &quot;mraid2k&quot;

[HardwareIds.scsi.QLogic] id = &quot;PCI\VEN_1077&DEV_1216&SUBSYS_8471101E&quot;, &quot;mraid2k&quot;

The third-party products that are discussed in this article are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.

