Bad DLL Call Convention Error

[heixian]

Hello everybody,

I just install the VB-PCAP following VBPCAP doc 1.0. But after I install the Winpcap and copy the VB-PCAP dll file to the system32 folder, I still can't run the test application in the VBPCAP package.

It has the run time error 49: bad dll call convention.

I use VB6 in XP (SP2). When I debug the error. it direct me to the formMain .frm file, and highlight the function 'vpGetAdapterInfo i, d' in the form_load sub.

Does anybody know what's going on?

Thanks

[Lorenzo VBPCAP Founder]

Hi Heixian,

you get a strange error check the file you are using. Download the version 1.0 of vbpcap form www.lorenzocerulli.tk i've tested with vb 6.0 sp6 and it works perfectly. If you are running apps in IDE mode try to compile it first cause somethimes vb 6 does some STRANGE things.

If the problem persist please try to use the vbGetAdapterInfoVB5 function instead of the one you mentioned .

if the problem still presist please write me:
1.VB6 version and sp
2.Windows Verison and SP
3.winpcap version
4. Report exactly the error string and the window title
ragards
Lorenzo

[heixian]

Hello Lorenzo:

The error is still and same, not matter I use vbGetAdapterInfoVB5 or vpGetAdapterInfo function

What I downloaded vbpcap is version 1.0. The full name of the package is: 7-2.VBPCAP_1.0_toRelease.zip. What I did is just simple open the test application inside this pakcage and run it with VB6.

In the IDE mode the I got a run time error: bad DLL calling convention.

If I use the VB6 to create the .exe file for vbpcapTest application. It will run, but I there is no text in the dropdown menu in the vbpcap test form. And I will get the error message box: "Errore applicazione syntax error" when I click start button in the vbpcapTest form.

Here is my development enviroment:

1. VB6 with enterprise version with SP6
2. Windows XP with SP2
3. WinPcap_3_1.exe

The error string (runing from IDE mode): Run time error '49': Bad DLL calling convention.
window title: Microsoft Visual Basic

If run from vbpcapTest.exe file, error string: Errore applicazione syntax error
window tilte: vbcap Test

[jdomnitz]

try registering the dll in the system32 folder

[goodcarrot]

I got that message, too.


Try to compile, not to run on the IDE environment.

Then, it will work correctly


(But there are some difficulties to debug your code)

[stevem]

Hello Heixian,

Previously, I was using PacketX (beesync.com), but it has a bug when reporting more than one IP address per interface and therefore I cannot use it. I reported this bug to them a month or so ago but.....

Therefore I had a bit of a look at vb-pcap.

I had the same issue. No matter what I could not figure out what the problem was.

As I had to modify the source code to get a list of all IP addresses from an interface, I compiled it on my machine to see how it would go. I then found it would work ok in IDE.

I have since added small amount of code to provide a list of IP address(s) for an interface and it works fantastic.

Thanks Lorenzo. Not bad for "just a VB programmer"

Steve

[Lorenzo VBPCAP Founder]

Tnx Steve ;D

However i'm going to release vbpcap source code version 1.0.3 so if u feel to release the code you added to vbpcap i'll include it in the new version



tnx in advance
lorenzo

[frigolit]

I must say, I also received that error, in the IDE.
But it works if compiled to an EXE.
Hope you find what's causing this error

[jdomnitz]

Any word on the code to display adapter IP's? That would be a great feature...

[imperceptus]

There is an issue with using the latest version of PCAP according to some calls that were removed. Uninstall your version and install version 2.3 of Win Pcap. that did the job for me.

[baz]

Hi
I was beginning to think this forum was dead
I had problems trying to move the DLL to \system32 and regging it.
But all that needs to be done is to leave it in the directory where your creating the VB app
Works every time (for me)
WinpCap 3.0 for me, had problems with later versions although i can't remember what they were now although something about selecting NIC's and generic drivers seems to ring a bell.