|
Driver Messages
Each driver message consists of a message identifier and two 32-bit
parameters. The message identifier is a unique value that the DriverProc function checks to determine which action to carry out. The meaning of the
message parameters depends on the message. The parameters may represent values or
addresses. In many cases, the parameters are not used and are set to zero.
Driver messages can be standard or custom. Windows sends standard driver
messages, such as DRV_OPEN, DRV_CLOSE, and DRV_CONFIGURE, to an installable driver in response to a request to open, close, or
configure the driver. The standard messages direct the installable driver to load or
unload its resources, enable or disable its operation, open or close a driver
instance, and display a configuration dialog box. Some standard messages, such as DRV_POWER and DRV_EXITSESSION, notify the driver of system-wide events that affect the operation of the
driver or any related hardware.
Applications and DLLs send custom driver messages to direct an installable
driver to carry out driver-specific actions. Installable drivers that support
custom messages must include appropriate processing in the DriverProc function. To prevent conflict between custom and standard driver messages,
custom message identifiers must have values ranging from DRV_RESERVED to
DRV_USER. Custom messages passed to the DefDriverProc function are ignored.
Related Links
Software for Delphi and C++ Builder developers
Software for Visual Studio .NET developers
Software for Visual Basic 6 developers
Delphi Tips&Tricks
MegaDetailed.NET
More Online Helps
Win32 Programmer's Reference (win32.hlp)
OLE Programmer's Reference (ole.hlp)
Microsoft Windows Pen API Programmer's Reference (penapi.hlp)
Microsoft Windows Sockets 2 Reference (sock2.hlp)
Microsoft Windows Telephony API (TAPI) Programmer's Reference (tapi.hlp)
Unix Manual Pages
|
