Hi Thomas and All,
Do understand that the ImSamp NDIS IM Sample downloadable from the PCAUSA website was NOT developed by PCAUSA. It was an early sample developed byMicrosoft.
Here I wanted to provide detail information to the experts. Sorry if it goes anything wrong with PCAUSA.
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…
Ya there is no doubt for Passthru but the latest IMSamp source is still creating the same problem.
Anyway thankx for your time , it gives a boost to newbie like me with assurence that somewhere a good help is availabe.
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.
At the moment i’m trying with checked version of NT and IMSamp, and seems the problem has a little or nothing to do with TCP/IP… here is dump of target machine … anyone can please simplify this problem to me? What i should look for in IMSamp and also i’ve no idea about DPC routine, what is this, is it where the problem seems?
------------ DUMP BEGINS HERE ------------------------
ImSamp: Ndis 4.0 Intermediate Driver Sample: Version 0.100 built on Aug 28 2001 14:08:40
IMSamp: BindToLowerMP: \Device\DLKRTS1
IMSamp: (80935EC8) LowerMPOpenAdapterComplete
IMSamp: (80935EC8) ProcessLowerMPOpenAdapter
IMSamp: (80935EC8) =1 Adapter
IMSamp: (80935EC8) MakeNdisRequest: OID 00010102
… … …
IMSamp: (80935EC8) CLRequestComplete: OID 00010105
IMSamp: MPInitialize: Enter
IMSamp: (80935EC8) MPQueryInformation:
IMSamp: (80935EC8) MakeNdisRequest: OID 00010105
… … …
IMSamp: (80935EC8) CLRequestComplete: OID 01010102
IMSamp: BindToLowerMP: \Device\ImSampMP2
IMSamp: (809168A8) GetAdapterRegistryData: Missing InstanceNumber key
IMSamp: (809168A8) BindToLowerMP: Couldn’t get registry data C0000001 (\Device\ImSampMP2)
IMSamp: IRP Create
IMSamp: IRP Cleanup
IMSamp: (80935EC8) MPQueryInformation:
IMSamp: (80935EC8) MakeNdisRequest: OID 01010102
IMSamp: (80935EC8) CLRequestComplete: OID 01010102
… … …
IMSamp: (80935EC8) MPSetInformation
IMSamp: (80935EC8) MakeNdisRequest: OID 0001010F
IMSamp: (80935EC8) CLRequestComplete: OID 0001010F
… … …
*** Assertion failed: MINIPORT_LOCK_ACQUIRED(Miniport)
*** Source File: w:\nt\private\ntos\ndis\ndis40\mp..\efilter.c, line 2113
Break, Ignore, Terminate Process or Terminate Thread (bipt)?i
IMSamp: ClReceiveIndication (8096BBC8) +Adapter:h 2
IMSamp:
(8096BBC8) CLReceiveIndication: Packet 80935E00 Packetsize 28
IMSamp: (8096BBC8) MPReturnPacket: IM Packet 80935E00
IMSamp: (8096BBC8) -Adapter:a 1
IMSamp: (8096BBC8) CLReceiveComplete:
… … … …
IMSamp: ClReceiveIndication (8096BBC8) +Adapter:h 2
IMSamp: (8096BBC8) CLReceiveIndication: Packet 80935E78 Packetsize 46
IMSamp: (8096BBC8) MPReturnPacket: IM Packet 80935E78
IMSamp: (8096BBC8) -Adapter:a 1
IMSamp: (8096BBC8) CLReceiveComplete:
*** DPC routine f63819c1 > 1sec (61d interrupts, 0 isr time)
Break instruction exception - code 80000003 (first chance)
ntoskrnl!DbgBreakPoint:
80165c4c cc int 3
kd> g
*** Assertion failed: MINIPORT_LOCK_ACQUIRED(Miniport)
*** Source File: w:\nt\private\ntos\ndis\ndis40\mp..\efilter.c, line 2113
Break, Ignore, Terminate Process or Terminate Thread (bipt)?i
-------------- DUMP END -------------------------
And the message block (starting Assertion failed, and ending DPC routine) continues.
Thankx for any help.
– Sumit
----- Original Message -----
From: Barak Mandelovich
> 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.
—
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