VOGONS


First post, by masavishnu

User metadata
Rank Newbie
Rank
Newbie

It seems that Nvidia proprietary drivers and Dosbox don't mix. No configuration combination seems to be able to provide me with the desired scaling result. I would simply like to have the output scaled on my full screen, preferably without any filters. All I get is a small, postal-stamp-sized image in the middle of the screen.

Also, trying to run dosbox at lower resolutions than my primary resolution (1024*768@100 Hz) just doesn't work in full screen. At the moment I enable full screen, dosbox dies with the following message:

X Error of failed request: BadValue (integer parameter out of range for operation)
Major opcode of failed request: 135 (XFree86-VidModeExtension)
Minor opcode of failed request: 10 (XF86VidModeSwitchToMode)
Value in failed request: 0x135
Serial number of failed request: 153
Current serial number in output stream: 155

I suppose it's sdl-related as scummvm seems to be suffering from the same fault, too.

Any suggestions?

I'm running Gentoo Linux. A small summary of relevant information:

$X -version

X Window System Version 7.0.0
Release Date: 21 December 2005
X Protocol Version 11, Revision 0, Release 7.0
Build Operating System:Linux 2.6.16-gentoo-r13 i686
Current Operating System: Linux shilka 2.6.17-gentoo-r4 #2 SMP PREEMPT Thu Aug 3 16:30:52 EEST 2006 i686
Build Date: 21 July 2006
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Module Loader present

$uname -r
2.6.17-gentoo-r4

nvidia-kernel version 1.0.8762-r1

Reply 1 of 2, by Qbix

User metadata
Rank DOSBox Author
Rank
DOSBox Author

dosbox will probably attempt to set 640x480x70 when in fullscreen.

You can play with the output settings in dosbox.

Water flows down the stream
How to ask questions the smart way!

Reply 2 of 2, by masavishnu

User metadata
Rank Newbie
Rank
Newbie
Qbix wrote:

dosbox will probably attempt to set 640x480x70 when in fullscreen.

Thanks. This inspired me to make some changes to my xorg.conf, which seems to have cured the problem.