Hi all,
As suggested by Max(thanx a lot),I have written a sample Deserilized
Miniport which at it’s lower end writes to the serial port.
Now the problem started when I tried to load this driver,
As I load this driver,the function “NdisMRegisterMiniport” fails by giving
the error “0031 A Device attached to system is not functioning”.
If I register this driver through “NdisIMRegisterLayeredMiniport”,then
there is no error and the driver loads properly but as mentioned in DDK that
if ur IM driver doesn’t have Protocolxxx Functions then u should register it
by using “NdisMRegisterminiport”.
Now please tell me but to do??
1)Can I use “NdisIMRegisterLayeredMiniport” to register my driver as IM,if
so then how will my Miniportinitilze handle will be called?? The later
part of question require more information for u people 
2)If I should stick to DDK,then what is the possible reason for the above
error and how should I resolve it.please explain in detail what all is
needed to be done to solve this problem.
hey everybody,now I am waiting on a semaphore which is to be signaled by u
people,
so,Please do it ASAP
thanx
Chandandeep Singh Pabla
DCM Technologies
Subject: Re: NDIS IM Driver
From: “Maxim S. Shatskih”
Date: Wed, 2 May 2001 16:31:17 +0400
X-Message-Number: 16
> I am writing a NDIS4.0 intermediate Driver for Win NT4.0 which will talk
at
You will not need an IM driver in this case. You must not have a protocol
lower end.
Write a deserialized NDIS miniport on top of the serial port, not the IM.
> 1.Actully i have to run a transport driver(i.e TCP/IP) on a serial port so
i
> think IM driver is the only option left.Isn’t it so??
Not IM, but a miniport (better deserialized) on top of the serial port.
> 2.How can we map or convert an NDIS packet sent by Transport driver(eg.
> TCP/IP) into an IRP so that it could be passed to serial driver.
NDIS packet contains a MDL chain, IRP can contain it too.
> 3.In the usual scenario of layered kernel mode drivers,i can call
> “IoGetDeviceObjectPointer” to bind my upper layer driver to some lower
> driver.In my case of IM driver,should my IM driver have same function to
> bind to lower serial driver or there is some other way to accomplish this
> binding.
Yes, or - on w2k - you can register for a PnP device notification for the
Serial class devices and bind yourself to it from this notification, then
reporting the link up condition to the protocol drivers above you.
Max
—
You are currently subscribed to ntdev as: xxxxx@dcmtech.co.in
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