When will Ndis call MiniportReset ?

NTDEV
1

Hi Devs,
2K DDK says

  1. "NDIS does not call a deserialized NIC driver’s MiniportReset function
    if the driver’s MiniportSend or MiniportSendPackets function seems to have
    timed out "
  2. "For A miniport driver that has a WDM lower edge, MiniportCheckForHang
    is not specified in DriverEntry. The miniport driver can rely on NDIS to
    determine if its miniport instance is hung, based on sends and requests that
    timeout so this routine is not required. "

Now in case of Deserialized NIC Miniport driver with WDM Lower edge, that
does not provide a MiniportCheckForHang routine, What are the scenarios in
which Ndis will call MiniportReset ?

Regards
Anandhi

Disclaimer:
This document is intended for transmission to the named recipient only. If
you are not that person, you should note that legal rights reside in this
document and you are not authorized to access, read, disclose, copy, use or
otherwise deal with it and any such actions are prohibited and may be
unlawful. The views expressed in this document are not necessarily those of
HCL Technologies Ltd. Notice is hereby given that no representation,
contract or other binding obligation shall be created by this e-mail, which
must be interpreted accordingly. Any representations, contractual rights or
obligations shall be separately communicated in writing and signed in the
original by a duly authorized officer of the relevant company.

2

Anandhi,

Please remove your “Disclaimer” if you need an answer here.

Stephan

On Tue, 26 Feb 2002 19:16:22 +0530, “Anandhi Dhanabalan - CTD,
Chennai.” wrote:

>Hi Devs,
>2K DDK says
>1) "NDIS does not call a deserialized NIC driver’s MiniportReset function
>if the driver’s MiniportSend or MiniportSendPackets function seems to have
>timed out "
>2) "For A miniport driver that has a WDM lower edge, MiniportCheckForHang
>is not specified in DriverEntry. The miniport driver can rely on NDIS to
>determine if its miniport instance is hung, based on sends and requests that
>timeout so this routine is not required. "
>
>Now in case of Deserialized NIC Miniport driver with WDM Lower edge, that
>does not provide a MiniportCheckForHang routine, What are the scenarios in
>which Ndis will call MiniportReset ?
>
>Regards
>Anandhi
>
> Disclaimer:
>This document is intended for transmission to the named recipient only. If
>you are not that person, you should note that legal rights reside in this
>document and you are not authorized to access, read, disclose, copy, use or
>otherwise deal with it and any such actions are prohibited and may be
>unlawful. The views expressed in this document are not necessarily those of
>HCL Technologies Ltd. Notice is hereby given that no representation,
>contract or other binding obligation shall be created by this e-mail, which
>must be interpreted accordingly. Any representations, contractual rights or
>obligations shall be separately communicated in writing and signed in the
>original by a duly authorized officer of the relevant company.

3

** Reply to message from xxxxx@hotmail.com (Stephan Wolf) on Tue, 26 Feb 2002
15:56:05 GMT

Please remove your “Disclaimer” if you need an answer here.

Actually, Stephan, you just broke HCL Technologies Ltd’s law since you
obviously accessed, read, disclosed (by quoting here), and copied (again by
posting here) the message. But did you USE the message? I’m going to try to
get a ruling from legal on what might be included with “otherwise deal with it.”
I probably broke the law when I hit the DEL key to trash the original. Of
course, that was after I accessed and read it :-(. I guess we’re all screwed!
Oh, wait a minute, the disclaimer later says that it creates no “representation,
contract or other binding obligation,” so maybe we’re ok. Except that I just
disclosed and copied that, and I had to read it again to double check.

I just love these kinds of disclaimers. “If I screwed up and sent this to you
by mistake, it’s your fault, and you must fix the problem for me or I’ll sue
you!” How about, “please forgive the intrusion?”

Sincerely,

Chris Myers
Senior Project Engineer
Quatech, Inc.

4

On Tue, 26 Feb 2002 11:17:57 -0500, Chris Myers
wrote:

> Actually, Stephan, you just broke HCL Technologies Ltd’s law since you
>obviously accessed, read, disclosed (by quoting here), and copied (again by
>posting here) the message.

Will I be fined now…? :frowning:

But seriously, I don’t like “disclaimers” and such in public forums
(ok, this one isn’t really “public” in a way). It always looks like
“all that’s being said can, and will, be used against you”.

I think we’re all trying to, and it’s the “spirit of the internet” (at
least, it used to be…), help each other here. So omit disclaimers or
go away…

Stephan

5

No one broke any LAWS here. Your company can put whatever they want on
their disclaimers, but it has no real legal weight and is certainly not LAW!
It’s your company’s stated position to prosecute, but hell, I can sue you
for just about anything.

Greg

-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com]On Behalf Of Chris Myers
Sent: Tuesday, February 26, 2002 10:18 AM
To: NT Developers Interest List
Subject: [ntdev] Re: When will Ndis call MiniportReset ?

