Microsoft KB Archive/159556

= Secondary CMD Controller Not Recognized at Startup =

Article ID: 159556

Article Last Modified on 1/19/2007

-

APPLIES TO


 * Microsoft Windows 98 Standard Edition
 * Microsoft Windows 95

-



This article was previously published under Q159556



If this article does not describe your hardware-related issue, please see the following Microsoft Web site to view more articles about hardware:

http://support.microsoft.com/default.aspx/w98?sid=460



SYMPTOMS
After you restart your computer, the secondary controller on a CMD PCI-0640 PCI-to-IDE controller may no longer be listed in Device Manager. When this occurs, devices on the secondary controller that use protected- mode drivers no longer function.



CAUSE
This behavior can be caused by incorrect settings in Device Manager for the CMD controller.



RESOLUTION
To resolve this issue, configure the parent device correctly. To do so, follow these steps:


 * 1) In Control Panel, double-click System.
 * 2) Click the Device Manager tab.
 * 3) Double-click the Hard Disk Controllers branch to expand it.
 * 4) Click the CMD PCI-0640 PCI-to-IDE controller, and then click Properties.
 * 5) Click the Settings tab.
 * 6) Select the proper configuration for the device.



MORE INFORMATION
Due to difficulties in detecting the chip sets on these controllers, extra settings have been added to ensure that they are properly configured at startup. You can chose among the following settings:


 * Default (Windows Auto Detect)
 * Both IDE Channels Enabled
 * Only Primary IDE Channel Enabled
 * Only Secondary IDE Channel Enabled
 * No IDE Channels Enabled

Additional query words: HWHDCTL 95

Keywords: kbhardware kbprb KB159556

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.