NDIS Intermediate driver hangs the machine on some cards

Hi experts,

I’s still fine with the problem as described in my previouss mail(and also below) as i faced it on Intel cards only. The same problem is encountering in DEC-500TX cards also… can anyone please give me any kind of guideline where can i start troubleshooting and perfecting this IM driver… you can say me either a “No” to save my time but please need an assured answer for any of you experts.
Thanks in advance.
–Sumit

Hi Thomas and all,

I also encounter the same problem with the PCAUSA ImSamp “Version 0.100 built on May 28 1997 13:33:16”. After installaing, and manually disabling TCP/IP binding for Intel PRO/100+ Adapter, as i rebooted the machine it hanged up and comes up only when i remove the network cable from card. On the debug screen messages were

… … … …
ModLoad: f72b8000 f72bffc0 ImSamp.sys
ImSamp: Ndis 4.0 Intermediate Driver Sample: Version 0.100 built on May 28 1997 13:33:16
Unbind: calling Delinterface
Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.

eax=00000004 ebx=fc8d9700 ecx=f728aa92 edx=00000000 esi=8014985c edi=ffdff208
eip=8012f910 esp=8014977c ebp=801498f0 iopl=0 nv up di pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000002
Loading symbols for 80100000 ntoskrnl.exe -> ntoskrnl.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
ntoskrnl!DbgBreakPointWithStatus+4:
8012f910 cc int 3
Loading symbols for f74a8000 tdi.sys -> tdi.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for tdi.sys -
ChildEBP RetAddr Args to Child
801498f0 80140e60 0000000a 14dc0000 00000002 ntoskrnl!DbgBreakPointWithStatus+0x4
8014990c c009cb39 80859643 00000000 00000000 ntoskrnl!Kei386EoiHelper+0x2948
80859648 f74a95e8 00630000 0002000e 09c00000 0xffffffff`c009cb39
00000000 00000000 00000000 00000000 00000000 TDI!TdiDeregisterNetAddress+0x376
Bugcheck code 0000000A
Arguments 14dc0000 00000002 00000000 fc8d9700
ntoskrnl!DbgBreakPointWithStatus+4:
8012f910 cc int 3
kd>
… … … …

I took a look into the registry “SERVICE\IMSAMP” and “SERVICE\IMSAMPMP”, and changed the variable Group to “PNP_TDI”, instead of NDIS with all possible combination and the observations are here.

1> Firstly I changed the Group for ImSamp but i failed to get the desired functioanlity, now insteed of my machine hangup, I can login and work but my TCP/IP network doesn’t come up. the command “ipconfig” doesn’t display configurations except title message " Windows NT IP Configuration". At the same time I never get the message “Unbind: calling Delinterface”.

2> When i set Group of ImSampMP to PNP_TDI, quite illogical, still I tried that… a looping crash occusrs. i mean go command to debugger give same crash output again and again

… … … … …
ModLoad: f72b0000 f72b7fc0 ImSamp.sys
ImSamp: Ndis 4.0 Intermediate Driver Sample: Version 0.100 built on May 28 1997
13:33:16
ModLoad: f74b4000 f74b64e0 TDI.SYS
ModLoad: fc414000 fc439000 tcpip.sys
IP: Unable to read addrmaskreply value from registry.
Will be disabled.
ModLoad: fc3f8000 fc413040 netbt.sys
ModLoad: fc3dd000 fc3f7200 E100BNT.SYS
ModLoad: fc2cc000 fc2dc8c0 afd.sys
ModLoad: f7380000 f7387120 netbios.sys
ModLoad: fc8ab000 fc8ad640 Parport.SYS
Unbind: calling Delinterface
Break instruction exception - code 80000003 (first chance)

A fatal system error has occurred.

eax=00000004 ebx=fc8d9700 ecx=f728aa92 edx=00000000 esi=8014985c edi=ffdff208
eip=8012f910 esp=8014977c ebp=801498f0 iopl=0 nv up di pl nz na pe nc
cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000 efl=00000002
Loading symbols for 80100000 ntoskrnl.exe -> ntoskrnl.exe
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntoskrnl.exe -
ntoskrnl!DbgBreakPointWithStatus+4:
8012f910 cc int 3
Loading symbols for f74b4000 tdi.sys -> tdi.sys
*** ERROR: Symbol file could not be found. Defaulted to export symbols for tdi.sys -
ChildEBP RetAddr Args to Child
801498f0 80140e60 0000000a 14dc0000 00000002 ntoskrnl!DbgBreakPointWithStatus+0x4
8014990c c009cb39 8085d643 00000000 00000000 ntoskrnl!Kei386EoiHelper+0x2948
8085d648 f74b55e8 00630000 0002000e 09c00000 0xffffffff`c009cb39
00000000 00000000 00000000 00000000 00000000 TDI!TdiDeregisterNetAddress+0x376
Bugcheck code 0000000A
Arguments 14dc0000 00000002 00000000 fc8d9700
ntoskrnl!DbgBreakPointWithStatus+4:
8012f910 cc int 3
kd>

