Hello ,
> I have written the solution A. Ndis driver is loaded
XH> Thank you greatly.
XH> Can NDISWAN use IoXXXXX functions? I should
XH> support boht 98 and NT.
Yes is no Problem. I have written USB driver and NDIS for Windows
2000, Windows NT 4.0, Windows 95, Windows 98x
The best way to have no trouble in Windows 98 to compile your code
with NDIS.H and NTDDK.H is put all your code with
IoCallDriver … in a kernel mode DLL. Than can you call from your
NDIS driver a simple function API like openChannel, closeChannel …
In Windows 2000 the situation is much better (NDIS_WDM) flag, bud
the same solution works.
> You now the name of your USB driver object and can
> use IoGetDeviceObjectPointer to open the USB
> driver and ObDereferenceObjet to close.
XH> There is a new function in NDIS 5.0
XH> IoGetDeviceInterface
XH> Waht about it?
This normal Kernal API function call’s, You can use them for
NDIS ISDN drivers.
> > Also I should implement CAPI 2.0 support.
>
XH> But the IHV requires for it.Where can I put CAPI
XH> codes? in USB WDM driver.
XH> And CAPI also should provide a VxD on 98.And how
XH> VxD call a WDM driver?
Than you have a big problem to write CAPI 2.0 stuff
will some D-Channel protocols and B-Channel protocols
like X.75, X.25, V.120, V.110 … Many Many man years
software development or your company has enough money
and can buy all driver (NDIS, CAPI, …)source code
or binarie licenses. I know such company www.stollmann.de
For CAPI architecture support here exist 2 ways.
One way, put all your CAPI code in one or two WDM driver.
The lower interface is USB.
The NDIS driver is based on CAPI and use the CAPI interface
for connection data transfer management.
In Windows 98 you can write a simple VXD to support the CAPI
VXD interface. You must write the CAPI2032.DLL for user mode
application based on DeviceIoControl with the CAPI driver.
The second way, put all your Code in a NDIS driver. Use
the USB driver for Low Level ISDN access. Have a internal
CAPI interface. Use the internal CAPI interface to build
the TAPI stuff inside the NDIS driver.
Write VXD (Windows 98) and SYS (Windows 2000) protocol driver
with upper level CAPI interface and lower level NDIS interface
into your NDIS driver.
Enough work for you ?
I write this stuff since 5 years and now I m feel bored.
Enjoy