Windows Vista Tips

Windows Vista Tips > Newsgroups > Windows Vista Drivers > IM driver not receiving packets for Intel NIC

Reply
Thread Tools Display Modes

IM driver not receiving packets for Intel NIC

 
 
jyotsna
Guest
Posts: n/a

 
      12-06-2004
I have a IM driver working fine with all the NIC's accept Intel
series.

I tried to set ProtocolReceivePacket to NULL as specified in DDK
document.

But yet ProtocolReceive routine is not called.

I kept both the routines none of them is getting called.

Moreever when i send OID request
OID_GEN_MAXIMUM_LOOKAHEAD,OID_GEN_MAC_OPTIONS ,
OID_802_3_MAXIMUM_LIST_SIZE , OID_GEN_MAXIMUM_FRAME_SIZE,
OID_GEN_CURRENT_PACKET_FILTER the other NIC invokes PtRequestComplete
with correct value od OID, but for Intel card it invokes
PtRequestComplete for that many times but with OID value of last
request.

Has anybody got any clue??

Thanks in Advance
Jyotsna
 
Reply With Quote
 
 
 
 
Pavel A.
Guest
Posts: n/a

 
      12-06-2004
"jyotsna" wrote:
> Moreever when i send OID request
> OID_GEN_MAXIMUM_LOOKAHEAD,OID_GEN_MAC_OPTIONS ,
> OID_802_3_MAXIMUM_LIST_SIZE , OID_GEN_MAXIMUM_FRAME_SIZE,
> OID_GEN_CURRENT_PACKET_FILTER the other NIC invokes PtRequestComplete
> with correct value od OID, but for Intel card it invokes
> PtRequestComplete for that many times but with OID value of last
> request.


Can you please elaborate on this?
Miniports always handle OIDs one by one and not in parallel.
How have you managed to run several requests without waiting them to complete?

--PA


 
Reply With Quote
 
jbijargi@gmail.com
Guest
Posts: n/a

 
      12-07-2004
Thanks for reply Pavel

In PtBindAdapter after NdisOpenAdapter i am calling NdisRequest for all
above OID's.

Please let me know if i am doing something wrong. and also what is the
correct method of doing.

Thanks in Advace
Jyotsna

 
Reply With Quote
 
Thomas F. Divine [DDK MVP]
Guest
Posts: n/a

 
      12-07-2004
The article "Extending the PassThru NDIS IM Driver Sample" at the Windows
Driver Developer's Digest illustrates how an NDI SIM driver can make it's
own autonomous calls to NdisRequest to query OIDs that it may need.

Good luck,

Thomas F. Divine, Windows DDK MVP
http://www.pcausa.com

<> wrote in message
news: oups.com...
> Thanks for reply Pavel
>
> In PtBindAdapter after NdisOpenAdapter i am calling NdisRequest for all
> above OID's.
>
> Please let me know if i am doing something wrong. and also what is the
> correct method of doing.
>
> Thanks in Advace
> Jyotsna
>



 
Reply With Quote
 
Jyotsna
Guest
Posts: n/a

 
      12-07-2004
Sir can you please send me the link of article.


Sending the log also.

For working NIC
=======================================
SendLinkRequest->NdisRequest - Oid = 10105, Len = 4
PtRequestComplete - Oid = 10105
Query Request Completed 10105 Status 0
OID_GEN_MAXIMUM_LOOKAHEAD 200 Status 0

SendLinkRequest->NdisRequest - Oid = 10113, Len = 4
PtRequestComplete - Oid = 10113
Query Request Completed 10113 Status 0
OID_GEN_MAC_OPTIONS f Status 0

SendLinkRequest->NdisRequest - Oid = 1010104, Len = 4
PtRequestComplete - Oid = 1010104
Query Request Completed 1010104 Status 0
OID_802_3_MAXIMUM_LIST_SIZE 20 Status 0

SendLinkRequest->NdisRequest - Oid = 10106, Len = 4
PtRequestComplete - Oid = 10106
Query Request Completed 10106 Status 0
OID_GEN_MAXIMUM_FRAME_SIZE 5dc Status 0

SendLinkRequest->NdisRequest - Oid = 10107, Len = 4
PtRequestComplete - Oid = 10107
Query Request Completed 10107 Status 0

SendLinkRequest->NdisRequest - Oid = 10109, Len = 4
PtRequestComplete - Oid = 10109
Query Request Completed 10109 Status 0

SendLinkRequest->NdisRequest - Oid = 1010e, Len = 4
PtRequestComplete - Oid = 1010e
Query Request Completed 1010e Status 0
OID_GEN_CURRENT_PACKET_FILTER 0 Status 0

SendLinkRequest->NdisRequest - Oid = 1010e, Len = 4
PtRequestComplete - Oid = 1010e
Set Information Request Completed 1010e Status c00000bb
=======================================

