At 06:42 PM 2/1/99 +0100, Oeystein Folkvord wrote:
[deleted]
>I used XF86Config to do this, but I have never seen X behave like this
>afterwards.. Should I try another server than SVGA, or is this just a
>matter of hacking the /etc/XF86Config in the right way ?
I'm getting a bit confused. What do you mean when you say you "used"
XF86Config? /etc/XF86Config is a text file that X reads when it starts to
get its configuration parameters. You can edit it like any text file, or you
can use a special config program to create one. Two examples of config
programs are xf86config and XF86Setup.
Any, my first suggestion is that you use xf86config to generate a clean
XF86Config and see if that solves your problem.
If that is impractical, or if it doesn't eliminate the problem, then notice
*when* the problem starts. On the screen that comes up briefly before the
window manager (xvwm2-95, I'm guessing from your earlier comment about a big
"Start" button), is the X that represents the mouse cursor notmal size of
oversized? Does the chord CTRL-ALT-NP+ (nothing else; no numbers) or the
chord CTRL-ALT-NP-[minus] change the size?
If you are using the SVGA server, your problem is unlikely to be with the
video card, but you might be giving X the wrong settings for your monitor.
Also, if you edited XF86Config by hand, it is possible that the symlink from
X isn't set correctly to point (eventually) to XF86_SVGA.
Sorry if some of this is too basic -- from your messages, it's hard to tell
what you alread know and what you've tried. In any case, I hope some of this
is helpful. Good luck.
------------------------------------"Never tell me the odds!"---
Ray Olszewski -- Han Solo
762 Garland Drive
Palo Alto, CA 94303-3603
650.321.3561 voice 650.322.1209 fax [EMAIL PROTECTED]
----------------------------------------------------------------
