dvsing

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: winpkfilter – Vista x64 SP1 compatible? #6600
    dvsing
    Participant

      I’ve been using the latest version available from this website – downloaded it a couple days ago. 3.0.4.0 I think.

      -Dan

      in reply to: winpkfilter – Vista x64 SP1 compatible? #6598
      dvsing
      Participant

        I’m not sure if this was an SP1 issue or just a Vista issue in general, but I figured out a fix for it.

        For a little background, I’m using Vista SP1 x64 which means that I have to use the F8 boot menu option to ‘disable driver signature enforcement’ in order to use the winpkfilter driver unsigned.

        The problem was that after the login/password screen was displayed, the UI would freeze if I had booted using this F8 option with the WinPkFilter driver installed. Not using the F8 option to disable signature enforcement means that the WinPkFilter driver doesn’t get loaded and this was the only way I was able to log back into the system (by preventing the driver from loading).

        The work-around is to boot into vista with diver signature enforcement enabled (normal boot) and open the Device Manager. Under the “Network adapters” tree you should see three “WAN Miniport (xxx) – WinpkFilter Miniport” devices: IP, IPv6, and Network Monitor. Right click each of these and disable them. This will not affect the usability of WinPkFilter.

        My guess is that WinPkFilter is being installed such that it is binding to some adapters that are incompatible with it. This seems to fix the problem.

        Also, as a side note, if you’re annoyed about having to hit F8 every time on boot to disable driver signature enforcement, there is an option: you can test-sign the driver yourself and enable the loading of test signed drivers. Instructions on doing this are available here:

        http://www.rage3d.com/board/showthread.php?t=33920573

        -Dan

        in reply to: OpenFilterDriver fails.. help! #6365
        dvsing
        Participant

          Working!!!

          I figured out the problem. There was one project option that seemed to cause it to suddenly work. Your ListAdapters program uses a Multi-Byte character set whereas the c++ Visual Studio 2005 default character set is unicode. I bet this was causing a problem with OpenFilterDriver because the default string being passed didn’t hook up with the driver properly (you could probably shed more light on the exact reason why).

          Anyhow, I think we’re in business now – thank you!

          -Dan

          in reply to: OpenFilterDriver fails.. help! #6364
          dvsing
          Participant

            ok… Has this successfully been used with Microsoft Visual Studio 2005 on a 64-bit platform?

            -Dan

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