Oh, my apologies, i thought i had the terminology down pat, but i guess not!<br>I added a comment correcting myself on the appdb.<br><br>On the actual code, i think the bug lies somewhere in:<br>IWineD3DPaletteImpl_SetEntries
<br><br>During the menus this is called repeatedly.<br><br>Which looking at the source (wined3d/palette.c) there is a comment<br>about problems with depth conversion (which Carmageddon runs in 8 bit)<br>so I'm working on the assumption thats where the problem lies.
<br><br>Tonight I plan to do some testing on that to see what i can find.<br><br><div><span class="gmail_quote">On 2/13/07, <b class="gmail_sendername">Stefan D�singer</b> <<a href="mailto:stefandoesinger@gmx.at">stefandoesinger@gmx.at
</a>> wrote:</span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">> wine explorer /desktop=foo,640x480 CARM95.EXE<br>Yes, you're mangling the terminology here. What you do here is a virtual
<br>desktop. Managed mode means that the windows are managed by the X11 window<br>manager(so they have the window decorations like Linux apps and can be<br>minimized as normal), while unmanaged mode means that wine manages them, they
<br>have windows 95-style decos and stay on top of all Linux apps. Managed mode<br>is the default, I think you can enable unmanaged mode with a registry switch.<br><br></blockquote></div><br>-- <br>Nathan