BUG: IOCTL SMART_GET_VERSION Returns Invalid bIDEDeviceMap Info

ID: Q196120

The information in this article applies to:

Microsoft Win32 Device Driver Kit (DDK) for Windows NT, version 4.0

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:

http://www.microsoft.com/hwdev/respec/storspec.htm

Refer to the SMART Specification from the SFF (Small Form Factor) Committee for additional SMART details.

Keywords : kbDDK kbNTOS400bug kbStorageDev
Version : WINNT:4.0
Platform : winnt
Issue type : kbbug