MiniportHalt

I have an Intermediate Driver that works on Dell machines. On a new machine
the MiniportHalt handler is called right after Miniport Initialize Handler.
MPInitialize returns SUCCESS.

I need suggestions on how to find out why MPHalt is being called.

Larry C

Pavel
Wed Sep 03 22:16:11 CDT 2003

"Larry Clawson" <larry.clawson@honeywell.com> wrote in message
news:OzUVC%23ncDHA.2672@tk2msftngp13.phx.gbl...
> I have an Intermediate Driver that works on Dell machines. On a new machine
> the MiniportHalt handler is called right after Miniport Initialize Handler.
> MPInitialize returns SUCCESS.
>
> I need suggestions on how to find out why MPHalt is being called.
>

You do something that ndis does not like (such as: fail or return bad data for some OIDs).

-- PA

Larry
Wed Sep 03 21:18:08 CDT 2003

I'm not returning any failed statuses. The OID is something to check though.

Thank you.

Larry c


"Pavel A." <pavel_a@geeklife.com> wrote in message
news:u1IkenocDHA.1808@TK2MSFTNGP11.phx.gbl...
> "Larry Clawson" <larry.clawson@honeywell.com> wrote in message
> news:OzUVC%23ncDHA.2672@tk2msftngp13.phx.gbl...
> > I have an Intermediate Driver that works on Dell machines. On a new
machine
> > the MiniportHalt handler is called right after Miniport Initialize
Handler.
> > MPInitialize returns SUCCESS.
> >
> > I need suggestions on how to find out why MPHalt is being called.
> >
>
> You do something that ndis does not like (such as: fail or return bad data
for some OIDs).
>
> -- PA
>
>

Stephan
Thu Sep 04 07:42:31 CDT 2003

Run Microsoft's NDISTest against your driver and see what the logs
say:

http://www.wd-3.com/071503/NDISTest.htm

Stephan
---
On Thu, 4 Sep 2003 12:18:08 +1000, "Larry Clawson"
<larry.clawson@honeywell.com> wrote:

>I'm not returning any failed statuses. The OID is something to check though.
>
>Thank you.
>
>Larry c
>
>
>"Pavel A." <pavel_a@geeklife.com> wrote in message
>news:u1IkenocDHA.1808@TK2MSFTNGP11.phx.gbl...
>> "Larry Clawson" <larry.clawson@honeywell.com> wrote in message
>> news:OzUVC%23ncDHA.2672@tk2msftngp13.phx.gbl...
>> > I have an Intermediate Driver that works on Dell machines. On a new
>machine
>> > the MiniportHalt handler is called right after Miniport Initialize
>Handler.
>> > MPInitialize returns SUCCESS.
>> >
>> > I need suggestions on how to find out why MPHalt is being called.
>> >
>>
>> You do something that ndis does not like (such as: fail or return bad data
>for some OIDs).
>>
>> -- PA

bburgin
Thu Sep 04 00:58:56 CDT 2003

------=_NextPart_0001_FECF9AA6
Content-Type: text/plain
Content-Transfer-Encoding: 7bit


Hi Larry,

Have you stripped the stack to its most basic components: protocol and
miniport and then added your IM? Anything show up from turning on NDIS
tracing w/ NdisSystems set to 0xffffffff and NdisLevel set to zero?

Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_FECF9AA6
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20
\par Hi Larry,
\par
\par Have you stripped the stack to its most basic components: protocol and miniport and then added your IM? Anything show up from turning on NDIS tracing w/ NdisSystems set to 0xffffffff and NdisLevel set to zero?
\par
\par Bryan S. Burgin
\par bburgin@microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_FECF9AA6--

Larry
Thu Sep 04 18:41:13 CDT 2003

Thanks, I'll do that.

