Visual Basic Errors

Home › Forums › Discussions › Support › Visual Basic Errors

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • January 4, 2006 at 9:15 pm #4972
    Malph
    Participant

      Hi, i’m trying to use NDISAPI with Visual Basic 6.0 but i have some problems ^^

      The samples in the packages try to call the function “OpenFilterDriver” that doesnt exist in the Library. Some others functions doesnt respect the functions declarations presented in the Help.

      Moreover, i tried to add a Reference to the DLL … But Visual Basic refuses to link it …

      I think the Sample isn’t up to date with the current DLL Version ^^

      Is there a way to use this DLL with Visual Basic ? 🙂

      Thx for answers 🙂

      January 5, 2006 at 9:33 am #5871
      Vadim Smirnov
      Keymaster

        Yes, you are right; there are problems with using the ndisapi.dll binary included within the WinplFilter package. The problem was caused by moving the NDISAPI project from one building environment to another so the routines exported through the DEF file were not exported anymore (this binary also is not possible to use with Delphi). We appreciate you report, WinpkFilter packages with fixed ndisapi.dll binary will be available for download in the next few days.

        Fixed binary also available for download from the following link http://www.ntkernel.com/downloads/ndisapi.zip

        Since WinpkFilter 3.0 we provide the complete source code for the ndisapi.dll in the freely available packages because of different building environments you may have to use. So, you can modify/port/rebuild the ndisapi.dll or even integrate it into your application.

        Some others functions doesnt respect the functions declarations presented in the Help.

        Could you please provide the details?

        January 5, 2006 at 8:47 pm #5872
        Vadim Smirnov
        Keymaster

          ndisapi.dll binary in the WinpkFilter demo package was fixed. Thanks for reporting this problem.

          January 5, 2006 at 9:11 pm #5873
          Malph
          Participant

            Thx for the update, but i have some errors :

            ➡ In PacketSniffer Project, a Fatal Error shut down VB at line 65 in frmMain ( GetTcpipBoundAdaptersInfo nHandle, AdList )
            This line works well in the ListAdapters Project.

            I can bypass the problem if I declare a local variable like :

            ‘Get TCP/IP bound adapters information
            Dim AdList2 As TCP_AdapterList
            GetTcpipBoundAdaptersInfo nHandle, AdList2
            AdList = AdList2

            No fatal error … but some lines later, the program go on these errors :

            “Failed to get current packet filter from the network interface”
            “Failed to set promiscuous mode fro the network interface.”

            Then, no packet are captured.
            (we can notice the ‘fro’ instead of ‘for’ 😉 )

            I just want to notice, that when i use the binpacketsniffer.exe its working well.

            ➡ In the ListAdapters Project i’v notice some errors on the display screen. The MAC Address for my Ethernet Card return : “00000000” instead of it real value. When i use the binListAdapters the correct value is given.

            When i spy the adapterHandle value, it is 0
            Request.hAdapterHandle = AdList.m_nAdapterHandle(nIndex)

            So I think this is the source of the problem ^^

            I didnt found why this is 0, but i’ll search a bit waiting for your response 😉

            Thanks a lot for your precedent fast answers. I’ll say to you if i find some other bugs 🙂

          • Author
            Posts
          Viewing 4 posts - 1 through 4 (of 4 total)
          • You must be logged in to reply to this topic.