Hi,
I need to detect when device driver (any kind of device) is going to load, but at very first steps (before driver has loaded). Also I need to know what kind of device is connecting.
Is there any API for this?
Should I develop a filter driver for this?
Thanks for your help.
What bigger problem are you trying to solve? The hardware a pnp driver is loading for is not known by that driver until the driver’s AddDevice() is called
From: xxxxx@gmail.commailto:xxxxx
Sent: ?9/?14/?2014 8:06 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: [ntdev] Device connection detection
Hi,
I need to detect when device driver (any kind of device) is going to load, but at very first steps (before driver has loaded). Also I need to know what kind of device is connecting.
Is there any API for this?
Should I develop a filter driver for this?
Thanks for your help.
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>
Hello Doron,
I understand that the exact hardware is not known. But can I know the class of the device?
After AddDevice() called the driver fully loaded and functional, or there are other steps to perform?
As I understand driver should get IRP_MN_START_DEVICE to start working.
No. What bigger problem are you trying to solve?
d
Bent from my phone
From: xxxxx@gmail.commailto:xxxxx
Sent: ?9/?15/?2014 1:01 AM
To: Windows System Software Devs Interest Listmailto:xxxxx
Subject: RE:[ntdev] Device connection detection
Hello Doron,
I understand that the exact hardware is not known. But can I know the class of the device?
After AddDevice() called the driver fully loaded and functional, or there are other steps to perform?
As I understand driver should get IRP_MN_START_DEVICE to start working.
—
NTDEV is sponsored by OSR
Visit the list at: http://www.osronline.com/showlists.cfm?list=ntdev
OSR is HIRING!! See http://www.osr.com/careers
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer</mailto:xxxxx></mailto:xxxxx>
xxxxx@gmail.com wrote:
After AddDevice() called the driver fully loaded and functional, or there are other steps to perform?
As I understand driver should get IRP_MN_START_DEVICE to start working.
You are over-generalizing here, and that tells me you do not understand
your problem domain.
The driver can start doing work in its DriverEntry, just as soon as it
is loaded into memory. That happens even before the dispatch tables are
set up. The driver can continue to do work in its AddDevice. In most
cases it can’t yet talk to its hardware (assuming it has hardware), but
the driver is still fully alive and functional.
As Doron has asked, you should try to tell us what larger task you are
trying to accomplish here. I suspect you are attempting to build yet
another ill-fated security product. If so, you’re doing it the wrong way.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.