Partager via


DRV_OPEN (Windows Embedded CE 6.0)

1/6/2010

This message requests a driver to be opened. Drivers are opened for many reasons. The most common reason is preparation for data conversion. Your driver must be able to handle multiple open-driver instances correctly. Multiple streams can and will be opened on a single driver instance. Do not store and/or create instance data that is unique to a stream.

Parameters

  • hdrvr
    Driver handle that will be returned to the application. This is typically the handle of the ACM driver, but this is not guaranteed. For example, if an ACM driver is implemented within a waveform driver, then the driver will be opened by both MMSYSTEM and ACM.
  • lParam2
    Pointer to the ACMDRVOPENDESC structure that defines how ACM driver is being opened.

Return Values

The supporting function returns zero (0) if the driver fails to open. Otherwise, it returns a nonzero value that identifies the driver instance

Remarks

Whenever an application sends a message to the driver, the Real-time Communications (RTC) Client API routes the message to this entry point and passes this value in the dwID parameter.

Requirements

Header msacmdrv.h
Windows Embedded CE Windows CE 1.0 and later

See Also

Reference

DRV_CLOSE

Concepts

ACM Driver Messages
Required Entry-point Function