Tape Class API Calls Do Not Appear to Be Implemented (314667)


The information in this article applies to:

  • Microsoft Windows Server 2003, Standard Edition
  • Microsoft Windows Server 2003, Enterprise Edition
  • Microsoft Windows Server 2003, Datacenter Edition
  • Microsoft Windows Server 2003, 64-Bit Enterprise 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.
Modification Type:MajorLast Reviewed:6/5/2003
Keywords:kbnofix kbprb kbProgramming KB314667
©2002 Microsoft Corporation. All rights reserved.