** Reply to message from xxxxx@hotmail.com (Stephan Wolf) on Tue, 26 Feb
2002
15:56:05 GMT

Please remove your “Disclaimer” if you need an answer here.

Actually, Stephan, you just broke HCL Technologies Ltd’s law since you
obviously accessed, read, disclosed (by quoting here), and copied (again by
posting here) the message. But did you USE the message? I’m going to try
to
get a ruling from legal on what might be included with “otherwise deal with
it.”
I probably broke the law when I hit the DEL key to trash the original. Of
course, that was after I accessed and read it :-(. I guess we’re all
screwed!
Oh, wait a minute, the disclaimer later says that it creates no
“representation,
contract or other binding obligation,” so maybe we’re ok. Except that I
just
disclosed and copied that, and I had to read it again to double check.

I just love these kinds of disclaimers. “If I screwed up and sent this to
you
by mistake, it’s your fault, and you must fix the problem for me or I’ll sue
you!” How about, “please forgive the intrusion?”

Sincerely,

Chris Myers
Senior Project Engineer
Quatech, Inc.

You are currently subscribed to ntdev as: xxxxx@pdq.net
To unsubscribe send a blank email to %%email.unsub%%

6

** Reply to message from “Gregory G. Dyess” on Tue, 26 Feb
2002 16:31:25 -0600

> No one broke any LAWS here. Your company can put whatever they want on
> their disclaimers, but it has no real legal weight and is certainly not LAW!
> It’s your company’s stated position to prosecute, but hell, I can sue you
> for just about anything.

Greg: HELLO!?!?
I’m not sure what’s funnier, the original message I was MAKING FUN OF, or your
reply here.

Sincerely,

Chris Myers
Senior Project Engineer
Quatech, Inc.

7

>

On Tue, 26 Feb 2002 11:17:57 -0500, Chris Myers
> wrote:
>
> > Actually, Stephan, you just broke HCL Technologies
> Ltd’s law since you
> >obviously accessed, read, disclosed (by quoting here), and
> copied (again by
> >posting here) the message.
>
> Will I be fined now…? :frowning:

Greg, was right. No one broke the law, the disclaimer said "This document is
intended for transmission to the named recipient only. "
So it means this document was intended for NT-devForum and all its
subscribers.
Stephan U don’t have to worry! U’ll not be fined ;o)

> But seriously, I don’t like “disclaimers” and such in public forums
> (ok, this one isn’t really “public” in a way). It always looks like
> “all that’s being said can, and will, be used against you”.

Agreed! Looks like I am getting a lot of help/ideas on disclaimers instead
of the real issue, anyway I’ll take up the help, from here on U’ll not see
any disclaimers in my mail

>
> I think we’re all trying to, and it’s the “spirit of the internet” (at
> least, it used to be…), help each other here.

True HELP is what we are all here to give and receive, And “HELP” - if
possible without spamming subscribers mailbox. (Of course even this mail of
mine falls in such a category, but I don’t have choice. Sorry about it
people! )

> So omit disclaimers or go away…
Gosh! I thought this was a “public” forum!!!

Best Regards :o)
Anandhi

8

Ok, enough philosophy - back to work:

