This is a multi-part message in MIME format.
------=_NextPart_000_000E_01C578D7.F25D7500
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I am testing my NDISWAN IM driver on PPC 2003 and I find a strange =
problem after the NDISWAN IM driver is initialized. What I found is that =
the upper layer application kept polling the OID_TAPI_GET_DEV_CAPS for =
around seven times. When I plugged the USB cable and turn the AciveSync =
on, my NDISWAN IM driver kept receiving the OID_TAPI_GET_DEV_CAPS , =
which caused the PPC getting into a nonstop loop.=20
Due to the nature of NDISWAN IM driver, it needs not to talk to =
hardware directly and it simply forward the requests to the AsyncMac =
driver. I really do not know why the application is not happy with the =
parameters returned from the OID_TAPI_GET_DEV_CAP. If anybody had such =
a problem before, can you tell me what the problem is.=20
The PPC2003 I am testing is=20
SIEMENS SX66 PPC.
------=_NextPart_000_000E_01C578D7.F25D7500
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2900.2668" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY>
<DIV><FONT face=3DArial>I am testing my NDISWAN IM driver on PPC =
2003 and I=20
find a strange problem after the NDISWAN IM driver is initialized. What =
I found=20
is that the upper layer application kept polling the </FONT><FONT=20
face=3DArial>OID_TAPI_GET_DEV_CAPS for around seven times. When I =
plugged the USB=20
cable and turn the AciveSync on, my NDISWAN IM driver kept =
receiving=20
the OID_TAPI_GET_DEV_CAPS , which caused the PPC getting =
into a=20
nonstop loop. </FONT></DIV>
<DIV><FONT face=3DArial>Due to the nature of NDISWAN IM =
driver, it=20
needs not to talk to hardware directly and it simply forward the =
requests=20
to the AsyncMac driver. I really do not know why the application is not =
happy=20
with the parameters returned from the OID_TAPI_GET_DEV_CAP. =
</FONT><FONT=20
face=3DArial>If anybody had such a problem before, can you tell me what =
the=20
problem is. </FONT></DIV>
<DIV><FONT face=3DArial></FONT> </DIV>
<DIV><FONT face=3DArial>The PPC2003 I am testing is </FONT></DIV>
<DIV><FONT face=3DArial></FONT> </DIV>
<DIV><FONT face=3DArial> =
SIEMENS SX66=20
PPC.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<P><FONT face=3DArial></FONT> </P></BODY></HTML>
------=_NextPart_000_000E_01C578D7.F25D7500--