Dear Winpcap team:

We have been using Winpcap for awhile to provide our customers with a demo
of Treck TCP, a Win32 port of our embedded TCP/IP Internet protocol
products, which normally does not run on top of MS-Windows but instead runs
in an embedded system with or without a RTOS. Our Win32 Treck demo
(http://www.treck.com/TreckDemo.zip) works fine with winpcap versions 2.3,
3.0 and 3.01.a (and probably other versions). However, I just tried running
our Win32 Treck demo with the latest version of winpcap (3.1 beta 4), and it
crashes because you have removed the function PacketGetNetInfo and it
appears added a new function PacketGetNetInfoEx in its place. Can you please
keep the old function PacketGetNetInfo when you add the new function
PacketGetNetInfoEx, that way you are backwards-compatible with earlier
versions of winpcap (and then won't break other applications that call the
older winpcap API PacketGetNetInfo)?

Thanks.
- Ed Remmell

Treck, Inc. (formerly Elmic Systems, USA)

Best of Show Winner, ESC 2003


-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.300 / Virus Database: 265.6.11 - Release Date: 1/12/2005
 


---
Treck, Inc. -  Confidentiality Notice
 
This electronic transmission may contain information that is proprietary or 
confidential.  You are hereby notified that any dissemination, distribution or 
duplication of this electronic transmission to some other entity, without the 
expressed written consent of Treck, Inc.  is strictly prohibited, unless the 
contents of this electronic transmission specifically authorizes you to do so.  
If your receipt of this electronic transmission is in error, please notify the 
corporate offices of Treck, Inc.  immediately by  calling (513) 528-5732, or by 
reply to this transmission.
 



================================================================= This is the 
WinPcap users list. It is archived at
 http://www.mail-archive.com/[email protected]/

 To unsubscribe use
 mailto: [EMAIL PROTECTED]
=================================================================

Reply via email to