Hi,
I am writing a NDIS-WDM wan miniport driver which support tapi, it’s lower
range is the os’s internal serial driver.
My driver is based on the ISDNWAN driver in the DDK, and my os is win2k sp3.
I use dial-up connections to dial out with using my driver’s wan adapter. In
the OID_TAPI_MAKE_CALL, I dial the tel number transfer with this oid ,after
tel is connected, I indicate line-up and LINECALLSTATE_CONNECTED then I get
a get OID_TAPI_GET_ID , then I get a OID_WAN_SET_LINK_INFO. All seems ok, I
think maybe I can send and receive package now, but os crashed after I
returned NDIS_STATUS_SUCCESS in OID_WAN_SET_LINK_INFO request. I don’t know
why and where, can anybody help me?
Thanks sooooo much for any thing you may be able to offer.
Patrick Wen
IIRC such drivers are obsoleted, and CoNDIS WAN miniports are the current model.
Max
----- Original Message -----
From: fwen
To: NT Developers Interest List
Sent: Thursday, December 19, 2002 4:30 AM
Subject: [ntdev] my tapi miniport driver crashed after line up
Hi,
I am writing a NDIS-WDM wan miniport driver which support tapi, it’s lower
range is the os’s internal serial driver.
My driver is based on the ISDNWAN driver in the DDK, and my os is win2k sp3.
I use dial-up connections to dial out with using my driver’s wan adapter. In
the OID_TAPI_MAKE_CALL, I dial the tel number transfer with this oid ,after
tel is connected, I indicate line-up and LINECALLSTATE_CONNECTED then I get
a get OID_TAPI_GET_ID , then I get a OID_WAN_SET_LINK_INFO. All seems ok, I
think maybe I can send and receive package now, but os crashed after I
returned NDIS_STATUS_SUCCESS in OID_WAN_SET_LINK_INFO request. I don’t know
why and where, can anybody help me?
Thanks sooooo much for any thing you may be able to offer.
Patrick Wen
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to %%email.unsub%%
Tank you for your help.
I changed ndis version to 4 now. After PPP connection setup completely, ndis will call my NdisWanSend function to send IP packet, but system will crash at the second time.
I traced it, it always crash at KeWaitForSingleObject which I called after I send a IRP_MJ_WRITE irp to lower serial driver, and the crash messages is ATTEMPTED_SWITCH_FROM_DPC, I don’t know how to resolve this question. Please give me some suggestion.
----- Original Message -----
From: Maxim S. Shatskih
To: NT Developers Interest List
Sent: Wednesday, December 18, 2002 10:38 AM
Subject: [ntdev] Re: my tapi miniport driver crashed after line up
IIRC such drivers are obsoleted, and CoNDIS WAN miniports are the current model.
Max
----- Original Message -----
From: fwen
To: NT Developers Interest List
Sent: Thursday, December 19, 2002 4:30 AM
Subject: [ntdev] my tapi miniport driver crashed after line up
Hi,
I am writing a NDIS-WDM wan miniport driver which support tapi, it’s lower
range is the os’s internal serial driver.
My driver is based on the ISDNWAN driver in the DDK, and my os is win2k sp3.
I use dial-up connections to dial out with using my driver’s wan adapter. In
the OID_TAPI_MAKE_CALL, I dial the tel number transfer with this oid ,after
tel is connected, I indicate line-up and LINECALLSTATE_CONNECTED then I get
a get OID_TAPI_GET_ID , then I get a OID_WAN_SET_LINK_INFO. All seems ok, I
think maybe I can send and receive package now, but os crashed after I
returned NDIS_STATUS_SUCCESS in OID_WAN_SET_LINK_INFO request. I don’t know
why and where, can anybody help me?
Thanks sooooo much for any thing you may be able to offer.
Patrick Wen
You are currently subscribed to ntdev as: xxxxx@storagecraft.com
To unsubscribe send a blank email to %%email.unsub%%
You are currently subscribed to ntdev as: xxxxx@utstar.com
To unsubscribe send a blank email to xxxxx@lists.osr.com