(In reply to comment #13)
> (In reply to comment #12)
> > If they are 32-bit games, you'll hit the same issue.
> 
> Not meaning to question your expertise, but would you care to explain: if
> "wine requires 32-bit 3D driver" why virtual desktop (i.e. non-fullscreen)
> mode is running just fine? In my layman view this would mean wine's
> perfectly able to handle the 2D rendering and display on it's part without
> having to install 32-bit 3D driver (which in my case would require complete
> switch to closed source catalyst package and I'm a bit reluctant to do so).

You can install a 32 bit version of the open source 3D driver as well.  Just
because the graphics in a game do not appear to be 3D, they generally still use
a 3D API (OpenGL or Direct3D) which requires a 32 bit 3D driver since the apps
are 32 bit.  Also there seem to be several possibly unrelated issues now piled
onto this bug.