BUG: IOCTL SMART_GET_VERSION Returns Invalid bIDEDeviceMap Info
PSS ID Number: 196120
Article Last Modified on 11/18/2003
The information in this article applies to:
- Microsoft Windows NT 4.0 Driver Development Kit (DDK)
- Microsoft Windows 2000 Driver Development Kit (DDK)
- Microsoft Windows XP Driver Development Kit (DDK)
This article was previously published under Q196120
SYMPTOMS
The IOCTL call for SMART_GET_VERSION returns invalid bIDEDeviceMap
information in the GETVERSIONINPARAMS structure. If the IOCTL succeeds, the
bIDEDeviceMap will always be 1. The bIDEDeviceMap is a bitmask that
typically provides device information, indicating IDE or Atapi, primary or
secondary controller, drive 0 or drive 1.
NOTE: SMART stands for Self-Monitoring, Analysis and Reporting Technology.
The SMART_GET_VERSION IOCTL is sometimes referred to as the DFP_GET_VERSION
IOCTL.
NOTE: DFP stands for Disk Fault Protection.
CAUSE
The Atapi.sys driver incorrectly fills in the bIDEDeviceMap information
when the SMART_GET_VERSION IOCTL is issued.
RESOLUTION
There is no resolution at this time.
STATUS
Microsoft has confirmed this to be a bug in the Microsoft products listed
at the beginning of this article.
REFERENCES
The Microsoft Windows 95 and Windows NT SMART IOCTL API Specification is
available on:
Refer to the SMART Specification from the SFF (Small Form Factor) Committee
for additional SMART details.
Keywords: kbBug kbStorageDev KB196120
Technology: kbAudDeveloper kbwin2000DDK kbwin2000Search kbWinDDK kbWinDDKSearch kbWinNT400DDK kbWinNT400search kbWinNTsearch kbWinXPDDKSearch