Hi,

>
> Hi all !
>
> 1.  The *final* version of V3.0 (as downloaded from the website)
>     reports itself (PacketGetVersion() call) as "3.0 alpha 3",
>     which is probably not what we want :)

I have already fixed this issue. From next version of packet.dll
PacketGetVersion() will look at the version number of the dll binary instead
of printing a static string.

>     --> I suggest the string be changed to "3.0 (platform)", so,
>         "3.0 (Win95) Beta 3", "3.0 (Win2000) Alpha 1" and so on.
>   This would give the calling application some hint about
>         what can be done with the platform its running on.

A probably better alternative if you need system-dependent code is to use
the GetVersion() Win32 API function.

> 2.  While running a simple test app on Win95, it seems that many
>     things don't work there, or no longer work.  Was the Packet 9x
>     driver ever updated to the Ntx core?

What kind of things?
>From the main page of the documentation:

" Our development and documentation efforts focus primarily on the Windows
NT/2000/XP version of WinPcap. This choice is based on the fact that the
majority of the WinPcap users work on NTx systems, but also that the 9x
technology has been abandoned by Microsoft. Moreover, we assume that a
person that needs to use a PC for an advanced task like network analysis
installs an advanced OS on the machine. For this reason, this documentation
will refer to the WinNTx drivers and APIs. Win9x versions are very similar
in the concept but sometimes differ in the implementation, moreover the
Win9x version of the API lack of some sophisticated functionality."

>     On Win95:
>
> NETLIB: using NPF/PACKET version 3.0 alpha3
> INTERFACE  Ethernet Address   IP / MASK / BCAST
> eth5       00:60:97:4a:84:a4  10.0.0.0, 255.0.0.0, 10.255.255.255
> eth3       00:00:00:00:00:00  10.0.0.0, 255.0.0.0, 10.255.255.255
> eth2       44:45:53:54:00:01  10.0.0.0, 255.0.0.0, 10.255.255.255
> eth1       44:45:53:54:00:01  10.0.0.0, 255.0.0.0, 10.255.255.255
>
>     On Win2000:
>
> NETLIB: using NPF/PACKET version 3.0 alpha3
> INTERFACE  Ethernet Address   IP / MASK / BCAST
> eth1       00:02:b3:89:6a:8d  10.0.95.146, 255.255.255.0, 10.0.95.255
> eth0       00:d0:59:37:b4:5c  10.0.24.82, 255.255.255.0, 10.0.24.255
>
>     It looks the PacketGetNetInfo() call isnt't behaving properly on the
>     Win9X driver...

The bug is probably due to some problem in the routine that scans the
registry. As I wrote before, since we have limited resources we focus on the
WinNTx version of the library, so I can't grant we'll able to look at this
issue in the short period. Obviously, we gladly accept patches.

Loris

> Cheers,
> Fred



==================================================================
 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