<html>Sorry for the late reply, but FYI adding "NM" and "NPF" to list dependeny list fixed the problem. Thanks!<br>
<br>
Michael Ryan<br>
PCSentinel Software<br>
http://www.pcsentinelsoftware.com<br>
<br>
>-----Original Message-----<br>
>From: Bryan Kadzban [mailto:bryan@kadzban.is-a-geek.net]<br>
>Sent: Thursday, September 8, 2005 05:43 PM<br>
>To: winpcap-users@winpcap.org<br>
>Subject: Re: [Winpcap-users] problem using winpcap 3.1 with windows service<br>
><br>
>Michael Ryan wrote:<br>
>> First, Bryan and Arno, thanks for the suggestions and help. My <br>
>> service does link directly to the wcap.dll, and it is not part of a <br>
>> group.<br>
>> <br>
>> In the scenario described below and by Bryan earlier, is there any <br>
>> way my service can depend on NPF directly and avoid the middle <br>
>> service?<br>
><br>
>In your service's registry key, add a REG_MULTI_SZ named<br>
>"DependOnServices" (or possibly "DependOnService"; I don't remember for<br>
>sure, so check out some of the other service keys on your machine and<br>
>use whatever value-name they use). You'll have to use regedt32 if you<br>
>do this on a 2K Pro box, but XP's regedit can handle it just fine.<br>
><br>
>The data is a list of service names ( == names of registry keys) that<br>
>your service should depend on. Add "NM" and "NPF" to this list (the<br>
>names are case-insensitive), because those are the registry keys for the<br>
>"Network Monitor driver" driver and the "Netgroup Packet Filter" driver.<br>
><br>
>You'll need both, because wpcap.dll links against packet.dll, which<br>
>links against wanpacket.dll, which calls LoadLibrary on the Netmon<br>
>client DLL, which tries to start the "nm" driver if it isn't already<br>
>running.<br>
></html>