When running -8 option for direct Ethernet (802.1AS compliant) encapsulation, ptpv2d does IPv4 Multicast group join about ptpv2d HOT 4 OPEN

What is the time precision for this source code running in Windows? I found 
that it seems more than 15ms?

When it comes to precision on my Windows portation, I did not do anything
special when it comes to time adjustment and time accuracy.  

I did not have any experience in doing a Winsock application as this is the
first one I've ever done.

With that, when it came to both socket application and getting/setting time
from the operating system, I did the best I could.

So I'm not surprised that the accuracy is less than Linux as from what I
could tell, standard Windows calls for getting/setting time are not very
accurate.

If you know of a better way that time could be measured and set, I'd be open
to porting it into the code.

Alan

Hi Alan

Thank you for your attention~ I tried to use PTPV2D on the WIndows XP. I found 
some problems as following:

1) I run PTPV2D on 2 computers. After that, according to the debug message of 
msgUnpackV2Header, the time is synchronized. Which API or method is expected to 
use for getting the time which are synchronized? 
- getTime(TimeInternal *time, Integer16 utc_offset)?
- GetSystemTimeAsFileTime?
- etc?

2) When the time is synchronized by using PTPV2D, the system clock will not be 
adjusted(changed) by PTPV2D program . How can I let the program to set the 
system clock in order to let the system clock are synchronized between 2 
computers.

I found that the void updateClock(RunTimeOpts*,PtpClock*) in ptpd_dep.h without 
called.

MCW, comments edited in below.

If you are a member of the ptpv2d google group, please use the ptpv2d group
instead of the issues page on code.google.com.