Request advice on USB ISDN TA Driver architecture.

NTDEV
1

Request advice on USB ISDN TA Driver architecture.
Dear all,
I am now developing an USB ISDN TA Driver for 98/NT.
I decide use the following architecture.
The driver solution contains following compoment:
(a). NDISWAN miniport driver which provides a
interface
to NDIS wrapper.It contains only NDISWAN miniport
functions
and TAPI implementation.It call USB WDM driver
through
CAPI 2.0 kernel mode interface to fulfill
ISDN functions.
(b). USB WDM driver. It implements ISDN L2 L3 protocol
and device
management.It provides a CAPI 2.0 kernel mode
interface to
NDISWAN miniport driver and user mode DLLs.
(c). CAPI2032.DLL It implements CAPI 2.0 32 bits DLL,
it call
USB WDM driver to fulfill CAPI functions.
(d). CAPI20.DLL It implements CAPI 2.0 16 bits DLL, it
call
USB WDM driver to fulfill CAPI functions.
** Can anyone tell me how this DLL fulfill CAPI
functions under
Windows 2000, since it is a 16 bits DLL and
can not call USB WDM driver **
(e). Win98 CAPI 2.0 VxD. Implements CAPI 2.0 32 bits
kernel mode functions. Can a VxD call a WDM
driver? It not, how can I
implements the CAPI 2.0 function in this VxD?
Other questions:
(1) In NDIS 5.0, It looks like that we can put (a) and
(b)'s function
into only *ONE* driver following a MS knowledge
base, is this
a better solution?
(2) Which is the difficult driver to implements
between (a) and (b) if
my ISDN TA is a Active TA?
(3) How many time and how many lines of code will this
project cost?
Thanks.
(Mail me at xxxxx@yahoo.com will be more thanks).
BR
Volition2k.
Is this

=====
|-------------------------------|
Behold, galvatron.
|+++++++++++++++++++++++++++++++|

Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

2

  1. The single driver solution is easier to implement and easier to debug.

  2. The approximate number of lines of code required is:
    the number of lines of code for your CAPI driver +
    the number of lines of code for the NDISWAN sample driver +
    the number of line of code for your CAPI / NDISWAN interface.

-Ed Hamlet

Xu Hui @lists.osr.com on 06/26/2000 07:27:05 PM

Please respond to “NT Developers Interest List”

Sent by: xxxxx@lists.osr.com

To: “NT Developers Interest List”
cc:
Subject: [ntdev] Request advice on USB ISDN TA Driver architecture.

Request advice on USB ISDN TA Driver architecture.
Dear all,
I am now developing an USB ISDN TA Driver for 98/NT.
I decide use the following architecture.
The driver solution contains following compoment:
(a). NDISWAN miniport driver which provides a
interface
to NDIS wrapper.It contains only NDISWAN miniport
functions
and TAPI implementation.It call USB WDM driver
through
CAPI 2.0 kernel mode interface to fulfill
ISDN functions.
(b). USB WDM driver. It implements ISDN L2 L3 protocol
and device
management.It provides a CAPI 2.0 kernel mode
interface to
NDISWAN miniport driver and user mode DLLs.
(c). CAPI2032.DLL It implements CAPI 2.0 32 bits DLL,
it call
USB WDM driver to fulfill CAPI functions.
(d). CAPI20.DLL It implements CAPI 2.0 16 bits DLL, it
call
USB WDM driver to fulfill CAPI functions.
Can anyone tell me how this DLL fulfill CAPI
functions under
Windows 2000, since it is a 16 bits DLL and
can not call USB WDM driver
(e). Win98 CAPI 2.0 VxD. Implements CAPI 2.0 32 bits
kernel mode functions. Can a VxD call a WDM
driver? It not, how can I
implements the CAPI 2.0 function in this VxD?
Other questions:
(1) In NDIS 5.0, It looks like that we can put (a) and
(b)'s function
into only ONE driver following a MS knowledge
base, is this
a better solution?
(2) Which is the difficult driver to implements
between (a) and (b) if
my ISDN TA is a Active TA?
(3) How many time and how many lines of code will this
project cost?
Thanks.
(Mail me at xxxxx@yahoo.com will be more thanks).
BR
Volition2k.
Is this

=====
|-------------------------------|
Behold, galvatron.
|+++++++++++++++++++++++++++++++|

__________________________________________________
Do You Yahoo!?
Get Yahoo! Mail - Free email you can access from anywhere!
http://mail.yahoo.com/

—
You are currently subscribed to ntdev as: xxxxx@conexant.com
To unsubscribe send a blank email to $subst(‘Email.Unsub’)