Hi all, as version string shows when you substitute Npcap with new versions, it easily caused confusion when a user installs it. So I have updated the version to 0.03 in all exe, dll and sys files.
On Mon, Jul 27, 2015 at 3:19 PM, Yang Luo <hslu...@gmail.com> wrote: > Hi list, > > Thanks for your tests for the first two versions of Npcap, I have fixed > several problems as following: > 1) Npcap causes BSoD if you uninstall Npcap when Npcap is still in use for > capturing packets. > 2) Npcap can't start the driver automatically when system reboots in 0.02, > now I have added this feature back. > 3) Npcap lose many packets for loopback capturing in 0.02, like TCP data > packets. Now I have fixed it and tested against TCP data transmission, UDP > data transmission and Apache HTTP server (XAMPP). > 4) "Npcap Loopback Adapter" can be successfully renamed in Win10. > 5) Npcap can see MB miniport adapter now. > > The latest Npcap installer is: > https://svn.nmap.org/nmap-exp/yang/NPcap-LWF/npcap-nmap-0.03.exe > > I have tested this version Npcap under Wireshark 1.12.6 x64, in Windows > 8.1 x64 and Windows 10 Insider Preview 10240 x64. > > Notice: > 1) You need to try it under Win7 and later, and no need to change the > installation options, just click the "Next"s. Npcap installed in "WinPcap > Compatible Mode" is exclusive with WinPcap, so you must uninstall WinPcap > first (installer will prompt you this). > 2) If you have installed WinPcap, better to reboot the PC after > uninstalling Winpcap and then install Npcap. > > The README is: > https://github.com/nmap/npcap > > > Cheers, > Yang >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: https://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
