Problem in inf file characteristics value with winpk filter

Home Forums Discussions Support Portal Problem in inf file characteristics value with winpk filter

This topic contains 7 replies, has 2 voices, and was last updated by  vikashm05 4 years, 3 months ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #5380

    vikashm05
    Participant

    Hi ,

    I am using a inf file for installation of my driver using LAN properties but i am facing the following problems during installation of my driver with winpk filter installation:

    All these changes are done with windows 2008 R2 Server 64 bit .
    Problem1:

    1)Install winpk filter software.
    2)After installation of winpk filter, i am trying to install my certified driver using LAN properties but it is not properly installed .Inside LAN properties it shows two icons of winpk filter installed on my system instead of one.

    Solution of two winpk filetr icons:

    1)we have changed the characteristics value in inf file from 0x40000 to 0x4410.Using 0x4410, It installed properly via LAN properties.

    2)We have also done some changes in inf file related to certification and we make a un certified build and install it using DISABLE DRIVER SIGNATURE ENFORCEMENT properties.

    3)After installing winpk filter and committed some changes in inf file like Characteristics=0x4410 ,it installed properly.

    But when we tried to install using this inf file(Characteristics=0x4410), without winpk filter driver is not installed properly and parameters in not updated in registry properly.

    problem2:

    1)when i prepared a installer using same inf file which contains Characteristics=0x4410 value and install it after winpk installation ,my driver parameters is not added in registry and also in LAN properties there is no any icons comes related to my driver.

    >>using same inf file , it was installed via LAN properties.

    Note:When i have installed the same installer on windows 64 bit machine , it installed properly and icons also comes in LAN properties but all parameters is not updated in registry.

    Please inform the desired solution and behavior of different Characteristics values.

    #7099

    Vadim Smirnov
    Moderator

    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?

    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.

    You are using NCF_NDIS_PROTOCOL|NCF_FILTER|NCF_NO_SERVICE = 0x4410, which an example can be used for the protocol part of NDIS IM driver.

    So, if you are trying to install NDIS LWF driver you have to use NCF_LW_FILTER, if NDIS Intermediate then NCF_NDIS_PROTOCOL|NCF_FILTER|NCF_NO_SERVICE.

    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.

    #7100

    vikashm05
    Participant

    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

    #7101

    Vadim Smirnov
    Moderator

    You should use 0x40000 for LWF driver for system to install and start driver properly.

    To eliminate compatibility issue with original standard WinpkFilter LWF you have to generate new GUID and replace it in both

    NetCfgInstanceId present in my INF file is NetCfgInstanceId=”{5cbf81bd-5055-47cd-9055-a76b2b4e3697}”

    and

    #define FILTER_UNIQUE_NAME L”{5cbf81bd-5055-47cd-9055-a76b2b4e3697}” //unique name, quid name

    Then rebuild LWF driver.

    #7102

    vikashm05
    Participant

    Again Thanks a lot for your quick reply but i have one more question i.e. mentioned below:

    1)How generate new GUID .

    2)How to change it in winpk filter after generating a new GUID :

    #define FILTER_UNIQUE_NAME L”{5cbf81bd-5055-47cd-9055-a76b2b4e3697}” //unique name, quid name

    Because we are using a winpk filter installer and source code is not available for compilation after doing these changes.

    #7103

    Vadim Smirnov
    Moderator

    @vikashm05 wrote:

    1)How generate new GUID .

    You can use guidgen utility to generate new GUID.

    @vikashm05 wrote:

    2)How to change it in winpk filter after generating a new GUID :

    Change INF file and string in common.h. Then just rebuild LWF drivers.

    #7104

    vikashm05
    Participant

    As per my understanding GUID and NetCfgInstanceId are same .

    Now, i am able to generate a new GUID using tool and also changed this value in my code .

    One more question i want to ask i.e.:

    When i install my services using INF file via LAN properties, it properly installed and value is also updated in registry.

    But when i prepare a uncertifed installer using my .sys, .pdb and changed .inf file, it installed on my system but all registry parameters is not updated in registry.These parameters are updated using my code .sys file.

    So, i want to ask is there in any difference if we installed same file using LAN properties and using installer.Also is there any difference in certified build and insatllation of uncertifed build through disable driver signature enforcement.

    Regards,
    Vikash

    #7105

    vikashm05
    Participant

    Hi,

    Please also let me know ,whether NetCfgInstanceId is also used for changing parameter in registry .

    NetCfgInstanceId is responsible for changing any parameters in registry or not.

    Thanks,

    Vikash

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.