I have a game I want to run but it wants a 640x480x16-bit screen. Normally I just ctl-alt-- to lower the resolution but it doesn't like that since it keeps the virtual resolution at 1280x1024. I can move the mouse over the entire 1280x1024 and the screen pans with the mouse. How do I disable that? I know the old way by editing the XF86Config file in /etc/X11/ but that doesn't work. In fact, sax2 does some funky stuff editing the files and changing the XF86Config doesn't seem to do anything. Any thought on how I can fix this? John
On Sunday 24 March 2002 02.14, John Scott wrote:
I have a game I want to run but it wants a 640x480x16-bit screen. Normally I just ctl-alt-- to lower the resolution but it doesn't like that since it keeps the virtual resolution at 1280x1024. I can move the mouse over the entire 1280x1024 and the screen pans with the mouse. How do I disable that?
As far as I know this isn't available yet in X 4.x. It will be in a future release.
I know the old way by editing the XF86Config file in /etc/X11/ but that doesn't work.
What way is that?
In fact, sax2 does some funky stuff editing the files and changing the XF86Config doesn't seem to do anything. Any thought on how I can fix this?
sax2 edits the file /etx/X11/XF86Config, that much I can agree with. But I've edited that file many times manually. SuSE's X is in no way dependant on sax2, it is very much possible to edit the config file manually. If you feel your edits aren't taking effect, something else must be wrong. //Anders
andjoh@cicada.linux-site.net wrote:
On Sunday 24 March 2002 02.14, John Scott wrote:
I have a game I want to run but it wants a 640x480x16-bit screen. Normally I just ctl-alt-- to lower the resolution but it doesn't like that since it keeps the virtual resolution at 1280x1024. I can move the mouse over the entire 1280x1024 and the screen pans with the mouse. How do I disable that?
As far as I know this isn't available yet in X 4.x. It will be in a future release.
I know the old way by editing the XF86Config file in /etc/X11/ but that doesn't work.
What way is that?
There used to be a desktop size option waaay back when I used Caldera 1.3 which was about 3 years ago. Don't know which XFree that was. Haven't seen it in 4.x though I don't know that it doesn't exist. It was used in the "screen" section after default depth. ...Not important, just wondering if anyone was using something similar.
In fact, sax2 does some funky stuff editing the files and changing the XF86Config doesn't seem to do anything. Any thought on how I can fix this?
sax2 edits the file /etx/X11/XF86Config, that much I can agree with. But I've edited that file many times manually. SuSE's X is in no way dependant on sax2, it is very much possible to edit the config file manually. If you feel your edits aren't taking effect, something else must be wrong.
//Anders
I figured this second one out. sax keeps a copy in /usr/X11R6/lib/X11/sax/files/XF86Config. If I changed both files then my changes took efffect. I never had to do that before now so I don't know what strangeness is happening with this config. I thought it might be a new SuSEconfig mod of some sort. I can never tell what handmade edits won't have effect because of some rc.config option that needs to be changed. John
On Sunday 24 March 2002 22.02, John Scott wrote:
There used to be a desktop size option waaay back when I used Caldera 1.3 which was about 3 years ago. Don't know which XFree that was. Haven't seen it in 4.x though I don't know that it doesn't exist. It was used in the "screen" section after default depth. ...Not important, just wondering if anyone was using something similar.
That's still there. It's "Virtual x y", but since it's static I didn't think that was what you wanted. The virtual desktop isn't changed when you resize with ctrl-alt-+. I read somewhere that this functionality is being worked on. Some programs get around this by grabbing the mouse so you can't go outside the window area, so you're tricked into thinking the virtual desktop has changed even though it hasn't. That has to be done inside the program, though.
I figured this second one out. sax keeps a copy in /usr/X11R6/lib/X11/sax/files/XF86Config. If I changed both files then my changes took efffect. I never had to do that before now so I don't know what strangeness is happening with this config. I thought it might be a new SuSEconfig mod of some sort. I can never tell what handmade edits won't have effect because of some rc.config option that needs to be changed.
No such file here (SuSE 7.3) Changes I make in /etc/X11/XF86Config take effect. //Anders
andjoh@cicada.linux-site.net wrote:
On Sunday 24 March 2002 22.02, John Scott wrote:
There used to be a desktop size option waaay back when I used Caldera 1.3 which was about 3 years ago. mething similar.
That's still there. It's "Virtual x y", but since it's static I didn't think that was what you wanted. The virtual desktop isn't changed when you resize with ctrl-alt-+. I read somewhere that this functionality is being worked on.
ah. Don't quote me as it was a long time ago but I believe the option was Virtual = none or something to that effect. I noticed I didn't need the option after my next upgrade so it's been long forgotten until now.
sax keeps a copy in /usr/X11R6/lib/X11/sax/files/XF86Config. If I changed both files then my changes took efffect. I never had to do that before now so I don't know what strangeness is happening with this config. I
No such file here (SuSE 7.3) Changes I make in /etc/X11/XF86Config take effect.
//Anders
That's wierd. I did a fresh install of 7.3 a couple months ago. This is the first instance where I needed be concerned about X. I upgraded my nVidia drivers and ran sax2 to turn on 3d accel. My 1280x1024 desktop was gone and replaced with 1024x768. ctl-alt-(+/-) had no effect. A look inside /etc/X11/XF86Config revealed that sax only put 1 res on the mode line (despite my having put 5during setup). I simply changed the file back with the resolutions I needed but nothing happened. I got extremely frustrated that my /etc/X11/XF86Config changes were not having effect so I did "locate XF86Config". It revealed the other copy. I re-edited /etc/X11/XF86Config (it had reverted after suseconfig was run again) then copied it over the sax copy and that worked.
participants (2)
-
Anders Johansson
-
John Scott