[Winpcap-users] Npcap 0.04, based on original WinPcap 4.1.3, call for test

[食肉大灰兔V5]

I have fixed the PATH empty issue by using a custom strlen-8192 version of
NSIS, see installer at:
https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-1.00.exe


Cheers,
Yang

On Fri, Sep 11, 2015 at 12:07 AM, Pascal Quantin <pascal.quantin at gmail.com>
wrote:

>
>
> 2015-09-10 17:44 GMT+02:00 食肉大灰兔V5 <hsluoyz at gmail.com>:
>
>> Hi,
>>
>> The first reason I think is that the original WinPcap uses the NSIS
>> installer, as Npcap tries to keep as much as possible with WinPcap, Npcap
>> also uses NSIS. Moreover, Nmap also uses NSIS. As for why don't use MSI, I
>> think this is because open-source projects (like WinPcap, Npcap, etc) tend
>> to not use commercial software (like MSI). There should be some reasons
>> about this.
>>
>
> Nowadays there is an open source project named WiX allowing you to create
> MSI. But it requires you to create a brand new installer from scratch, and
> it seems to be more complex to use (at least that's my first feeling but
> people are reluctant to learn new things ;) ).
>
> Cheers,
> Pascal.
>
>
>>
>> Cheers,
>> Yang
>>
>> On Thu, Sep 10, 2015 at 7:55 PM, Petr Lázňovský <lazna at volny.cz> wrote:
>>
>>> Maybe dubm question, but why not create MSI package, de-facto standard
>>> in installations for windows?
>>>
>>> L.
>>>
>>> > Presumably the issue comes from the NSIS EnvVarUpdate macro used by
>>> Npcap installer when having a long %PATH% variable, as explained here:
>>> > http://sourceforge.net/p/nsis/bugs/1046/
>>> > and
>>> >
>>> http://nsis.sourceforge.net/Environmental_Variables:_append%2C_prepend%2C_and_remove_entries
>>>
>>> > Looks like the method used to update it should be changed...
>>>
>>> > Pascal.
>>>
>>>
>>>
>>> > 2015-09-10 10:18 GMT+02:00 食肉大灰兔V5 <hsluoyz at gmail.com>:
>>>
>>> > Hi,
>>>
>>>
>>> > Like the installer said: "Npcap detected you have installed WinPcap,
>>> in order to Install Npcap in WinPcap API-compatible Mode, you must
>>> uninstall WinPcap first.". So I would suggest you uninstall WinPcap first
>>> before trying Npcap in WinPcap API-compatible Mode.
>>>
>>>
>>> > Cheers,
>>> > Yang
>>>
>>>
>>> > On Thu, Sep 10, 2015 at 4:14 PM, Petr Lázňovský <lazna at volny.cz>
>>> wrote:
>>>
>>> > This option is inactive, see screenshoot.
>>> >
>>> >  L.
>>> >
>>>
>>> >  So you should ALWAYS has "Install Npcap in WinPcap API-compatible
>>> Mode" option checked when installing Npcap (which is the default option).
>>> > _______________________________________________
>>> >  Winpcap-users mailing list
>>> >  Winpcap-users at winpcap.org
>>> >  https://www.winpcap.org/mailman/listinfo/winpcap-users
>>> >
>>>
>>>
>>> >
>>> > _______________________________________________
>>> >  Winpcap-users mailing list
>>> >  Winpcap-users at winpcap.org
>>> >  https://www.winpcap.org/mailman/listinfo/winpcap-users
>>> >
>>>
>>>
>>> _______________________________________________
>>> Winpcap-users mailing list
>>> Winpcap-users at winpcap.org
>>> https://www.winpcap.org/mailman/listinfo/winpcap-users
>>>
>>
>>
>> _______________________________________________
>> Winpcap-users mailing list
>> Winpcap-users at winpcap.org
>> https://www.winpcap.org/mailman/listinfo/winpcap-users
>>
>>
>
> _______________________________________________
> Winpcap-users mailing list
> Winpcap-users at winpcap.org
> https://www.winpcap.org/mailman/listinfo/winpcap-users
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20150911/27865028/attachment-0001.html>