Forum Replies Created
-
Posts
-
You can use VirtNet under Windows x64 if disable driver signing requirement (press F8 during system boot and choose Disable Driver Signature Enforcement option) or you can use test signing for VirtNet driver.
For the cross platform compatibility WinpkFilter driver returns adapter names as ANSI strings (actually only ANSI set used for internal adapter names). On user mode level you can operate with UNICODE strings if needed, just remember that strings from driver are in ANSI.
It may happen if your packet processing code is incredibly slow. In this case internal driver packets queue reaches its maximum size and all newly coming packets are dropped.
If you use high speed connection I recommend to use ReadPackets API instead ReadPacket (refer PackThru sample) and optimize your packet processing code.
WinpkFilter 3.0.6 released. This service release includes the bugfix for WinpkFilter NDIS IM driver (BSOD on restoring from Hibernate state on Windows Vista).
Important note:
For Windows Vista and later versions of the Windows family of operating systems, kernel-mode software must have a digital signature to load on x64-based computer systems. WinpkFilter drivers are not signed and in order to test them on Vista x64 you should press F8 during system boot and choose Disable Driver Signature Enforcement option. For the commercial software you’d have to obtain Code Signing certificate from Verysign or another Certificate Authority authorized by Microsoft.If you are eligible for a free update, please send the following details to [email protected] tо receive an update instruction:
1) Your order ID.
2) An approximate date of purchasing.Try installing NDIS IM variant of WinpkFilter driver. Most probably you have another NDIS hooking driver installed by third-party firewall of AV software, which does conflict with WinpkFilter.
Sometimes reboot is required, sometimes not. That depends if network stack can reconfigure dynamically or not.
If you try to install WinpkFilter run-time on the fresh copy of Windows XP x64 under Administrator account you should not meet any problems. I don’t know what was the particular reason for the automatic installation to fail, may be lack of privilege to install the driver, may be previous version of WinpkFilter was installed before and was not completely removed before reinstall, may be something else.
WinpkFilter 3.0.5 released:
1) fixed compatibility issue with Kaspersky software
2) added API for getting active WAN connections information
3) added API for sending/receiving bulk of packetsImportant note:
For Windows Vista and later versions of the Windows family of operating systems, kernel-mode software must have a digital signature to load on x64-based computer systems. WinpkFilter drivers are not signed and in order to test them on Vista x64 you should press F8 during system boot and choose Disable Driver Signature Enforcement option. For the commercial software you’d have to obtain Code Signing certificate from Verysign or another Certificate Authority authorized by Microsoft.If you are eligible for a free update, please send the following details to [email protected] to receive an update instruction:
1. Your order ID.
2. An approximate date of purchasing.
