Hi
David,
Thanks
for the response.
I
agree that this is a cool feature, and I want to change my NDIS IM driver
(which currently needs INF files and must be signed my Microsoft) to behave the
same way.
Are
you suggesting that I could load my driver dynamically from an App if I call
the same functions you outlined below? No need to digitally sign my
driver with MS?
Roger
-----Original Message-----
From: David Barnish [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 4:27 PM
To: [EMAIL PROTECTED]
Subject: RE: [WinPcap-users] What kind of Windows driver is Winpcap?The PacketOpenAdapter() function in packet32.c reads the Windows Registry to see if the required entries needed for the driver are there. If they are not found, it calls PacketInstallDriver() which calls CreateService() to create the service on the system. This will place the entries into the Registry. PacketOpenAdapter() then uses various Service Control Manager function calls to start the driver. This all works fine if the driver file is already in the correct directory. If not, the PacketOpenAdapter() call will fail. Most drivers do not do this, but this is a very cool feature of this driver.Thank you,
David Barnish-----Original Message-----
From: Roger Tragin [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 05, 2003 3:12 PM
To: '[EMAIL PROTECTED]'
Subject: [WinPcap-users] What kind of Windows driver is Winpcap?Hi,I have written NDIS Intermediate drivers before for W2K and it required INF files and had to be signed. However, Winpcap does not. Looks like the App dynamically loads it when needed. How is this so?--
Roger Tragin