3> Observation with the Group set to PNP_TDI in both Adapter and Transport are the messages…
… … … …
ModLoad: f72b8000 f72bffc0 ImSamp.sys
ImSamp: Ndis 4.0 Intermediate Driver Sample: Version 0.100 built on May 28 1997 13:33:16
Unbind: calling Delinterface
… … … …
and no responce from machine

I’m using the oemsetup.inf and imsamp.sys that came with the IM driver from pcausa… and i’ve checked against the latest driver by intel which i downloaded yesterday and previously i’s using the driver shipped with card ab that was again by intel only.

Please advise…

Thanks in advance,

  • Sumit Pandya

-----Original Message-----
From: Thomas F. Divine [mailto:xxxxx@pcausa.com]
Sent: Wednesday, October 11, 2000 10:36 PM
To: NT Developers Interest List
Subject: [ntdev] Re: Intermediate drivers co-existence

You might try setting the GROUP setting for your IM to PNP_TDI instead of
NDIS. The offending 3Com gizmo (I hate it!!!) starts as a service with a
group setting of NDIS as well. Without further discriminators your IM can be
loaded in the wrong order.

Let me know if this helps. It worked for me.

Good luck,

Thomas F. Divine

PCAUSA - Toolkits & Resources For Network Software Developers
NDIS Protocol - TDI Client - Windows 95 Redirector
http:

----- Original Message -----
From: Barak Mandelovich
To: NT Developers Interest List
Sent: Tuesday, October 10, 2000 8:55 AM
Subject: [ntdev] Intermediate drivers co-existence

> Hi, everybody!
>
> I built my own IM driver, based on the ImSamp.sys driver
> from the DDK, and it works fine on machines without
> other intermediate drivers.
>
> The problem starts when I try to install it on a machine
> with an intermediate driver already installed (e.g.: The Intel Pro/100+,
> which
> is not a regular Ethernet card, but it has an intermediate driver
> above the MAC level, that makes it look to the system as a “regular”
> Ethernet (the system “thinks” that the IM driver is the MAC driver…) ).
>
> Now, when I install the ImSamp, it’s installed between the NIC’s
> MAC driver and the NIC’s IM driver, instead of between the IM and the IP
> layer.
>
> I think it has something to do with the oemsetup.inf of ImSamp.
>
> Am I right? If not - where should I look for the answer?
> If I’m right - can someone please tell me what should be done
> (I took a look at the ImSamp’s oemsetup.inf and understood NOTHING…)
>
> Where can I find info regarding oemsetup.inf?
>
> I tried to change the bindings manually, but for the IMSAMP
> service, I could only choose “physical” devices (e.g.: The MAC driver
> of the NIC, another Ethernet card etc.)
>
> thanks in advance,
>
> - Barak
>


eLitecore Technologies Pvt. Ltd.


eLitecore Technologies Pvt. Ltd.


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:>

Do understand that the ImSamp NDIS IM Sample downloadable from the PCAUSA
website was NOT developed by PCAUSA. It was an early sample developed by
Microsoft.

Microsoft has newer NDIS IM Samples for Windows NT as well as NDIS IM
samples for Windows 2000 and Windows XP. Each of these newer samples are
progressively better…

See the NDIS IM FAQ at the URL below for links to the current NDIS IM driver
samples:

http://www.pcausa.com/resources/ndisimfaq.htm#AnchorNTImSamp

Now there are additional problems specific to some cards. On Windows 2000
and higher the problems are often related to NDIS Task Offload. See the
release notes for PCAUSA’s new NDIS IM driver samples for a diary of some of
these problems.

http://www.rawether.net/ndisim/support/releasenotes.htm

It looks like you Case 1.) below is making progress. The hang has been
eliminated at least. Now you must debug to find out why TCP/IP isn’t
working.

Good luck,

Thomas F. Divine

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

----- Original Message -----
From: “Sumit Pandya”
To: “NT Developers Interest List”
Sent: Monday, August 27, 2001 10:07 AM
Subject: [ntdev] NDIS Intermediate driver hangs the machine on some cards

