http://bugs.winehq.com/show_bug.cgi?id=656
*** shadow/656 Fri May 10 16:53:51 2002 --- shadow/656.tmp.17031 Fri May 10 17:15:07 2002 *************** *** 9,15 **** +----------------------------------------------------------------------------+ | Assigned To: wine-bugs@winehq.com | | Reported By: michaelc@lindows.com | - | CC list: Cc: | +----------------------------------------------------------------------------+ | Milestone: TargetMilestone: --- | | URL: | --- 9,14 ---- *************** *** 74,76 **** --- 73,92 ---- ------- Additional Comments From vberon@mecano.gme.usherb.ca 2002-05-10 16:53 ------- Created an attachment (id=89) Small test case for FileTimeToLocalFileTime and FileTimeToSystemTime + + + ------- Additional Comments From vberon@mecano.gme.usherb.ca 2002-05-10 17:15 ------- + Michael, could you try the program I attached to the bug? It should compile under WineLib or + Windows. I can't attach a Windows binary, as the compiler I have access to forbids the + redistribution of executables done with it. + + The results I have under Windows NT 4.0 SP? is that the first printed time is UTC, and the second is + local to my TZ (EDT). Those results are the same with Wine, with the exception that the Milliseconds + field is always 0 in the case of GetFileTime (filesystem limitation?). + + The 2 Time*To*Timefunctions seem OK then. The same usage on Windows and Wine gives the same results. + Given some time, I'll try to do a regression test for those 2. + + So it's something else, very probably wrt to UTC vs local time conversion (or absence thereof). Is + there a call to GetSystemTime or a similar function sometime before? If you still have the log (or + can produce another one with the same symptoms), could you compress it and mail it to me? Thank you \ No newline at end of file
-
wine-bugs＠winehq.com