Larry
"Stephan Wolf" <stewo68@hotmail.com> wrote in message
news:pncelvgmdqpq2iubb3vum49d3rcri8bih9@4ax.com...
> Run Microsoft's NDISTest against your driver and see what the logs
> say:
>
> http://www.wd-3.com/071503/NDISTest.htm
>
> Stephan
> ---
> On Thu, 4 Sep 2003 12:18:08 +1000, "Larry Clawson"
> <larry.clawson@honeywell.com> wrote:
>
> >I'm not returning any failed statuses. The OID is something to check
though.
> >
> >Thank you.
> >
> >Larry c
> >
> >
> >"Pavel A." <pavel_a@geeklife.com> wrote in message
> >news:u1IkenocDHA.1808@TK2MSFTNGP11.phx.gbl...
> >> "Larry Clawson" <larry.clawson@honeywell.com> wrote in message
> >> news:OzUVC%23ncDHA.2672@tk2msftngp13.phx.gbl...
> >> > I have an Intermediate Driver that works on Dell machines. On a new
> >machine
> >> > the MiniportHalt handler is called right after Miniport Initialize
> >Handler.
> >> > MPInitialize returns SUCCESS.
> >> >
> >> > I need suggestions on how to find out why MPHalt is being called.
> >> >
> >>
> >> You do something that ndis does not like (such as: fail or return bad
data
> >for some OIDs).
> >>
> >> -- PA

Larry
Thu Sep 04 18:40:30 CDT 2003

Is there information on how to trun on NDIS tracing either in the WinDbg
Help or an KB Article.

thanks.

Larry
""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:E8CP%231vcDHA.1068@cpmsftngxa06.phx.gbl...
>
> Hi Larry,
>
> Have you stripped the stack to its most basic components: protocol and
> miniport and then added your IM? Anything show up from turning on NDIS
> tracing w/ NdisSystems set to 0xffffffff and NdisLevel set to zero?
>
> Bryan S. Burgin
> bburgin@microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.

bburgin
Thu Sep 04 21:01:42 CDT 2003

------=_NextPart_0001_00F72625
Content-Type: text/plain
Content-Transfer-Encoding: 7bit


In the DDK at DDK\Network Devices and Protocols\Desgn Guide\Debugging NDIS
Drivers\NDIS Debugging Extensions For Windows 2000\Enabling NDIS Debug
Tracing. I usually just do through the registry by setting (DWORD)
DebugLevel and (DWORD) DebugSystems at
HKLM\SYSTEM\CurrentControlSet\Services\NDIS\Parameters -- described about
halfway down that page.

HTH


Bryan S. Burgin
bburgin@microsoft.com

This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_00F72625
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit

{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fnil\fprq2\fcharset0 MS Sans Serif;}}
\viewkind4\uc1\pard\f0\fs20
\par In the DDK at DDK\\Network Devices and Protocols\\Desgn Guide\\Debugging NDIS Drivers\\NDIS Debugging Extensions For Windows 2000\\Enabling NDIS Debug Tracing. I usually just do through the registry by setting (DWORD) DebugLevel and (DWORD) DebugSystems at HKLM\\SYSTEM\\CurrentControlSet\\Services\\NDIS\\Parameters -- described about halfway down that page.
\par
\par HTH
\par
\par
\par Bryan S. Burgin
\par bburgin@microsoft.com
\par
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par }
------=_NextPart_0001_00F72625--

Larry
Thu Sep 04 21:21:12 CDT 2003

Thank you Bryan.


""Bryan S. Burgin [MSFT]"" <bburgin@online.microsoft.com> wrote in message
news:QE79mG1cDHA.2408@cpmsftngxa06.phx.gbl...
>
> In the DDK at DDK\Network Devices and Protocols\Desgn Guide\Debugging NDIS
> Drivers\NDIS Debugging Extensions For Windows 2000\Enabling NDIS Debug
> Tracing. I usually just do through the registry by setting (DWORD)
> DebugLevel and (DWORD) DebugSystems at
> HKLM\SYSTEM\CurrentControlSet\Services\NDIS\Parameters -- described about
> halfway down that page.
>
> HTH
>
>
> Bryan S. Burgin
> bburgin@microsoft.com
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.