> Hi experts,
>
> I’s still fine with the problem as described in my previouss mail(and
also below) as i faced it on Intel cards only. The same problem is
encountering in DEC-500TX cards also… can anyone please give me any kind
of guideline where can i start troubleshooting and perfecting this IM
driver… you can say me either a “No” to save my time but please need an
assured answer for any of you experts.
> Thanks in advance.
> --Sumit
>
> Hi Thomas and all,
>
> I also encounter the same problem with the PCAUSA ImSamp “Version
0.100 built on May 28 1997 13:33:16”. After installaing, and manually
disabling TCP/IP binding for Intel PRO/100+ Adapter, as i rebooted the
machine it hanged up and comes up only when i remove the network cable from
card. On the debug screen messages were
>
> … … … …
> ModLoad: f72b8000 f72bffc0 ImSamp.sys
> ImSamp: Ndis 4.0 Intermediate Driver Sample: Version 0.100 built on May 28
1997 13:33:16
> Unbind: calling Delinterface
> Break instruction exception - code 80000003 (first chance)
>
> A fatal system error has occurred.
>
> eax=00000004 ebx=fc8d9700 ecx=f728aa92 edx=00000000 esi=8014985c
edi=ffdff208
> eip=8012f910 esp=8014977c ebp=801498f0 iopl=0 nv up di pl nz na pe
nc
> cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000
efl=00000002
> Loading symbols for 80100000 ntoskrnl.exe -> ntoskrnl.exe
> ERROR: Symbol file could not be found. Defaulted to export symbols
for ntoskrnl.exe -
> ntoskrnl!DbgBreakPointWithStatus+4:
> 8012f910 cc int 3
> Loading symbols for f74a8000 tdi.sys -> tdi.sys
>
ERROR: Symbol file could not be found. Defaulted to export symbols
for tdi.sys -
> ChildEBP RetAddr Args to Child
> 801498f0 80140e60 0000000a 14dc0000 00000002
ntoskrnl!DbgBreakPointWithStatus+0x4
> 8014990c c009cb39 80859643 00000000 00000000
ntoskrnl!Kei386EoiHelper+0x2948
> 80859648 f74a95e8 00630000 0002000e 09c00000 0xffffffffc009cb39<br>&gt; 00000000 00000000 00000000 00000000 00000000<br>TDI!TdiDeregisterNetAddress+0x376<br>&gt; Bugcheck code 0000000A<br>&gt; Arguments 14dc0000 00000002 00000000 fc8d9700<br>&gt; ntoskrnl!DbgBreakPointWithStatus+4:<br>&gt; 8012f910 cc int 3<br>&gt; kd&gt;<br>&gt; ... ... ... ...<br>&gt;<br>&gt; I took a look into the registry "SERVICE\IMSAMP" and<br>"SERVICE\IMSAMPMP", and changed the variable Group to "PNP_TDI", instead of<br>NDIS with all possible combination and the observations are here.<br>&gt;<br>&gt; 1&gt; Firstly I changed the Group for ImSamp but i failed to get the<br>desired functioanlity, now insteed of my machine hangup, I can login and<br>work but my TCP/IP network doesn't come up. the command "ipconfig" doesn't<br>display configurations except title message " Windows NT IP Configuration".<br>At the same time I never get the message "Unbind: calling Delinterface".<br>&gt;<br>&gt; 2&gt; When i set Group of ImSampMP to PNP_TDI, quite illogical, still I<br>tried that... a looping crash occusrs. i mean go command to debugger give<br>same crash output again and again<br>&gt;<br>&gt; ... ... ... ... ...<br>&gt; ModLoad: f72b0000 f72b7fc0 ImSamp.sys<br>&gt; ImSamp: Ndis 4.0 Intermediate Driver Sample: Version 0.100 built on May 28<br>1997<br>&gt; 13:33:16<br>&gt; ModLoad: f74b4000 f74b64e0 TDI.SYS<br>&gt; ModLoad: fc414000 fc439000 tcpip.sys<br>&gt; IP: Unable to read addrmaskreply value from registry.<br>&gt; Will be disabled.<br>&gt; ModLoad: fc3f8000 fc413040 netbt.sys<br>&gt; ModLoad: fc3dd000 fc3f7200 E100BNT.SYS<br>&gt; ModLoad: fc2cc000 fc2dc8c0 afd.sys<br>&gt; ModLoad: f7380000 f7387120 netbios.sys<br>&gt; ModLoad: fc8ab000 fc8ad640 Parport.SYS<br>&gt; Unbind: calling Delinterface<br>&gt; Break instruction exception - code 80000003 (first chance)<br>&gt;<br>&gt; A fatal system error has occurred.<br>&gt;<br>&gt; eax=00000004 ebx=fc8d9700 ecx=f728aa92 edx=00000000 esi=8014985c<br>edi=ffdff208<br>&gt; eip=8012f910 esp=8014977c ebp=801498f0 iopl=0 nv up di pl nz na pe<br>nc<br>&gt; cs=0008 ss=0010 ds=0023 es=0023 fs=0030 gs=0000<br>efl=00000002<br>&gt; Loading symbols for 80100000 ntoskrnl.exe -&gt; ntoskrnl.exe<br>&gt; ***ERROR: Symbol file could not be found. Defaulted to export symbols<br>for ntoskrnl.exe -<br>&gt; ntoskrnl!DbgBreakPointWithStatus+4:<br>&gt; 8012f910 cc int 3<br>&gt; Loading symbols for f74b4000 tdi.sys -&gt; tdi.sys<br>&gt;*** ERROR: Symbol file could not be found. Defaulted to export symbols<br>for tdi.sys -<br>&gt; ChildEBP RetAddr Args to Child<br>&gt; 801498f0 80140e60 0000000a 14dc0000 00000002<br>ntoskrnl!DbgBreakPointWithStatus+0x4<br>&gt; 8014990c c009cb39 8085d643 00000000 00000000<br>ntoskrnl!Kei386EoiHelper+0x2948<br>&gt; 8085d648 f74b55e8 00630000 0002000e 09c00000 0xffffffffc009cb39
> 00000000 00000000 00000000 00000000 00000000
TDI!TdiDeregisterNetAddress+0x376
> Bugcheck code 0000000A
> Arguments 14dc0000 00000002 00000000 fc8d9700
> ntoskrnl!DbgBreakPointWithStatus+4:
> 8012f910 cc int 3
> kd>
>
> 3> Observation with the Group set to PNP_TDI in both Adapter and
Transport are the messages…
> … … … …
> ModLoad: f72b8000 f72bffc0 ImSamp.sys
> ImSamp: Ndis 4.0 Intermediate Driver Sample: Version 0.100 built on May 28
1997 13:33:16
> Unbind: calling Delinterface
> … … … …
> and no responce from machine
>
> I’m using the oemsetup.inf and imsamp.sys that came with the IM driver
from pcausa… and i’ve checked against the latest driver by intel which i
downloaded yesterday and previously i’s using the driver shipped with card
ab that was again by intel only.
>
> Please advise…
>
> Thanks in advance,
>
> - Sumit Pandya
>
>
> -----Original Message-----
> From: Thomas F. Divine [mailto:xxxxx@pcausa.com]
> Sent: Wednesday, October 11, 2000 10:36 PM
> To: NT Developers Interest List
> Subject: [ntdev] Re: Intermediate drivers co-existence
>
>
> You might try setting the GROUP setting for your IM to PNP_TDI instead of
> NDIS. The offending 3Com gizmo (I hate it!!!) starts as a service with a
> group setting of NDIS as well. Without further discriminators your IM can
be
> loaded in the wrong order.
>
> Let me know if this helps. It worked for me.
>
> Good luck,
>
> Thomas F. Divine
>
> PCAUSA - Toolkits & Resources For Network Software Developers
> NDIS Protocol - TDI Client - Windows 95 Redirector
> http:
>
> ----- Original Message -----
> From: Barak Mandelovich
> To: NT Developers Interest List
> Sent: Tuesday, October 10, 2000 8:55 AM
> Subject: [ntdev] Intermediate drivers co-existence
>
>
> > Hi, everybody!
> >
> > I built my own IM driver, based on the ImSamp.sys driver
> > from the DDK, and it works fine on machines without
> > other intermediate drivers.
> >
> > The problem starts when I try to install it on a machine
> > with an intermediate driver already installed (e.g.: The Intel Pro/100+,
> > which
> > is not a regular Ethernet card, but it has an intermediate driver
> > above the MAC level, that makes it look to the system as a “regular”
> > Ethernet (the system “thinks” that the IM driver is the MAC
driver…) ).
> >
> > Now, when I install the ImSamp, it’s installed between the NIC’s
> > MAC driver and the NIC’s IM driver, instead of between the IM and the IP
> > layer.
> >
> > I think it has something to do with the oemsetup.inf of ImSamp.
> >
> > Am I right? If not - where should I look for the answer?
> > If I’m right - can someone please tell me what should be done
> > (I took a look at the ImSamp’s oemsetup.inf and understood NOTHING…)
> >
> > Where can I find info regarding oemsetup.inf?
> >
> > I tried to change the bindings manually, but for the IMSAMP
> > service, I could only choose “physical” devices (e.g.: The MAC driver
> > of the NIC, another Ethernet card etc.)
> >
> > thanks in advance,
> >
> > - Barak
> >
>
>
>
>
> eLitecore Technologies Pvt. Ltd.
>
>
>
>

> eLitecore Technologies Pvt. Ltd.
>
>
> —
> You are currently subscribed to ntdev as: xxxxx@pcausa.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</http:></http:></http:>