Hi,
While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at https://testbot.winehq.org/JobDetails.pl?Key=36998
Your paranoid android.
=== wxppro (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w2003std (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== wvistau64 (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== wvistau64_zh_CN (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== wvistau64_fr (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== wvistau64_he (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w2008s64 (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w7u (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w7pro64 (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w8 (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w864 (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w1064 (32 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== wvistau64 (64 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w2008s64 (64 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w7pro64 (64 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w864 (64 bit explorer) === explorer.c:110: Test failed: explorer is not avaible
=== w1064 (64 bit explorer) === explorer.c:110: Test failed: explorer is not avaible