0x000000d1 error in TdiReturnChainedReceives

NTDEV
1

Hi:

As per the DDK, TSDUs passed into the ClientEventChainedReceive handler
may be released at a later point in time by returning STATUS_PENDING from
the handler and later calling TdiReturnChainedReceives on the tsdu
descriptor.

I did the same and passed the second parameter of the function as 0x01
saying that the descriptor list array had one element. This caused the
error mentioned. When I pass 0x0 as the number of elements at the
descriptor list, there is no error. I have not been able to explain this.
Does not the descriptor list actually point to an NDIS_PACKET and if that
is the case the number of elements in the descriptor list must be atleast
one?

KK

2

What is the first parameter you are passing? Is it Tsdu or an address of
Tsdu? You should pass the address of Tsdu.

-Srin.

-----Original Message-----
From: Keshab Koch [mailto:xxxxx@india.nsc.com]
Sent: Tuesday, May 27, 2003 11:41 PM
To: NT Developers Interest List
Subject: [ntdev] 0x000000d1 error in TdiReturnChainedReceives

Hi:

As per the DDK, TSDUs passed into the ClientEventChainedReceive
handler
may be released at a later point in time by returning STATUS_PENDING
from
the handler and later calling TdiReturnChainedReceives on the tsdu
descriptor.

I did the same and passed the second parameter of the function as 0x01
saying that the descriptor list array had one element. This caused the
error mentioned. When I pass 0x0 as the number of elements at the
descriptor list, there is no error. I have not been able to explain
this.
Does not the descriptor list actually point to an NDIS_PACKET and if
that
is the case the number of elements in the descriptor list must be
atleast
one?

KK

You are currently subscribed to ntdev as: xxxxx@nai.com
To unsubscribe send a blank email to xxxxx@lists.osr.com