hello all,
I have completed a port driver and a ndis driver ,if i want to install these driver into the same device. what modification should i do at least in the INF? I have 5 files, usb2ser.sys and usbport.inf wdfcoinstaller01009.dll are for the port driver , ndis.sys and ndis.inf are for NDIS driver.
Now i modify the INF [Manufacturer] section with the same PID VID ,and include the usbport.inf in the ndis.inf ,and just install driver with ndis.inf ,and i found that the usbpost driver didn’t be installed ,so i think there would be a key SECTION to specify the driver stack layer , does it ? or notice me the releveant document would be help.
Any help would be appreciate. thanks in advance!
Can I assume that your driver isn’t really named ndis.sys?
Bill Wandel
-----Original Message-----
From: xxxxx@lists.osr.com
[mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Tuesday, March 15, 2011 10:58 PM
To: Windows System Software Devs Interest List
Subject: [ntdev] Install the driver into one stack with INF
hello all,
I have completed a port driver and a ndis driver ,if i want to install these
driver into the same device. what modification should i do at least in the
INF? I have 5 files, usb2ser.sys and usbport.inf wdfcoinstaller01009.dll are
for the port driver , ndis.sys and ndis.inf are for NDIS driver.
Now i modify the INF [Manufacturer] section with the same PID VID ,and
include the usbport.inf in the ndis.inf ,and just install driver with
ndis.inf ,and i found that the usbpost driver didn’t be installed ,so i
think there would be a key SECTION to specify the driver stack layer , does
it ? or notice me the releveant document would be help.
Any help would be appreciate. thanks in advance!
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at
http://www.osronline.com/page.cfm?name=ListServer
>Can I assume that your driver isn’t really named ndis.sys?
yes , just for easy to understand the meaning. sorry ,you can call it ndisnet.sys any way. it’s not the driver of MSFT.
Anyone please update
for the driver stack would be like below. i just want to install the device driver into one stack with one INF, But i cannot find the docunment talk about this stack.
App
|
|
NDIS driver
|
|
Com Port
|
|
Lower driver
IIRC, the com port is the device, ie you do not have to talk to some physical com port and the device behind the connector. In that case, you have driver, ie your NDIS miniport: which registers with NDIS, accepts NDIS packets. When process NDIS packets and OIDs, internally uses the COM port protocol for your device (IIRC, it is USB, so URBs) and send the requests to the hw. No need to have a 2nd driver underneath.
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Wednesday, March 16, 2011 7:50 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Install the driver into one stack with INF
Anyone please update
for the driver stack would be like below. i just want to install the device driver into one stack with one INF, But i cannot find the docunment talk about this stack.
App
|
|
NDIS driver
|
|
Com Port
|
|
Lower driver
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
xxxxx@hotmail.com wrote:
Anyone please update
for the driver stack would be like below. i just want to install the device driver into one stack with one INF, But i cannot find the docunment talk about this stack.
App
|
|
NDIS driver
|
|
Com Port
|
|
Lower driver
You were the fellow who was asking about USB serial ports, weren’t you?
If you want a network-like interface, why on earth would you throw a
serial port in the mix? Why not just make a USB Ethernet interface?
That’s supported.
If you really need NDIS -> Serial -> USB, then you will need two INF
files. There is no way around it. You have drivers in two completely
different install classes.
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>IIRC, the com port is the device, ie you do not have to talk to some physical
com port and the device behind the connector. In that case, you have driver, ie
your NDIS miniport: which registers with NDIS, accepts NDIS packets. When
process NDIS packets and OIDs, internally uses the COM port protocol for your
device (IIRC, it is USB, so URBs) and send the requests to the hw.
Yes , exactly the same as what you said.
No need to have a 2nd driver underneath.
i have some self define AT command to be sent by this com port driver.so i try to insert the com port driver into the stack, so i can tansfer the data by NDIS , or program an application to send AT cmd to get information from the com port.
So i know that i just need one INF to install the com port driver and NDIS together. the NDIS just get the lower device interface to send URB , and the com port still can get the Information
App1 APP2
| |
| |
NDIS driver |
| |
| |
Com Port <----------
|
Com ports are exclusive devices, you can’t have the app and your ndis driver talk to it at the same time
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Thursday, March 17, 2011 8:12 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Install the driver into one stack with INF
IIRC, the com port is the device, ie you do not have to talk to some
physical com port and the device behind the connector. In that case,
you have driver, ie your NDIS miniport: which registers with NDIS,
accepts NDIS packets. When process NDIS packets and OIDs, internally
uses the COM port protocol for your device (IIRC, it is USB, so URBs) and send the requests to the hw.
Yes , exactly the same as what you said.
No need to have a 2nd driver underneath.
i have some self define AT command to be sent by this com port driver.so i try to insert the com port driver into the stack, so i can tansfer the data by NDIS , or program an application to send AT cmd to get information from the com port.
So i know that i just need one INF to install the com port driver and NDIS together. the NDIS just get the lower device interface to send URB , and the com port still can get the Information
App1 APP2
| |
| |
NDIS driver |
| |
| |
Com Port <----------
|
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>You were the fellow who was asking about USB serial ports, weren’t you?
If you want a network-like interface, why on earth would you throw a
serial port in the mix? Why not just make a USB Ethernet interface?
That’s supported.
Yes ,i am.
well ,NDIS is optional or trigger. and sometimes i would like to sent AT command directly by com port.
>Com ports are exclusive devices, you can’t have the app and your ndis driver
talk to it at the same time
does NDIS initialise always open com port ? if is not . how about not to open the com port in the driver . before app2 use it , i close the comport in app1?
I would imagine that yes, the ndis stack you build will always open the com port. How else will you complete the network traffic coming through your ndis stack? You are making your life very complicated by attempting to share the com port. Redesign not to do that
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Thursday, March 17, 2011 9:36 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Install the driver into one stack with INF
Com ports are exclusive devices, you can’t have the app and your ndis
driver talk to it at the same time
does NDIS initialise always open com port ? if is not . how about not to open the com port in the driver . before app2 use it , i close the comport in app1?
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>I would imagine that yes, the ndis stack you build will always open the com
port. How else will you complete the network traffic coming through your ndis
stack? You are making your life very complicated by attempting to share the com
port. Redesign not to do that
Thanks Doron ,you are help to me.
Hello Doron, i have another idea.
For my device i still it as com port class .after that i install the NDIS without device .
and in the NDIS driver initialise function , i open the com port device interface as the NDIS next lower driver .if i want to reuse the com port driver ,i just remove the NDIS driver to free the com port ?
then the com port is available again. As modem creation .i specified the com port number for NDIS.
Seems quite cumbersome and entirely unintuitive for your users
d
-----Original Message-----
From: xxxxx@lists.osr.com [mailto:xxxxx@lists.osr.com] On Behalf Of xxxxx@hotmail.com
Sent: Thursday, March 17, 2011 10:46 PM
To: Windows System Software Devs Interest List
Subject: RE:[ntdev] Install the driver into one stack with INF
Hello Doron, i have another idea.
For my device i still it as com port class .after that i install the NDIS without device .
and in the NDIS driver initialise function , i open the com port device interface as the NDIS next lower driver .if i want to reuse the com port driver ,i just remove the NDIS driver to free the com port ?
then the com port is available again. As modem creation .i specified the com port number for NDIS.
NTDEV is sponsored by OSR
For our schedule of WDF, WDM, debugging and other seminars visit:
http://www.osr.com/seminars
To unsubscribe, visit the List Server section of OSR Online at http://www.osronline.com/page.cfm?name=ListServer
>Seems quite cumbersome and entirely unintuitive for your users
if you have any suggestions that provide the user choice to select the dial up method.
our customer would like to dial up to internet with NDIS mode , and if they wish ,they can too dial up with com port according to MS 's modem method.
wrote in message news:xxxxx@ntdev…
>>Seems quite cumbersome and entirely unintuitive for your users
>
> if you have any suggestions that provide the user choice to select the
> dial up method.
>
> our customer would like to dial up to internet with NDIS mode , and if
> they wish ,they can too dial up with com port according to MS 's modem
> method.
>
Have you considered Connection-Oriented NDIS?
http://msdn.microsoft.com/en-us/library/ff545201(v=VS.85).aspx
– pa
xxxxx@hotmail.com wrote:
> You were the fellow who was asking about USB serial ports, weren’t you?
> If you want a network-like interface, why on earth would you throw a
> serial port in the mix? Why not just make a USB Ethernet interface?
> That’s supported.
Yes ,i am.
well ,NDIS is optional or trigger. and sometimes i would like to sent AT command directly by com port.
PLEASE describe your hardware for us. I, for one, am suspicious that
you are marching down the wrong path. If you have AT commands, then
there must be a modem somewhere. Are you just making a USB modem? If
so, can’t you just advertise a Modem device, and let the operating
system run PPP on top of that to do networking?
–
Tim Roberts, xxxxx@probo.com
Providenza & Boekelheide, Inc.
>PLEASE describe your hardware for us. I, for one, am suspicious that
you are marching down the wrong path. If you have AT commands, then
there must be a modem somewhere. Are you just making a USB modem? If
so, can’t you just advertise a Modem device, and let the operating
system run PPP on top of that to do networking?
Tim ,you are intelligent.
My hardware is a Phone ,It has a modem there and support AT command ,
for some customers ,they would like to plug in the phone into PC and virtual a Network Card in the Netork Connection and they can directly enjoy the Internet Service without dial up procedure.
With compatibility reason, I have to keep the “com port”.
So i try to create a NDIS driver to generate *NETWORK CARD* device , and the data will be transmitted via com port to device , i would package the AT command in the NDIS driver and send it to com port . i am doing survey if the NDIS and com port can be installed together, or respectively install.
if they can be installed together , that the com port driver would be a lower driver .
if they can not be installed together ,then i should search the com port device interface first . and send the IRP to it from NDIS driver.
>Netork Connection and they can directly enjoy the Internet Service without dial up procedure.
If your task is this simple, I would suggest to install the AutoRun app which will note the arrival of your device and immediately do the RAS call for dialup, without notifying the user.
Dialup procedure is as easy as a) starting some app b) pressing the large Connect button in it. Both steps can be trivially automated.
I do not think writing an NDIS miniport is worth your time for such a simple task. Also note that emulating Ethernet over point-to-point link is a bit illogical, and you will have some issues with IP and MAC addressing there. For instance, you will need to spend 4 IP addresses per link, not 1 as with PPP.
–
Maxim S. Shatskih
Windows DDK MVP
xxxxx@storagecraft.com
http://www.storagecraft.com