WM_DEVICECHANGE看别人的东东

昨天有人问我，如何”hook” Windows的WM_DEVICECHANGE消息，相关的问题以前在blog上写过一个方法，但那是适用于有窗口的。我想他要实现的是在无窗口的情况下只用一个dll实现，觉得新鲜，于是试了一下。
我用的是全局的hook,首先用的是
SetWindowsHookEx( WH_GETMESSAGE, UsbProc, g_hInst, 0 );
钩子函数是这样定义的
LRESULT CALLBACK UsbProc(int nCode,WPARAM wParam,LPARAM lParam)
{
switch(nCode)
{
case HC_ACTION:
if ( wParam == PM_NOREMOVE)
{
PMSG pMsg = PMSG(lParam);
if ( pMsg->message == WM_DEVICECHANGE )
{
switch( pMsg->wParam )
{
case DBT_DEVICEARRIVAL:
MessageBox( NULL, "Device arrival!", "警告", MB_OK );
break;
case DBT_DEVICEQUERYREMOVE:
// Handle device removal request
MessageBox( NULL, "Device request remove!", "警告", MB_OK );
break;
case DBT_DEVICEREMOVECOMPLETE:
// Handle device removal
MessageBox( NULL, "Device removal!", "警告", MB_OK );
break;
}
}
}
}
return CallNextHookEx( NULL,nCode,wParam,lParam);
}
这样的话，当U盘插入的时候，并没有出现设备插入的提示，但是把DBT_DEVICEARRIVAL换成DBT_DEVNODES_CHANGED后就可以，只是有20几个提示。
于是我改用下面的方法：
SetWindowsHookEx( WH_CALLWNDPROC, UsbProc, g_hInst, 0 );
LRESULT CALLBACK UsbProc(int nCode,WPARAM wParam,LPARAM lParam)
{
switch(nCode)
{
case HC_ACTION:
PCWPSTRUCT pMsg = PCWPSTRUCT(lParam);
if ( pMsg->message == WM_DEVICECHANGE )
{
switch( pMsg->wParam )
{
case DBT_DEVICEARRIVAL:
MessageBox( NULL, "Device arrival!", "警告", MB_OK );
break;
case DBT_DEVICEQUERYREMOVE:
// Handle device removal request
MessageBox( NULL, "Device request remove!", "警告", MB_OK );
break;
case DBT_DEVICEREMOVECOMPLETE:
// Handle device removal
MessageBox( NULL, "Device removal!", "警告", MB_OK );
break;
}
}
}
return CallNextHookEx( NULL,nCode,wParam,lParam);
}

这样出现了预定的提示，但是是一直提示。
在网上得到了下面的资料：
There are 14 types of hooks:
WH_CALLWNDPROC called when SendMessage is called
WH_CALLWNDPROCRET called when SendMessage returns
WH_GETMESSAGE called when GetMessage or PeekMessage is called
WH_KEYBOARD called when GetMessage or PeekMessage retrieves WM_KEYUP or WM_KEYDOWN from the message queue
WH_MOUSE called when GetMessage or PeekMessage retrieves a mouse message from the message queue
WH_HARDWARE called when GetMessage or PeekMessage retrieves some hardware message that is not related to keyboard or mouse.
WH_MSGFILTER called when a dialog box, menu or scrollbar is about to process a message. This hook is local. It’s specifically for those objects which have their own internal message loops.
WH_SYSMSGFILTER same as WH_MSGFILTER but system-wide
WH_JOURNALRECORD called when Windows retrieves message from the hardware input queue
WH_JOURNALPLAYBACK called when an event is requested from the system’s hardware input queue.
WH_SHELL called when something interesting about the shell occurs such as when the task bar needs to redraw its button.
WH_CBT used specifically for computer-based training (CBT).
WH_FOREGROUNDIDLE used internally by Windows. Little use for general applications
WH_DEBUG used to debug the hooking procedure
和
LRESULT CALLBACK WindowProc(
HWND hwnd, // handle to window
UINT uMsg, // WM_DEVICECHANGE
WPARAM wParam, // device-change event
LPARAM lParam // event-specific data
);
Parameters
hwnd
Handle to window.
uMsg
WM_DEVICECHANGE message identifier.
wParam
Set to DBT_DEVNODES_CHANGED.
lParam
Set to zero.
Return Values
Return TRUE.

Remarks
There is no additional information about which device has been added to or removed from the
system. Applications that require more information should register for device notification.
难道必须要用RegisterDeviceNotification吗？看来这个问题还是要好好研究一下

本文转自
http://www.blog.edu.cn/user4/pafone/archives/2007/1660551.shtml