NDIS Intermediate Driver Question(IMSAMP, PASSTHRU)

NTDEV
1

Hi everybody

I have a few questions regarding these samples, if anybody can help
please.

  1. When using the protocol reserved area of NDIS_PACKET, there seems to be
    confusion as to the sizes these can be. 16 bytes or more than 16 bytes that
    is the question?. Can somebody clarify the size that this “variable field
    can be” on both NT4 and W2K for both sends and receives?

  2. On these samples a lot of packets seem to get lost by the upper
    protocols namely TCP/IP? Is this a Known issue.

  3. On some NT4 platforms, especially when running on 3C509 Etherlink III
    cards, The cards seem to stop transmitting, and sometimes receiving. If you
    then leave the P.C. for a while, and ping it all starts working again.
    It gives the impression that NDIS has run out of PACKETS/memory. Is there
    any way of tracing this !!. I have seen that somebody knows how to enable
    NDIS tracing… Is this also a Known issue or can somebody help in tracing
    NDIS?

Thanks , in advance

Any help greatly received.

Steve

xxxxx@bemac.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

2

Refer to KB articles Q164459 and Q229660 for details on enabling NDIS and NDISWAN tracing -

Regards,

Ed Lau

MidCore Software, Inc.
900 Straits Tpke
Middlebury, CT 06762

www.midcore.com

----- Original Message -----
From: xxxxx@bemac.com
To: NT Developers Interest List
Sent: Tuesday, May 22, 2001 7:26 AM
Subject: [ntdev] NDIS Intermediate Driver Question(IMSAMP, PASSTHRU)

Hi everybody

I have a few questions regarding these samples, if anybody can help
please.

  1. When using the protocol reserved area of NDIS_PACKET, there seems to be
    confusion as to the sizes these can be. 16 bytes or more than 16 bytes that
    is the question?. Can somebody clarify the size that this “variable field
    can be” on both NT4 and W2K for both sends and receives?

  2. On these samples a lot of packets seem to get lost by the upper
    protocols namely TCP/IP? Is this a Known issue.

  3. On some NT4 platforms, especially when running on 3C509 Etherlink III
    cards, The cards seem to stop transmitting, and sometimes receiving. If you
    then leave the P.C. for a while, and ping it all starts working again.
    It gives the impression that NDIS has run out of PACKETS/memory. Is there
    any way of tracing this !!. I have seen that somebody knows how to enable
    NDIS tracing… Is this also a Known issue or can somebody help in tracing
    NDIS?

Thanks , in advance

Any help greatly received.

Steve

xxxxx@bemac.com

You are currently subscribed to ntdev as: xxxxx@midcore.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

3

----- Original Message -----
From:
To: NT Developers Interest List
Sent: Tuesday, May 22, 2001 7:26 AM
Subject: [ntdev] NDIS Intermediate Driver Question(IMSAMP, PASSTHRU)

> Hi everybody
>
>
> I have a few questions regarding these samples, if anybody can help
> please.
>
>
> 1. When using the protocol reserved area of NDIS_PACKET, there seems to be
> confusion as to the sizes these can be. 16 bytes or more than 16 bytes
that
> is the question?. Can somebody clarify the size that this “variable field
> can be” on both NT4 and W2K for both sends and receives?
>
>
The Windows 2000 DDK documentation has been systematically revised to show
the correct value: “at least 16 bytes”. This applies to Windows NT as well.

I am also having fits with 3Com adapters of several varieties…

Regards,

Thomas F. Divine

PCAUSA - Toolkits & Resources For Network Software Developers
NDIS Protocol - NDIS Intermediate - TDI Client
http: - http:

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com</http:></http:>

4

> 1. When using the protocol reserved area of NDIS_PACKET, there seems to be

confusion as to the sizes these can be. 16 bytes or more than 16 bytes
that
is the question?. Can somebody clarify the size that this “variable field
can be” on both NT4 and W2K for both sends and receives?

This data area can be the arbitrary size you have specified in (IIRC)
NdisAllocatePacketPool.
It is recommended to keep all packet-related data there without allocating
any additional memory chunks. The lesser times you call ExAllocatePool, the
better.

Max

You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

5

Thanks a mill…

Steve

xxxxx@bemac.com
-----Original Message-----
From: Ed Lau
To: NT Developers Interest List
Date: Tuesday, May 22, 2001 2:33 PM
Subject: [ntdev] Re: NDIS Intermediate Driver Question(IMSAMP, PASSTHRU)

Refer to KB articles Q164459 and Q229660 for details on enabling NDIS and NDISWAN tracing -

Regards,

Ed Lau

MidCore Software, Inc.
900 Straits Tpke
Middlebury, CT 06762

www.midcore.com

----- Original Message -----
From: xxxxx@bemac.com
To: NT Developers Interest List
Sent: Tuesday, May 22, 2001 7:26 AM
Subject: [ntdev] NDIS Intermediate Driver Question(IMSAMP, PASSTHRU)

Hi everybody

I have a few questions regarding these samples, if anybody can help
please.

1. When using the protocol reserved area of NDIS_PACKET, there seems to be
confusion as to the sizes these can be. 16 bytes or more than 16 bytes that
is the question?. Can somebody clarify the size that this “variable field
can be” on both NT4 and W2K for both sends and receives?

2. On these samples a lot of packets seem to get lost by the upper
protocols namely TCP/IP? Is this a Known issue.

3. On some NT4 platforms, especially when running on 3C509 Etherlink III
cards, The cards seem to stop transmitting, and sometimes receiving. If you
then leave the P.C. for a while, and ping it all starts working again.
It gives the impression that NDIS has run out of PACKETS/memory. Is there
any way of tracing this !!. I have seen that somebody knows how to enable
NDIS tracing… Is this also a Known issue or can somebody help in tracing
NDIS?

Thanks , in advance

Any help greatly received.

Steve

xxxxx@bemac.com

—
You are currently subscribed to ntdev as: xxxxx@midcore.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com —
You are currently subscribed to ntdev as: xxxxx@bemac.com
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com

—
You are currently subscribed to ntdev as: $subst(‘Recip.EmailAddr’)
To unsubscribe send a blank email to leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com