Strange.
The main purpose of the list passed to NdisOpenAdapter() is to tell to NDIS which adapters the protcol supports. This information is used by NDIS to make the bindings: if for example a protocol specifies only NdisMedium802_3, it will be installed only over ethernet adapters. Therefore, if the packet driver doesn't specify NdisMedium802_5, it *should* not be installed by the system over token-ring adapters. But in this case it has been installed. Don't ask me the reason.
Loris.
-----Messaggio Originale-----
Da: Guy Harris <gharris@xxxxxxxxxxxx>
A: <DORLINGB@xxxxxxxxxx>
Cc: <ethereal-users@xxxxxxxx>
Data invio: mercoled� 9 agosto 2000 9.38
Oggetto: Re: [ethereal-users] Using Ethereal on an IBM Thinkpad with Ethernet and TRN cards with Win95
> On Wed, Aug 09, 2000 at 09:20:34AM +0200, DORLINGB@xxxxxxxxxx wrote:
> > Later I had to reinstall and the token ring card was installed at that
> > time.
> > Well WINPCAP bound itself to the TRN card too and all seemed to be OK. A
> > few days later when
> > I restarted the Thinkpad it hung on boot. Turns out that the problem was
> > that WINPCAP
> > was bound to the TRN card, when I removed it all was OK again.
>
> WinPcap doesn't support token ring currently.
>
> Fulvio, could the fact that the current packet drivers (on both NT and
> 9x) don't specify NdisMedium802_5 in the list passed to
> "NdisOpenAdapter()" cause this?
>