Fixing the last failing tests

[Dmitry Timoshkov]

"Dan Kegel" <dank at kegel.com> wrote:

> The test you submitted that checks this,
> http://www.winehq.org/pipermail/wine-patches/2005-July/018839.html
> must have passed once on Windows,
> but it seems to be failing now; see e.g.
> http://test.winehq.org/data/200802131000/xp_rs-winxp-sp2/user32:win.txt
> which is full of lines like
> win.c:3656: Test failed: IsWindowUnicode expected to return FALSE
> 
> Do you have a Windows system where that test passes currently?

I've performed a little investigation trying to find out at which point XP
has changed its behaviour. It's pretty much hard taking into account how
many broken user32:win.c tests we have at test.winehq.org (all the tests
marked as 'failed' are useless). It looks like the change/breakage occured
somewhere at the end of October 2007 - beginning of November 2007:

http://test.winehq.org/data/200710271000/xp_brainless-20071027/user32:win.txt
http://test.winehq.org/data/200710271000/xp_mbv-.48/user32:win.txt

don't have failing IsWindowUnicode tests,
but http://test.winehq.org/data/200711072209/#XP suite already has them:

http://test.winehq.org/data/200711072209/xp_200711SCHOEMB/user32:win.txt

-- 
Dmitry.