Microsoft KB Archive/314667

= Tape Class API Calls Do Not Appear to Be Implemented =

Article ID: 314667

Article Last Modified on 3/2/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, 64-Bit Datacenter Edition

-



This article was previously published under Q314667



SYMPTOMS
When an application attempts to call the tape application programming interfaces (APIs), it may appear that not all the API calls in the native drivers are implemented. For example, on a digital audio tape (DAT) drive, Erase Short may not appear to be implemented, although Erase Long may appear to be implemented.



STATUS
This behavior is by design.



MORE INFORMATION
The application calling the tape APIs should look at flags (bits) set in FeaturesLow and FeaturesHigh fields of TAPE_GET_DRIVE_PARAMETERS.

For instance, if the drive supports Erase Short, then TAPE_DRIVE_ERASE_SHORT is set in FeaturesLow. If the drive supports Erase Long, then TAPE_DRIVE_ERASE_LONG is set. The Driver Development Kit documentation gives an explanation for each flag in these fields.

Keywords: kbnofix kbprb kbprogramming KB314667

-

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

© Microsoft Corporation. All rights reserved.