1) WinpkFilter NDIS hooking variant is installed directly through the registry. snetcfg is only applicable to NDIS IM variant of WinpkFilter. Which driver have actually used?
Im installing driver with snetcfg with ndisrd.inf and ndisrd_m.inf parameters but im using ndis hooking driver with delphi
2) What version of WinpkFilter have you used? Prior 3.0.4 WinpkFilter NDIS IM driver may have meet problems with loopback packets processing which would cause the similar crash. This was fixed in 3.0.4.
I used 3.0.2.1 version of ndisrd.sys
3) What Windows version have you used? I’ve quickly tested Windows XP 32 bit with IPX installed and have not noticed problems with both NDIS IM and NDIS hooking drivers.
I used Windows XP (both old and updated versions) on large network. Aprox. 70 pc on LAN with IPX. Winpk installed all of the machines. I started a machine successfully. There is no problem if only 1 machine uses same physical network with IPX and winpk driver. When I bootup the second pc with same sw configuration(IPX and winpk) both of the machine crashes with bluescreen.
4) If you have any firewall(even integrated with AV)/VPN software installed then please let us know the name and the version, since this can be a software driver conflict.
I dont use any fw or vpn software. Also windows fw disabled.
I dont know another way of installing driver. I tried to write values into registery with my own installer, I got some errors on different machines with windows xp. How can I do clear install hooking driver automatically? Is there another script or etc? like snet cfg