Hi all,
My Intermediate driver exposes a WAN virtual NIC and
is bound to the NdisWAN driver. The virtual NIC
supports TAPI Oids and is exposed as a dialup device.
This setup works fine on Win 2K. On 98SE, however the
TAPI calls fail in OID_TAPI_GET_DEV_CAPS. A window
which pops up saying TAPISRV.EXE has caused a General
Protection Fault and would be shutdown. The dialup
device does’nt get exposed because of this.
Can anybody throw light upon why the TAPISRV could
throw up a general protection fault.
Thanks,
SSRA
— Syed Ahamed wrote:
> Date: Tue, 28 Aug 2001 08:24:49 -0700 (PDT)
> From: Syed Ahamed
> Subject: [ntdev] Reg. IM Driver in 98SE/ME
> To: “NT Developers Interest List”
>
> Reply-to: “NT Developers Interest List”
>
>
> Hello,
> I’m having a NDIS IM driver for 98SE/ME, which
> exposes
> standard WAN virtual miniports with PPP framing and
> as
> TAPI provider. In this context I’ve got to support
> TAPI OIDs in the driver
>
> However I’ve found no example of how the TAPI OIDs
> are
> handled in 98SE or ME. I’m able to bind to the
> underlying nic properly. (I’m able to verify this
> since I’m able to query the MAC address of the
> underlying miniport successfully).
>
> When I try to create a dialup connection the TAPISRV
> application crashes with a General Protection Fault.
> Can anybody throw more light on this?
>
> Thanks,
> SSRA
>
>
> Do You Yahoo!?
> Make international calls for as low as $.04/minute
> with Yahoo! Messenger
> http://phonecard.yahoo.com/
>
> —
> You are currently subscribed to ntdev as:
> xxxxx@yahoo.com
> To unsubscribe send a blank email to
leave-ntdev-$subst(‘Recip.MemberIDChar’)@lists.osr.com
Do You Yahoo!?
Get email alerts & NEW webcam video instant messaging with Yahoo! Messenger
http://im.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