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 <[email protected]>: > 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ý <[email protected]> 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 > [email protected] > https://www.winpcap.org/mailman/listinfo/winpcap-users > > > _______________________________________________ > Winpcap-users mailing list > [email protected] > https://www.winpcap.org/mailman/listinfo/winpcap-users > _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users
