[Bug 2939] X11DRV_ChangeDisplaySettingsExW No matching mode found! (NoRes)

[Wine Bugs]

http://bugs.winehq.org/show_bug.cgi?id=2939





------- Additional Comments From inverseparadox at comcast.net  2005-06-05 20:25 -------
I have a similar problem. I was running along quite happily, playing Might and
Magic VI under Wine (it ran almost perfectly, well enough I believe to qualify
for the Gold list), and updating from CVS every few days just on the principle
of the thing; one day it suddenly failed on start in a very similar way. (More
specifics below.) I didn't report it at the time because I wasn't certain the
problem wasn't some aspect of my own system, but I've now taken the time to
revert to earlier versions of Wine CVS, and they are capable of running the game
just fine.

Specifically, the version I get (in an existing Wine checkout, obviously) from

cvs -z3 update -dPA -D 2005-04-24

works, and the version I get from

cvs -z3 update -dPA -D 2005-04-25

does not.

I've looked over the diff between those dates, and I don't see anything which
looks particularly related, but the fact remains that one version works and the
other one doesn't.


The specific failure is as follows: at the point at which the game window pops
up, and the screen would change resolution if I were running the older version,
the window is a blank gray with an "Error" box reading "DDraw ->
SetDisplayMode() failed". In the 2005-04-25 version (see later note), when I
click the OK button in that box, the window disappears and Wine exits. The
messages printed, from run begin to final exit, are:

===
fixme:msvideo:DrawDibRealize (0x1, 0xf4, 0), stub
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
fixme:mci:MCI_LoadMciDriver Couldn't load driver for type L"E:".
If you don't have a windows installation accessible from Wine,
you perhaps forgot to create a [mci] section in system.ini
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x77c1f5f0)->(00020022,00000011
)
err:x11settings:X11DRV_ChangeDisplaySettingsExW No matching mode found! (XF86Vid
Mode)
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x77c1f5f0)->(00000000,00000008
)
===

For comparison, the messages for a similar run (exiting the program at the first
opportunity) in the 2005-04-24 version are

===
fixme:msvideo:DrawDibRealize (0x1, 0xf4, 0), stub
Xlib:  extension "XFree86-DRI" missing on display ":0.0".
fixme:mci:MCI_LoadMciDriver Couldn't load driver for type L"E:".
If you don't have a windows installation accessible from Wine,
you perhaps forgot to create a [mci] section in system.ini
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x77c1f5f0)->(00020022,00000011
)
fixme:xvidmode:X11DRV_XF86VM_SetCurrentMode Cannot change screen BPP from 32 to 
16
fixme:xvidmode:X11DRV_XF86VM_SetCurrentMode Cannot change screen BPP from 32 to 
16
fixme:mci:MCI_LoadMciDriver Couldn't load driver for type L"CDAUDIO".
If you don't have a windows installation accessible from Wine,
you perhaps forgot to create a [mci] section in system.ini
fixme:mci:MCI_LoadMciDriver Couldn't load driver for type L"CDAUDIO".
If you don't have a windows installation accessible from Wine,
you perhaps forgot to create a [mci] section in system.ini
fixme:mmtime:timeBeginPeriod Stub; we set our timer resolution at minimum
fixme:ddraw:DIB_DirectDrawSurface_Blt dwFlags DDBLT_WAIT and/or DDBLT_ASYNC: can
't handle right now.
fixme:mmtime:timeEndPeriod Stub; we set our timer resolution at minimum
fixme:ddraw:Main_DirectDraw_SetCooperativeLevel (0x77c1f5f0)->(00020022,00000008
)
===

(In both cases, the initial 'DrawDibRealize' stub line crops up while the
CD-autorun splash screen is visible, and has no apparent practical effect.)

The most obvious candidate difference is the fact that the 'working' version, at
the point at which the newer version fails, complains about being unable to
switch the screen from 32bpp to 16bpp; it seems possible that the newer version
fails out because it can't do this, but I'm not sure why that would happen.


As an additional note, in still more recent versions (I haven't tracked down the
date of the change, but CVS of yesterday - 2005-05-05 - definitely exhibits this
behaviour), instead of succesful exit when I click the OK button the dialog box
disappears but the gray window remains frozen; Wine does not exit until I either
go back to its terminal and hit Ctrl-Backspace or kill it by some other means.
Whether or not this is at all related I don't know, but it is certainly a
problem, and I felt it was worth mentioning in this context.

It's been suggested to me that adding a 16-bit modeline to my X config might
enable me to run the game just fine, and that may be the case. Testing it,
however, would require me to restart X, and I have many things open which I
don't want to lose any sooner than I need to.

-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.