I don't understand clearly the advantage in looking under "Windows
NT\CurrentVersion\NetworkCards" rather than under
"{4D36E972-E325-11CE-BFC1-08002BE10318}".
Does current solution miss some adapters?
Moreover, Windows keeps information about the adapters in several different
locations in the registry, and often the position of those locations and
their content changes from one version to another. This is the reason of the
complexity of PacketGetAdapterNames(). I accept suggestions about the best
(and more stable) location to use.
Loris
>Hello winpcap users,
>
>with older versions of packet.DLL , there was no probem to find the
adapters cards.
>-> the pack was registered as a protocol/service linked with each card we
needed.
>->this work fine !
>
>
>in versions WinPcap_3_0_a4. and 2.3
>in packet.dll , function PacketGetAdapterNames work :
> a.. read the registry
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E972-E325-11C
E-BFC1-08002BE10318}
> b.. read the tcpip linkage .....
> c.. services ...
>is there a way to simplify this in reading only :
> under windowsNT (NT,2000,XP)
>
> read the adapter list in register :
("HKEY_LOCAL_MACHINE\\Software\\Microsoft\\Windows
NT\\CurrentVersion\\NetworkCards")
> under (windows 95,98)
> read the adapter list in register :
("HKEY_LOCAL_MACHINE\\System\\CurrentControlSet\\Services\\Class\\Net")
>and register the service NPF_**** from adapters found by this way ????
>
>Thanks...
==================================================================
This is the WinPcap users list. It is archived at
http://www.mail-archive.com/winpcap-users@;winpcap.polito.it/
To unsubscribe use
mailto: [EMAIL PROTECTED]?body=unsubscribe
==================================================================
