Hi,
I want to expose a normal WDM based driver as NIC driver, without interacting with NDIS. I just tried putting:
class=Net and
ClassGuid={4D36E972-E325-11CE-BFC1-08002BE10318}
these two lines in inf file but my driver is not getting loaded.
What are all the stuffs which are mandatory for exposing a driver(say which dont have to interact with NDIS but acts as a normal WDM based driver). It will be great if anyone can throw light on this.
Thanks
Sanwin
ps: But same driver, if I load it as Modem driver with say class=Modem its working fine, in the sense its getting loaded properly.
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
Impossible, any NIC drivers must have an NDIS upper end.
Max
----- Original Message -----
From: San Wind
To: NT Developers Interest List
Sent: Tuesday, November 06, 2001 3:07 PM
Subject: [ntdev] Query related to NEtwork INF file
Hi,
I want to expose a normal WDM based driver as NIC driver, without interacting with NDIS. I just tried putting:
class=Net and
ClassGuid={4D36E972-E325-11CE-BFC1-08002BE10318}
these two lines in inf file but my driver is not getting loaded.
What are all the stuffs which are mandatory for exposing a driver(say which dont have to interact with NDIS but acts as a normal WDM based driver). It will be great if anyone can throw light on this.
Thanks
Sanwin
ps: But same driver, if I load it as Modem driver with say class=Modem its working fine, in the sense its getting loaded properly.
You are currently subscribed to ntdev as: xxxxx@storagecraft.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
Thanx forU’r response Maxim,
But I’m just wondering why there is an option of
choosing “noupper” and “nolower” in INF file for
binding. I tried this in 98SE. But its not working.
Any comments ?
Thanx in Advance
reg
ME
-----Original Message-----
From: Maxim S. Shatskih
[mailto:xxxxx@storagecraft.com]
Sent: Wednesday, November 07, 2001 11:16 AM
To: NT Developers Interest List
Subject: [ntdev] Re: Query related to NEtwork INF file
Impossible, any NIC drivers must have an NDIS upper
end.
Max
----- Original Message -----
From: San Wind
To: NT Developers Interest List
Sent: Tuesday, November 06, 2001 3:07 PM
Subject: [ntdev] Query related to NEtwork INF file
Hi,
I want to expose a normal WDM based driver as NIC
driver, without interacting with NDIS. I just tried
putting:
class=Net and
ClassGuid={4D36E972-E325-11CE-BFC1-08002BE10318}
these two lines in inf file but my driver is not
getting loaded.
What are all the stuffs which are mandatory for
exposing a driver(say which dont have to interact with
NDIS but acts as a normal WDM based driver). It will
be great if anyone can throw light on this.
Thanks
Sanwin
ps: But same driver, if I load it as Modem driver with
say class=Modem its working fine, in the sense its
getting loaded properly.
Do You Yahoo!?
Find a job, post your resume.
http://careers.yahoo.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
That’s certainly true if you want to use the card with the existing network
protocols. I don’t see why that would be true if all you wanted was to give
the application program a IO interface.
You had probably better not use the network class and GUID, through.
++PLS
From: “Maxim S. Shatskih”
>Date: Wed, 7 Nov 2001 08:46:16 +0300
>X-Message-Number: 1
>
>This is a multi-part message in MIME format.
>
>------=_NextPart_000_017F_01C16768.A9F1F270
>Content-Type: text/plain;
> charset=“iso-8859-1”
>Content-Transfer-Encoding: quoted-printable
>
>Impossible, any NIC drivers must have an NDIS upper end.
>
> Max
—
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