Hmm, in “2)”, you omitted the word “typically”, ie. “[…] this routine
is not typically required” (http://www.osr.com/ddk/212nonds_8ns7.htm).

IMHO, in general, the whole concept of MiniportReset() is a braindead
idea and is AFAIK a relict from the Token-Ring firmware interface of
the late 80s. [Why should any higher-level protocol or application
ever issue a hardware reset request to an underlying driver? This is
like reading from a file and if there’s an error, issuing a hard disk
reset from an application - wrong layer.]

Anyway, if you do not want NDIS to reset your driver then consider one
or more of the following:

  • ignore the reset request by simply returning
    NDIS_STATUS_NOT_RESETTABLE or NDIS_STATUS_SUCCESS from MiniportReset()

  • stop NDIS from timing out any driver requests by specifying
    NDIS_ATTRIBUTE_IGNORE_PACKET_TIMEOUT and
    NDIS_ATTRIBUTE_IGNORE_REQUEST_TIMEOUT in the call to
    NdisMSetAttributesEx()

  • always return FALSE from MiniportCheckForHang()

Stephan

On Tue, 26 Feb 2002 19:16:22 +0530, “Anandhi Dhanabalan - CTD,
Chennai.” wrote:

>Hi Devs,
>2K DDK says
>1) "NDIS does not call a deserialized NIC driver’s MiniportReset function
>if the driver’s MiniportSend or MiniportSendPackets function seems to have
>timed out "
>2) "For A miniport driver that has a WDM lower edge, MiniportCheckForHang
>is not specified in DriverEntry. The miniport driver can rely on NDIS to
>determine if its miniport instance is hung, based on sends and requests that
>timeout so this routine is not required. "
>
>Now in case of Deserialized NIC Miniport driver with WDM Lower edge, that
>does not provide a MiniportCheckForHang routine, What are the scenarios in
>which Ndis will call MiniportReset ?
>
>Regards
>Anandhi
[snip]

9

Hi Devs,
2K DDK says

  1. "NDIS does not call a deserialized NIC driver’s MiniportReset
    function
    if the driver’s MiniportSend or MiniportSendPackets function seems
    to have
    timed out "
  2. "For A miniport driver that has a WDM lower edge,
    MiniportCheckForHang
    is not specified in DriverEntry. The miniport driver can rely on
    NDIS to
    determine if its miniport instance is hung, based on sends and
    requests that
    timeout so this routine is not required. "

Now in case of Deserialized NIC Miniport driver with WDM Lower
edge, that
does not provide a MiniportCheckForHang routine, What are the
scenarios in
which Ndis will call MiniportReset ?

Best Regards
Anandhi

10

You can refer to the following doc in the DDK:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/network/hh/network/203entry_5a07.asp

Which is called “Registering a CheckForHang Handle” in case the above link doesn’t work for you. It describes the scenarios under which NDIS will assume a miniport driver has stopped responding.

Ofcourse any other driver in the stack can call NdisReset at anytime for any other reason.

-Youssef.

-----Original Message-----
From: Anandhi [mailto:xxxxx@rediffmail.com]
Sent: Wed 2/27/2002 6:24 AM
To: NT Developers Interest List
Cc:
Subject: [ntdev] When will Ndis call MiniportReset ?

Hi Devs,
2K DDK says

  1. "NDIS does not call a deserialized NIC driver’s MiniportReset
    function
    if the driver’s MiniportSend or MiniportSendPackets function seems
    to have
    timed out "
  2. "For A miniport driver that has a WDM lower edge,
    MiniportCheckForHang
    is not specified in DriverEntry. The miniport driver can rely on
    NDIS to
    determine if its miniport instance is hung, based on sends and
    requests that
    timeout so this routine is not required. "

Now in case of Deserialized NIC Miniport driver with WDM Lower
edge, that
does not provide a MiniportCheckForHang routine, What are the
scenarios in
which Ndis will call MiniportReset ?

Best Regards
Anandhi

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

11

Can you please try and post standard ASCII text?

Or someone tell me how to read this in Forté Agent?

Thanks, Stephan

On Thu, 28 Feb 2002 16:51:01 -0800, “Youssef Barakat”
wrote:

