http://bugs.winehq.org/show_bug.cgi?id=5849
------- Additional Comments From tuharsky@misbb.sk 2006-23-08 01:30 ------- Created an attachment (id=3396) --> (http://bugs.winehq.org/attachment.cgi?id=3396&action=view) Logfile, bz2-ed +loaddll,ole,imm,msvcrt,msi OK oleaut32=b
Logfile with builtin oleaut32.
Again, I aborted the program immediately when the (wrong) date displayed.
If I would attemped to change the wrong date, program would just beep upon clicking on "OK" a won't proceed any further.
I mean, GETTING the date from system is the first fault, and SETTING is the second. Of course, they may be connected, they may be caused by the same bug.
However I feel, that it could be better to first solve the date, that program offers (tat he gets from system).
Now, the logs end at the same moment -when program displays the offered "today's date". One can compare, where is the difference between native and builtin oleaut32 behaviour.