Post by c0de7 on Jun 30, 2007 17:38:15 GMT -5
I encountered the same "Bad DLL Calling Convention" when I tried to compile a project that uses VBPCAP in Visual Basic. This error happens only when you run the code from the Visual basic IDE. When compiled into an exe there is no error. Microsoft says that THIS IS A BUG.(the exe should give the same error, but it doesn't)
Anyway, I managed to modify the source code of VBPCAP.dll. I added the __stdcall prefix to all functions and modified the localtime function(Visual Studio 2005 does not convert const time_t * to * long by default).
Anyone interested in the new DLL just contact me at lucian_code7@yahoo.com. (or Yahoo Messenger)
VBPCAP is great! Thanks to the author!
I understood that the source code available for download is for VBPCAP 0.4. Is that true? That means that the new DLL, with stdcall correction is the equivalent of VBPCAP 0.4.
I would like to see the source code for the latest VPPCAP release, please! Lorenzo please update the source code(and contact me)!
Thank you!
Anyway, I managed to modify the source code of VBPCAP.dll. I added the __stdcall prefix to all functions and modified the localtime function(Visual Studio 2005 does not convert const time_t * to * long by default).
Anyone interested in the new DLL just contact me at lucian_code7@yahoo.com. (or Yahoo Messenger)
VBPCAP is great! Thanks to the author!
I understood that the source code available for download is for VBPCAP 0.4. Is that true? That means that the new DLL, with stdcall correction is the equivalent of VBPCAP 0.4.
I would like to see the source code for the latest VPPCAP release, please! Lorenzo please update the source code(and contact me)!Thank you!