for Intel
=======================================
SendLinkRequest->NdisRequest - Oid = 10105, Len = 4
SendLinkRequest->NdisRequest - Oid = 10113, Len = 4
SendLinkRequest->NdisRequest - Oid = 1010104, Len = 4
SendLinkRequest->NdisRequest - Oid = 10106, Len = 4
SendLinkRequest->NdisRequest - Oid = 10107, Len = 4
SendLinkRequest->NdisRequest - Oid = 10109, Len = 4
SendLinkRequest->NdisRequest - Oid = 1010e, Len = 4
SendLinkRequest->NdisRequest - Oid = 1010e, Len = 4

PtRequestComplete - Oid = 1010e
PtRequestComplete - Oid = 1010e
PtRequestComplete - Oid = 1010e
PtRequestComplete - Oid = 1010e
PtRequestComplete - Oid = 1010e
PtRequestComplete - Oid = 1010e
PtRequestComplete - Oid = 1010e
PtRequestComplete - Oid = 1010e
=======================================

Thanks in Advance
Jyotsna
 
Reply With Quote
 
Jyotsna
Guest
Posts: n/a

 
      12-07-2004
Thanks a lot.
The problem of no reply to OID is solved.
Now i get correct reply to OID's as i am waiting until OID request is
completed.

But the main problem of not receiving the packets is still persisting.
Can you suggest someway to check where exactly is the problem.

Thanks in Advance
Jyotsna

"Pavel A." wrote:

> "jyotsna" wrote:
> > Moreever when i send OID request
> > OID_GEN_MAXIMUM_LOOKAHEAD,OID_GEN_MAC_OPTIONS ,
> > OID_802_3_MAXIMUM_LIST_SIZE , OID_GEN_MAXIMUM_FRAME_SIZE,
> > OID_GEN_CURRENT_PACKET_FILTER the other NIC invokes PtRequestComplete
> > with correct value od OID, but for Intel card it invokes
> > PtRequestComplete for that many times but with OID value of last
> > request.

>
> Can you please elaborate on this?
> Miniports always handle OIDs one by one and not in parallel.
> How have you managed to run several requests without waiting them to complete?
>
> --PA
>
>

 
Reply With Quote
 
Jyotsna
Guest
Posts: n/a

 
      12-08-2004
hi

I am having the working IM driver for Intel on windows98.
The MAJOR_NUMBER of driver is 5 for 98 while it is 4 for 2k.
for 2k it has to be 4 since we are using NDISWAN.

Is it the problem because of this. should i change to CoNDISWAN and
MAJOR_NUMBER 5.
And if i have to do that, what changes will be required.
Please can anyone help me out.

Thanks in Advance
Jyotsna

"Jyotsna" wrote:

> Thanks a lot.
> The problem of no reply to OID is solved.
> Now i get correct reply to OID's as i am waiting until OID request is
> completed.
>
> But the main problem of not receiving the packets is still persisting.
> Can you suggest someway to check where exactly is the problem.
>
> Thanks in Advance
> Jyotsna
>
> "Pavel A." wrote:
>
> > "jyotsna" wrote:
> > > Moreever when i send OID request
> > > OID_GEN_MAXIMUM_LOOKAHEAD,OID_GEN_MAC_OPTIONS ,
> > > OID_802_3_MAXIMUM_LIST_SIZE , OID_GEN_MAXIMUM_FRAME_SIZE,
> > > OID_GEN_CURRENT_PACKET_FILTER the other NIC invokes PtRequestComplete
> > > with correct value od OID, but for Intel card it invokes
> > > PtRequestComplete for that many times but with OID value of last
> > > request.

> >
> > Can you please elaborate on this?
> > Miniports always handle OIDs one by one and not in parallel.
> > How have you managed to run several requests without waiting them to complete?
> >
> > --PA
> >
> >

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
the INF Update Utility - Primarily for Intel® 4, 3, 900 Series Chipsets are the same Intel Driver Chipset for Vista and XP? rebelscum0000 Windows Vista General Discussion 19 06-25-2008 03:41 PM
INTEL DRIVER CHIPSET INF Update Utility - Primarily for Intel® 4, 3, 900 Series Chipsets (2455KB) 9.0.0.1008 6/2/2008 are the same Intel Driver Chipset for Vista and XP? rebelscum0000 Windows Vista General Discussion 5 06-25-2008 04:32 AM
the INF Update Utility - Primarily for Intel® 4, 3, 900 Series Chipsets are the same Intel Driver Chipset for Vista and XP? rebelscum0000 Windows Vista General Discussion 1 06-24-2008 09:57 PM
NDIS-WDM driver receives concatenated packets Harshal Chhaya Windows Vista Drivers 2 12-01-2004 04:28 PM
Ndiswanip packets not seen on an IM driver with QoS Packet Scheduler on XP google@spandya.mailshell.com Windows Vista Drivers 1 06-03-2004 01:25 AM



1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59