[Winpcap-users] problem using winpcap 3.1 with windows service

[Loris Degioanni]

All the changes in WinPcap versions are listed at the follwing page:

http://www.winpcap.org/misc/changelog.htm

Loris


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