Post by alisonb on Nov 19, 2006 6:12:58 GMT -5
If I use v0.4.0.0 (debug version, special build for Alan), I have no problems in the IDE of vb6sp6.
If I use v1.0.0.1 (the latest version) I get the Bad DLL calling convention error previously reported, when in the IDE, but not when compiled.
However, both versions cause XPSP2 (on my 2 PC's at least) to generate an error when STOPPING packet capture, and give an error associated with oleaut32.dll.
Any idea as to what may be happening ? I see the latest version is created using Dev C++ and Mingw compiler, is it possible for me to have the source code so I can try to compile it myself and investigate the problem ?
Many thanks, Alison
If I use v1.0.0.1 (the latest version) I get the Bad DLL calling convention error previously reported, when in the IDE, but not when compiled.
However, both versions cause XPSP2 (on my 2 PC's at least) to generate an error when STOPPING packet capture, and give an error associated with oleaut32.dll.
Any idea as to what may be happening ? I see the latest version is created using Dev C++ and Mingw compiler, is it possible for me to have the source code so I can try to compile it myself and investigate the problem ?
Many thanks, Alison