ping.dll

[tsdt]

Hi Agraham,

I have a device trying to construct a new socket obj in the ping.dll. It gaves socket exception. We have tried to change the ProtocolType to Stream, and SocketType to Tcp in your dll, and no error appears at that portion. However, at the Socket.Sendto() function, I got another socket exception.

If I didnt change the ProtocolType and the SocketType, then, I got a socket exception at the new socket(...), do you have any idea on this?

Thanks.

Best regards,:sign0085:

 

[agraham]

I'm afraid not.

 

[tsdt]

I'm afraid not.

Agraham,

We noticed that the Ping.dll is not support WinCE. In WinCE, it is not using the .NET framework to do the ping. It is using the Icmp directly. Am I right on this??

Have you tested this in WinCE, I wonder?

:sign0089:

 

[agraham]

If I try it on my WinCE netbook I get a "Support for the specified socket type does not exist in the address family" error. However HTTP works fine.

This does not surprise me as what is included in WinCE builds is determined by the device manufacturer so they are not standardised. Because of that I cannot guess what will work and what will not on individual WinCe implementations.

Windows Mobile/Pocket PC is standardised by Microsoft so you always know what is present on such a device. Therefore if it works on my WM2003 Pocket PC it is highly likely to work on my Windows Mobile 6.1 HT Diamond. If at all possible I would always recommend using a Windows Mobile device.

 

[tsdt]

If I try it on my WinCE netbook I get a "Support for the specified socket type does not exist in the address family" error. However HTTP works fine.

Oh.. I am having the same problem too.

This does not surprise me as what is included in WinCE builds is determined by the device manufacturer so they are not standardised. Because of that I cannot guess what will work and what will not on individual WinCe implementations..

I see.. How many solutions are there in total for WinCE?? So far, I know you can also use Icmp in the WinCE to do the ping.

Windows Mobile/Pocket PC is standardised by Microsoft so you always know what is present on such a device. Therefore if it works on my WM2003 Pocket PC it is highly likely to work on my Windows Mobile 6.1 HT Diamond. If at all possible I would always recommend using a Windows Mobile device.

Unfortunately, we need to support both WinCE and WM.

 

[agraham]

I see.. How many solutions are there in total for WinCE??

There is no answer to that question. I don't think anybody can tell you how many individual variants of WinCE are out there.

Unfortunately, we need to support both WinCE and WM.

WM should be no trouble. But you will need to either test on the specific WinCE devices you are targetting or test on what you think is a representative WinCE device and hope it works on others