我一直致力于检测USB插入/移除。我已经使用CreateWindowEx()实现了代码,并通过我的窗口进程回调传递了WNCLASSEX。在插入和删除我的usb时,我成功收到WM_DEVICECHANGE消息,但wParam始终设置为DBT_DEVNODES_CHANGED。
我从来没有得过DBT_DEVICEARRIVAL或DBT_DEVICEREMOVECOMPLETE。我一直在使用我得到的东西,但我真的需要能够分辨出设备到达和移除之间的区别,这样我就可以根据收到的内容采取不同的行动。
现在,我必须在收到DBT_DEVNODES_CHANGED之后放一个计时器,然后测试系统上是否有新的可移动设备,或者我的列表中是否有任何新的可移动设备。我确定这不对,所以我想我会问。我宁愿摆脱计时器,只是收到这两条消息。这对我必须做的事情有很大帮助。有什么建议吗?
这是我用于注册回调的代码,以及回调本身:
注意:2015年3月12日:更新代码以显示实际GUID和DoRegisterDeviceInterfaceToHwnd()函数的定义。):
GUID WceusbshGUID = { 0x25dbce51, 0x6c8f, 0x4a72, 0x8a,0x6d,0xb5,0x4c,0x2b,0x4f,0xc8,0x35 };
//GUID WusbrawGUID = {0xa5dcbf10, 0x6530, 0x11d2, 0x90, 0x1f, 0x00, 0xc0, 0x4f, 0xb9, 0x51, 0xed };
//GUID WusbGUID = {0x88BAE032, 0x5A81, 0x49f0, 0xBC, 0x3D, 0xA4, 0xFF, 0x13, 0x82, 0x16, 0xD6 };
INT_PTR WINAPI WinProcCallback(HWND __hWnd, UINT message, WPARAM wParam, LPARAM lParam);
BOOL DoRegisterDeviceInterfaceToHwnd(GUID InterfaceClassGuid, HWND __hWnd, HDEVNOTIFY *hDeviceNotify);
bool UsbController::startNotifyUsbAddedRemoved(QString &errmsg)
{
WNDCLASSEX wndClass;
wndClass.cbSize = sizeof(wndClass);
wndClass.style = 0;
wndClass.hInstance = reinterpret_cast<HINSTANCE>(GetModuleHandle(0));
wndClass.lpfnWndProc = reinterpret_cast<WNDPROC>(WinProcCallback);
wndClass.cbClsExtra = 0;
wndClass.cbWndExtra = 0;
wndClass.hIcon = LoadIcon(0, IDI_APPLICATION);
wndClass.hbrBackground = (HBRUSH)(COLOR_WINDOW+1);
wndClass.hCursor = LoadCursor(0, IDC_ARROW);
wndClass.lpszClassName = WND_CLASS_NAME;
wndClass.lpszMenuName = NULL;
wndClass.hIconSm = LoadIcon(0, IDI_APPLICATION);
if (!RegisterClassEx(&wndClass))
{
FormatErrorMsg("RegisterClassEx: ", errmsg);
return false;
}
HINSTANCE hInstance = (HINSTANCE)::GetModuleHandle(NULL);
__hWnd = CreateWindowEx(
WS_EX_CLIENTEDGE | WS_EX_APPWINDOW,
WND_CLASS_NAME,
WND_APP_NAME,
WS_OVERLAPPEDWINDOW, // style
CW_USEDEFAULT, 0,
0, 0,
NULL, NULL,
hInstance,
NULL);
if ( __hWnd == NULL )
{
FormatErrorMsg("CreateWindowEx: ", errmsg);
return false;
}
return true;
}
INT_PTR WINAPI WinProcCallback(HWND __hWnd, UINT message, WPARAM wParam, LPARAM lParam)
{
LRESULT lRet = 1;
static HDEVNOTIFY hDeviceNotify;
static HWND hEditWnd;
static ULONGLONG msgCount = 0;
switch (message)
{
case WM_CREATE:
//
// This is the actual registration., In this example, registration
// should happen only once, at application startup when the window
// is created.
//
// If you were using a service, you would put this in your main code
// path as part of your service initialization.
//
if ( ! DoRegisterDeviceInterfaceToHwnd( WceusbshGUID, __hWnd, &hDeviceNotify) )
{
// Terminate on failure.
//ErrorHandler(TEXT("DoRegisterDeviceInterfaceToHwnd"));
ExitProcess(1);
}
//
// Make the child window for output.
//
hEditWnd = CreateWindow(TEXT("EDIT"),// predefined class
NULL, // no window title
WS_CHILD | WS_VISIBLE | WS_VSCROLL |
ES_LEFT | ES_MULTILINE | ES_AUTOVSCROLL,
0, 0, 0, 0, // set size in WM_SIZE message
__hWnd, // parent window
(HMENU)1, // edit control ID
(HINSTANCE) GetWindowLong(__hWnd, GWL_HINSTANCE),
NULL); // pointer not needed
if ( hEditWnd == NULL )
{
// Terminate on failure.
ExitProcess(1);
}
// Add text to the window.
SendMessage(hEditWnd, WM_SETTEXT, 0,
(LPARAM)TEXT("Registered for USB device notification...\n"));
break;
case WM_SETFOCUS:
SetFocus(hEditWnd);
break;
case WM_SIZE:
// Make the edit control the size of the window's client area.
MoveWindow(hEditWnd,
0, 0, // starting x- and y-coordinates
LOWORD(lParam), // width of client area
HIWORD(lParam), // height of client area
TRUE); // repaint window
break;
case WM_DEVICECHANGE:
{
//
// This is the actual message from the interface via Windows messaging.
// This code includes some additional decoding for this particular device type
// and some common validation checks.
//
// Note that not all devices utilize these optional parameters in the same
// way. Refer to the extended information for your particular device type
// specified by your GUID.
//
// Output some messages to the window.
UsbController *pusbctl;
switch (wParam)
{
case DBT_DEVICEARRIVAL:
msgCount++;
pusbctl = UsbController::instance();
pusbctl->signalDeviceArrival();
break;
case DBT_DEVICEREMOVECOMPLETE:
msgCount++;
pusbctl = UsbController::instance();
pusbctl->signalDeviceRemoval();
break;
case DBT_DEVNODES_CHANGED:
msgCount++;
pusbctl = UsbController::instance();
pusbctl->signalDeviceAddedRemoved();
break;
default:
msgCount++;
break;
}
}
break;
default:
// Send all other messages on to the default windows handler.
lRet = DefWindowProc(__hWnd, message, wParam, lParam);
break;
}
return lRet;
}
BOOL DoRegisterDeviceInterfaceToHwnd(GUID InterfaceClassGuid, HWND __hWnd, HDEVNOTIFY *hDeviceNotify)
{
DEV_BROADCAST_DEVICEINTERFACE NotificationFilter;
ZeroMemory( &NotificationFilter, sizeof(NotificationFilter) );
NotificationFilter.dbcc_size = sizeof(DEV_BROADCAST_DEVICEINTERFACE);
NotificationFilter.dbcc_devicetype = DBT_DEVTYP_DEVICEINTERFACE;
//NotificationFilter.dbcc_devicetype = DEVICE_NOTIFY_ALL_INTERFACE_CLASSES;
NotificationFilter.dbcc_classguid = InterfaceClassGuid;
*hDeviceNotify = RegisterDeviceNotification(
__hWnd, // events recipient
&NotificationFilter, // type of device
DEVICE_NOTIFY_WINDOW_HANDLE // type of recipient handle
);
if ( NULL == *hDeviceNotify )
{
return FALSE;
}
return TRUE;
}
答案 0 :(得分:10)
如果你阅读MSDN的文档,它会说:
Detecting Media Insertion or Removal
当新设备或媒体(如CD或DVD)添加并可用时,以及删除现有设备或媒体时,Windows会向所有顶级窗口发送一组默认 WM_DEVICECHANGE消息。您无需注册即可接收这些默认消息。 请参阅RegisterDeviceNotification中的“备注”部分,了解默认情况下发送的消息的详细信息。
RegisterDeviceNotification function
具有顶级窗口的任何应用程序都可以通过处理WM_DEVICECHANGE消息来接收基本通知。应用程序可以使用RegisterDeviceNotification函数注册以接收设备通知 ...
DBT_DEVICEARRIVAL和DBT_DEVICEREMOVECOMPLETE事件自动广播到端口设备的所有顶级窗口。因此,没有必要为端口调用RegisterDeviceNotification,如果dbch_devicetype成员是 DBT_DEVTYP_PORT ,则函数将失败。
DBT_DEVTYP_PORT
0x00000003端口设备(串行或并行)。此结构是DEV_BROADCAST_PORT结构。
USB设备不是串行/并行端口。它是一个设备接口(DBT_DEVTYP_DEVICEINTERFACE
)。默认情况下,DBT_DEVICEARRIVAL
设备不会发送DBT_DEVICEREMOVECOMPLETE
/ DBT_DEVTYP_DEVICEINTERFACE
。如果您需要,则必须使用RegisterDeviceNotification()
来请求它们。
看起来您的代码基于此MSDN示例:
Registering for Device Notification
在该代码中,WceusbshGUID
被定义为{25dbce51-6c8f-4a72-8a6d-b54c2b4fc835}
,被评为 USB串行主机PnP驱动程序的类guid。根据这个MSDN页面:
System-Defined Device Setup Classes Available to Vendors
该guid是 Windows CE USB ActiveSync设备的类guid(与代码中使用的Wceusb...
前缀更一致)。对于 USB设备(所有不属于其他类 的USB设备),同一页面上的{88BAE032-5A81-49f0-BC3D-A4FF138216D6}
也是如此。
以下CodeProject文章:
Detecting Hardware Insertion and/or Removal
提及{{1>} USB裸设备。同样的guid在MSDN上被记录为GUID_DEVINTERFACE_USB_DEVICE
(其命名可能源于XP类命令和界面guid was not well separated的命名之前。)
因此,当您使用特定的类guid调用{a5dcbf10-6530-11d2-901f-00c04fb951ed}
时,请确保它是正确的类guid,因为您将获取设备事件只有特定的类型的设备。您的USB设备可能正在使用与您注册的类别不同的类别guid,这就是您没有获得预期的设备事件的原因。
如果你想检测任何 USB设备而不管其类guid(并且定义了几个USB类guid),你可以在调用{{1}时使用RegisterDeviceNotification()
标志然后类guid将被忽略。在DEVICE_NOTIFY_ALL_INTERFACE_CLASSES
和RegisterDeviceNotification()
消息中(假设您现在可以获取它们),报告的DBT_DEVICEARRIVAL
将告诉您实际的类guid,并且报告的DBT_DEVICEREMOVECOMPLETE
将开始使用dbcc_classguid
前缀。
最后一件事 - 如果在您的应用已经运行时插入/移除USB设备,您只会收到dbcc_name
条消息。要检测应用启动时是否已插入USB设备,您必须使用SetupAPI个功能(\\?\USB:
,DBT_DEVICE...
,SetupDiGetClassDevs()
等来枚举可用的功能设备