http://bugs.winehq.org/show_bug.cgi?id=28217
--- Comment #7 from Murray Colpman muzerakascooby@gmail.com 2011-11-15 16:12:31 CST --- I just did four regression tests for various stages.
Working 1.3.25 --> error message* 1.3.26:
d4076d438cb5ff05f6800cdaae7ac88844e70595 is the first bad commit commit d4076d438cb5ff05f6800cdaae7ac88844e70595 Author: Huw Davies huw@codeweavers.com Date: Tue Aug 2 14:11:10 2011 +0100
gdi32: Add a PutImage implementation to the dib driver.
:040000 040000 0be7c823d7ba618160e18b0889a0a94956f61183 a01acea3ceb2ad8781388283699d0c8243b90f7f M dlls
Error message 1.3.26 --> working pre-1.3.27: 40742c2f725e8a5f987471ccaafb59aa5c03820d is the first bad commit commit 40742c2f725e8a5f987471ccaafb59aa5c03820d Author: Huw Davies huw@codeweavers.com Date: Fri Aug 19 16:26:10 2011 +0100
gdi32: Fix colour table comparison.
:040000 040000 f2530c089c0a598b7813d1745c4ca43d54534547 5facc52659013eca0d8fb4f003b112bb7a7c5733 M dlls
Working pre-1.3.27 --> palette bug 1.3.27: abf8728e1f2f966650eaa5528a1f593a6e1986bb is the first bad commit commit abf8728e1f2f966650eaa5528a1f593a6e1986bb Author: Ričardas Barkauskas rbarkauskas@codeweavers.com Date: Mon Aug 8 01:26:00 2011 +0300
ddraw: Don't allow setting palette on non root surfaces.
:040000 040000 0c4c8222a2357e428cfc3dcbacda0332d4b08e72 2aa2d93bfcf700126a46bff963c8857a9bc8e822 M dlls
palette bug 1.3.27 --> black screen:
94ae743ea668e49d40ae4e2dc5fe1f5d9be018cb is the first bad commit commit 94ae743ea668e49d40ae4e2dc5fe1f5d9be018cb Author: Henri Verbeet hverbeet@codeweavers.com Date: Tue Aug 30 20:12:31 2011 +0200
ddraw: Make the OpenGL renderer the default one.
:040000 040000 fbce2dc172258a4a7eabc65b6f86bd58522b4667 dfb3b24196ac3ad09100758a48b2d4ef7e45e26b M dlls
Note that the black screen-ness manifests itself in a few ways that I've seen - in versions directly after that change it crashes straight after the intro with a stack error, as well as displaying messages to the effect that it shouldn't be running that code. Later on, it does the same but with freezing instead of crashing. Still later, the frontend appears to work "behind" the blackness, but I can't see much (just get the occasional white outlines of things, as you would normally if a Windows system was having the same issue). If you want me to regression test /these/, I can as well, but I think I'm all regression tested out for today ;)
*I did write down the error message, but I've lost it, and I don't want to install that version of wine to get it again - it was one generated by the game, about failing to load some resources required for the frontend, or something to that affect.