Hi Robert, <<Are you sure you have WinPcap 3.1 beta 2?>>
Yes. <<The message you are referring to is produced by line 962 in file AdInfo.c=20 which is in function PacketGetAdapters(). =20>> No, it was emanating from Packet32.DLL, at base address $00002078. I am saying "was" in definite terms because I just hand-patched a copy of PACKET32.DLL to replace the setup and call to MessageBox() with twenty-two $90's (NOPs), and my application runs fine now with no error messages. For anyone else reading this list, I should hasten to point out that I am using only a _very_ small sub-set of the WinPcap functions, mainly pcap_next_ex() and pcap_sendpacket(). So I know the basic functioning of Packet32 is intact despite the lack of an installed TCP-IP driver, and ignoring this error. I note also that other WinPcap functions apparently rely on the TCP-IP driver, because Ethereal will not run properly with the patched DLL. So no way could I openly recommend this hack to anyone else... it's just a temporary way for me to mask the driver's intended behavior, until I can take the time to research the matter further. Hmm.... I wonder how difficult it would be to just temporarily hook the kernel's MessageBox() code, and discard that particular call from Packet32? I do hate to have a patched DLL on my machine for any length of time. Any suggestions, anyone? Rob--- ----------------------------------------------------------------- LapTwo Technology Corporation Phone: 763-633-9434 16820 Highway 10, Suite 130 Fax: 253-276-2755 Elk River, Minnesota 55330 http://www.laptwo.com ----------------------------------------------------------------- ================================================================== This is the WinPcap users list. It is archived at http://www.mail-archive.com/[EMAIL PROTECTED]/ To unsubscribe use mailto: [EMAIL PROTECTED] ==================================================================
