Thanks SerpentFly……
Please find my comments mentioned below:
From your post it is not clear what kind of driver do you try to install along with WinpkFilter. Is it NDIS LWF, NDIS IM or protocol driver?
>>I am trying to install NDIS LWF.
Characteristics to use in INF depend on the type of your driver. For Windows Vista and higher WinpkFilter installs NDIS LWF filter driver and corresponding Characteristics value is NCF_LW_FILTER = 0x40000.
>>it’s ok but when i try to install my driver after installing winpk filter driver, it creates a problem and my driver is not visible using Characteristics value is NCF_LW_FILTER = 0x4000
when i change this Characteristics value to 0x4410, my driver is installed properly and it is visble in services list.
So, i have no idea why it gives an error using Characteristics value is NCF_LW_FILTER = 0x4000.
If you are trying to create the custom build of WinpkFilter NDIS LWF then besides changing driver name please note to generate new GUID to be used in common.h and in INF file (NetCfgInstanceId). This value uniquely identifies filter driver instance.
>>NetCfgInstanceId present in my INF file is NetCfgInstanceId=”{5cbf81bd-5055-47cd-9055-a76b2b4e3697}”
But i am not able to find GUID value inside common.h .i found only NetCfgInstanceId value inside common.h which is mentioned as :
#define FILTER_UNIQUE_NAME L”{5cbf81bd-5055-47cd-9055-a76b2b4e3697}” //unique name, quid name
So, please specify me i am wrong.
My major concern is Characteristics value because :
1)if winpk filter is not installed , my driver is installed properly with Characteristics value is 0x40000.
2)If if winpk filter is installed , my driver is not installed properly with Characteristics value is 0x40000.
3)if winpk filter is installed , my driver is installed properly with Characteristics value is 0x4410.
Thanks,
Vikash