Le dimanche 09 mai 2010 11:05:55, Stefan Leichter a écrit :
> Failing tests on wine needs to be marked with the todo_wine macro
Yes, but as I said in my first mail I would prefer to get hints on how this
should be fixed. I know nothing about path handling in wine, if it turns out
to be trivial t
Am Sunday 09 May 2010 10:26:07 schrieb Vincent Pelletier:
> This test passes on win2k & winxp, fails on wine.
>
Failing tests on wine needs to be marked with the todo_wine macro see
http://www.winehq.org/site/docs/winedev-guide/testing-platforms and
http://www.winehq.org/pipermail/wine-devel/200
Le samedi 08 mai 2010 18:14:49, Vincent Pelletier a écrit :
> This test passes on win2k & winxp, fails on wine.
Bug opened for this issue:
http://bugs.winehq.org/show_bug.cgi?id=22635
Updated patch, with (too ?) many more test cases.
Interesting URLs:
http://msdn.microsoft.com/en-
us/library/aa3
This test passes on win2k & winxp, fails on wine.
That failure causes cdkey verification problems in "Earth 2160" as sold on
GOG.com:
Once the installation is finished, the installers generates a registry key
value based (among other things) on the ctime of installed directory.
Looked-up path has