>
>WW91IGNhbiByZWZlciB0byB0aGUgZm9sbG93aW5nIGRvYyBpbiB0aGUgRERLOg0KIA0KaHR0cDov
>L21zZG4ubWljcm9zb2Z0LmNvbS9saWJyYXJ5L2RlZmF1bHQuYXNwP3VybD0vbGlicmFyeS9lbi11
>cy9uZXR3b3JrL2hoL25ldHdvcmsvMjAzZW50cnlfNWEwNy5hc3ANCiANCldoaWNoIGlzIGNhbGxl
>ZCAiUmVnaXN0ZXJpbmcgYSBDaGVja0ZvckhhbmcgSGFuZGxlIiBpbiBjYXNlIHRoZSBhYm92ZSBs
>aW5rIGRvZXNuJ3Qgd29yayBmb3IgeW91LiBJdCBkZXNjcmliZXMgdGhlIHNjZW5hcmlvcyB1bmRl
>ciB3aGljaCBORElTIHdpbGwgYXNzdW1lIGEgbWluaXBvcnQgZHJpdmVyIGhhcyBzdG9wcGVkIHJl
>c3BvbmRpbmcuDQogDQpPZmNvdXJzZSBhbnkgb3RoZXIgZHJpdmVyIGluIHRoZSBzdGFjayBjYW4g
>Y2FsbCBOZGlzUmVzZXQgYXQgYW55dGltZSBmb3IgYW55IG90aGVyIHJlYXNvbi4NCiANCi1Zb3Vz
>c2VmLg0KDQoJLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0gDQoJRnJvbTogQW5hbmRoaSBbbWFp
>bHRvOmRhbmFuZGhpQHJlZGlmZm1haWwuY29tXSANCglTZW50OiBXZWQgMi8yNy8yMDAyIDY6MjQg
>QU0gDQoJVG86IE5UIERldmVsb3BlcnMgSW50ZXJlc3QgTGlzdCANCglDYzogDQoJU3ViamVjdDog
>W250ZGV2XSBXaGVuIHdpbGwgTmRpcyBjYWxsIE1pbmlwb3J0UmVzZXQgPw0KCQ0KCQ0KDQoJSGkg
>RGV2cywNCgkySyBEREsgc2F5cw0KCTEpICAiTkRJUyBkb2VzIG5vdCBjYWxsIGEgZGVzZXJpYWxp
>emVkIE5JQyBkcml2ZXIncyBNaW5pcG9ydFJlc2V0DQoJZnVuY3Rpb24NCglpZiB0aGUgZHJpdmVy
>J3MgTWluaXBvcnRTZW5kIG9yIE1pbmlwb3J0U2VuZFBhY2tldHMgZnVuY3Rpb24gc2VlbXMNCgl0
>byBoYXZlDQoJdGltZWQgb3V0ICINCgkyKSAiRm9yIEEgbWluaXBvcnQgZHJpdmVyIHRoYXQgaGFz
>IGEgV0RNIGxvd2VyIGVkZ2UsDQoJTWluaXBvcnRDaGVja0ZvckhhbmcNCglpcyBub3Qgc3BlY2lm
>aWVkIGluIERyaXZlckVudHJ5LiBUaGUgbWluaXBvcnQgZHJpdmVyIGNhbiByZWx5IG9uDQoJTkRJ
>UyB0bw0KCWRldGVybWluZSBpZiBpdHMgbWluaXBvcnQgaW5zdGFuY2UgaXMgaHVuZywgYmFzZWQg
>b24gc2VuZHMgYW5kDQoJcmVxdWVzdHMgdGhhdA0KCXRpbWVvdXQgc28gdGhpcyByb3V0aW5lIGlz
>IG5vdCByZXF1aXJlZC4gIg0KCQ0KCU5vdyBpbiBjYXNlIG9mIERlc2VyaWFsaXplZCBOSUMgTWlu
>aXBvcnQgZHJpdmVyIHdpdGggV0RNIExvd2VyDQoJZWRnZSwgIHRoYXQNCglkb2VzIG5vdCBwcm92
>aWRlIGEgTWluaXBvcnRDaGVja0ZvckhhbmcgIHJvdXRpbmUsIFdoYXQgYXJlIHRoZQ0KCXNjZW5h
>cmlvcyBpbg0KCXdoaWNoIE5kaXMgd2lsbCBjYWxsIE1pbmlwb3J0UmVzZXQgPw0KCQ0KCUJlc3Qg
>UmVnYXJkcw0KCUFuYW5kaGkNCgkNCgkNCgktLS0NCglZb3UgYXJlIGN1cnJlbnRseSBzdWJzY3Jp
>YmVkIHRvIG50ZGV2IGFzOiB5b3Vzc2VmYkBtaWNyb3NvZnQuY29tDQoJVG8gdW5zdWJzY3JpYmUg
>c2VuZCBhIGJsYW5rIGVtYWlsIHRvIGxlYXZlLW50ZGV2LTUyODFSQGxpc3RzLm9zci5jb20NCgkN
>Cg0K

12

> > Please remove your “Disclaimer” if you need an answer here.

Actually, Stephan, you just broke HCL Technologies Ltd’s law since you

This forum can be legally classified as “private mean of communication”, so, such insults are useless.

Max