<HTML
><HEAD
><TITLE
>XFree86</TITLE
><META
NAME="GENERATOR"
CONTENT="Modular DocBook HTML Stylesheet Version 1.76b+
"><LINK
REL="HOME"
TITLE="The X Window User HOWTO"
HREF="index.html"><LINK
REL="PREVIOUS"
TITLE="Introduction"
HREF="intro.html"><LINK
REL="NEXT"
TITLE="Running X"
HREF="runningx.html"></HEAD
><BODY
CLASS="SECT1"
BGCOLOR="#FFFFFF"
TEXT="#000000"
LINK="#0000FF"
VLINK="#840084"
ALINK="#0000FF"
><DIV
CLASS="NAVHEADER"
><TABLE
SUMMARY="Header navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TH
COLSPAN="3"
ALIGN="center"
>The X Window User HOWTO</TH
></TR
><TR
><TD
WIDTH="10%"
ALIGN="left"
VALIGN="bottom"
><A
HREF="intro.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="80%"
ALIGN="center"
VALIGN="bottom"
></TD
><TD
WIDTH="10%"
ALIGN="right"
VALIGN="bottom"
><A
HREF="runningx.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
></TABLE
><HR
ALIGN="LEFT"
WIDTH="100%"></DIV
><DIV
CLASS="SECT1"
><H1
CLASS="SECT1"
><A
NAME="XFREE86">2. XFree86</H1
><P
> Virtually every Linux distribution comes with XFree86's
<SPAN
CLASS="APPLICATION"
>X Window System</SPAN
> implementation. This project, of
course, provides us the X server, but also includes an extensive suite of
utilities and applications to help implement a fully functional GUI
environment. </P
><P
> In fact, the list would be just too long to list everything that
comes with XFree86. In addition to the X server itself, here are a few of the
noteworthy utilities:</P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xdm</B
> - the X Display Manager.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xfs</B
> - the X Font Server.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>twm</B
> - a lightweight Window Manager.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xterm</B
> - the best known terminal emulator. Also,
<B
CLASS="COMMAND"
>xterm3d</B
> and <B
CLASS="COMMAND"
>nxterm</B
>.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xwd</B
> - a screen and window image capturer.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xf86config</B
> - X server configuration utility.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xdpyinfo</B
> - X display information utility. This
shows great detail about the X server.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xlsclients</B
> - lists currently connected X server
clients.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xlsfonts</B
> - lists fonts available to
<SPAN
CLASS="APPLICATION"
>X</SPAN
>.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>appres</B
> - lists the X <SPAN
CLASS="QUOTE"
>"resources"</SPAN
> that a
program will use.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xfontsel</B
> - an application for viewing or
selecting fonts.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xprop</B
> - a tool for displaying window
<SPAN
CLASS="QUOTE"
>"properties"</SPAN
>, such as the Class name of the client.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xset</B
> - sets user preferences for many things,
including mouse, keyboard, sound (bell), etc.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xsetroot</B
> - a program for changing the
<SPAN
CLASS="QUOTE"
>"root window"</SPAN
> appearance, e.g. setting a background color.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xvidtune</B
> - an application to adjust X server
video modes and monitor related settings.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xwininfo</B
> - displays information about a selected
<SPAN
CLASS="QUOTE"
>"window"</SPAN
>.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> <B
CLASS="COMMAND"
>xmodmap</B
> - a utility for manipulating keyboard and mouse
button mappings.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
></P
><TABLE
BORDER="0"
><TBODY
><TR
><TD
> Many, many fonts. And quite a bit of documentation as well.
</TD
></TR
></TBODY
></TABLE
><P
></P
><P
> There are many more. We'll just touch on a few of these utilities here. But
feel free to explore the others. Most should have their own man pages. </P
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN197">2.1. Hardware</H2
><P
> The X server controls both input (keyboard, mouse, etc) and output (display,
monitor) devices. </P
><P
> Compatible hardware is a tough topic, since it is very much a moving target.
We are forced here to avoid specifics, since this would surely change by the
time you read this. And would be tediously lengthy anyway. </P
><P
> So let's settle for some generalities. <EM
>Most</EM
> PC type
hardware is supported to one degree or another. Big help ;-) </P
><P
> Rule of thumb: if it is a device that uses a long-standing, commonplace
protocol (e.g. PS/2), it should be well supported. Conversely, if it is
something relatively new, with ground-breaking technology, the odds
are not as good. This is just the nature of the beast with open source
development versus manufacturers that cater more to the most popular
platforms. Some manufacturers are more co-operative than others too. </P
><P
> Now, some general guidelines: </P
><P
> <P
></P
><UL
><LI
><P
> Monitors - This is easy. Linux does not really need to be compatible with
the monitor per se. That is the job of the video card. Any monitor that
your graphics card can drive should do fine. Including, flat panel
monitors.
</P
></LI
><LI
><P
> Video cards - This is much tougher. The X server is determined by the
the chipset. Many, many are supported. But inevitably there are always
some newer cards, or even revised cards, that are not. And some may have
better support and better optimization than others. Advanced
features such as multi-headed displays, 3D, TV out, DRI, etc., have some
support as well, though this should be researched first, as the support
may be limited. Supported cards are listed: <A
HREF="http://xfree86.org/cardlist.html"
TARGET="_top"
>http://xfree86.org/cardlist.html</A
>.
</P
><P
> Open source drivers are often developed incrementally. For instance, a
particular card may work well for basic display purposes, but specialized
features such as 3D may come much later in the development cycle. This
is a quite different development model than with proprietary drivers from
the manufacturer.
</P
></LI
><LI
><P
> Keyboards -- Any standard PC type keyboard should do fine,
including PS/2, USB and many infra-red devices. Probably many
<SPAN
CLASS="QUOTE"
>"non-standard"</SPAN
> ones too ;-)
</P
></LI
><LI
><P
> Mice and other pointer devices -- Most should be supported including
PS/2, bus, serial, USB and many infra-red devices. Optical mice also. Unix
has long preferred three button mice, though more buttons is supported as
well. Many wheeled mice have X server support via the
<SPAN
CLASS="QUOTE"
>"IMPS/2"</SPAN
> (IntelliMouse), or other specific protocols, though
may require supplemental configuration for some individual applications.
(See the <A
HREF="appendix.html#LINKS"
>Links</A
> section.)
</P
></LI
><LI
><P
> Laptops have their own unique set of problems since the hardware tends to
be very specialized, and often different from what is commonly found on
desktop style systems. <SPAN
CLASS="APPLICATION"
>X</SPAN
> is supported by many.
Check for details at <A
HREF="http://www.linux-laptop.net/"
TARGET="_top"
>http://www.linux-laptop.net/</A
>.
</P
></LI
></UL
></P
><P
> You can check the <SPAN
CLASS="QUOTE"
>"hardware compatibility list"</SPAN
> at your
distribution's web site too. This should give a very good idea of what
<EM
>should work</EM
> with your release. </P
><P
> Newer versions of XFree86 obviously will have better hardware support. If you
are using an older Linux version and don't have full hardware support, see
about upgrading XFree86. Check first to see if your distribution has updates
for your release. </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN228">2.2. XF86Config</H2
><P
> The primary configuration file for XFree86 is
<TT
CLASS="FILENAME"
>XF86Config</TT
>, which may exist on your system as
<TT
CLASS="FILENAME"
>XF86Config-4</TT
> for XFree86 v4.x, or possibly other
variations (see man page). It is typically located as
<TT
CLASS="FILENAME"
>/etc/X11/XF86Config</TT
>, though again, there may be
variations in the path. If both a <TT
CLASS="FILENAME"
>XF86Config-4</TT
>
and <TT
CLASS="FILENAME"
>XF86Config</TT
> exist, XFree86 v4.x will use the former.
This is a required file. </P
><P
> <TT
CLASS="FILENAME"
>XF86Config</TT
> file defines hardware devices, and other
critical components of the X server environment. </P
><P
> While this is a plain text file, and is editable, it is most often created
during installation by whatever utility your vendor uses for this purpose.
XFree86 also includes the <B
CLASS="COMMAND"
>xf86config</B
> utility for this,
but many distributions have their own such utilities. These utilities can be
run after installation if need be, to alter the configuration, or if new
hardware is installed. Read your locally installed documentation first. If
you attempt to hand edit this file, be sure to make a backup copy first since
<SPAN
CLASS="APPLICATION"
>X</SPAN
> won't start if this file is not to its liking
;-) </P
><P
> This file contains various <SPAN
CLASS="QUOTE"
>"sections"</SPAN
>. Each section defines some
fundamental aspect of XFree86, such as <SPAN
CLASS="QUOTE"
>"InputDevice"</SPAN
> (mouse,
keyboard, joystick, etc), <SPAN
CLASS="QUOTE"
>"monitor"</SPAN
>, or <SPAN
CLASS="QUOTE"
>"screen"</SPAN
>. The
<TT
CLASS="FILENAME"
>XF86Config</TT
> man page describes the sections and
common values for each. Note that the values listed in the man page is not a
comprehensive listing. There are many device specific <SPAN
CLASS="QUOTE"
>"options"</SPAN
>.
Check <A
HREF="http://xfree86.org"
TARGET="_top"
>http://xfree86.org</A
> for notes
and tips on your hardware. </P
><P
> The author's current <TT
CLASS="FILENAME"
>XF86Config-4</TT
>, as generated by Red
Hat's installer for XFree86 4.1: </P
><P
> <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> Section "ServerLayout"
Identifier "XFree86 Configured"
Screen 0 "Screen0" 0 0
InputDevice "Mouse0" "CorePointer"
InputDevice "Keyboard0" "CoreKeyboard"
EndSection
Section "Files"
# The location of the RGB database.
RgbPath "/usr/X11R6/lib/X11/rgb"
# Multiple FontPath entries are allowed (they are concatenated together)
# By default, Red Hat 6.0 and later now use a font server independent of
# the X server to render fonts.
FontPath "unix/:7100"
EndSection
# Module loading section
Section "Module"
Load "dbe" # Double-buffering
Load "GLcore" # OpenGL support
Load "dri" # Direct rendering infrastructure
Load "glx" # OpenGL X protocol interface
Load "extmod" # Misc. required extensions
Load "v4l" # Video4Linux
# Load "fbdevhw"
Load "pex5"
Load "record"
Load "xie"
EndSection
Section "InputDevice"
Identifier "Keyboard0"
Driver "keyboard"
Option "XkbLayout" "us"
# Option "AutoRepeat" "500 5"
# when using XQUEUE, comment out the above line, and uncomment the
# following line
# Option "Protocol" "Xqueue"
# Specify which keyboard LEDs can be user-controlled (eg, with xset(1))
# Option "Xleds" "1 2 3"
# To disable the XKEYBOARD extension, uncomment XkbDisable.
# Option "XkbDisable"
# To customize the XKB settings to suit your keyboard, modify the
# lines below (which are the defaults). For example, for a non-U.S.
# keyboard, you will probably want to use:
# Option "XkbModel" "pc102"
# If you have a US Microsoft Natural keyboard, you can use:
# Option "XkbModel" "microsoft"
EndSection
Section "InputDevice"
Identifier "Mouse0"
Driver "mouse"
Option "Device" "/dev/mouse"
Option "Protocol" "IMPS/2"
Option "Emulate3Buttons" "off"
Option "ZAxisMapping" "4 5"
EndSection
Section "Monitor"
Identifier "Sylvania F74"
VendorName "Unknown"
ModelName "Unknown"
HorizSync 30 - 70
VertRefresh 55 - 120
Option "dpms"
# Modelines go here if necessary. Use xvidtune to get proper values.
EndSection
Section "Device"
Identifier "ATI Rage 128"
Driver "r128"
BoardName "Unknown"
EndSection
Section "Device"
Identifier "Linux Frame Buffer"
Driver "fbdev"
BoardName "Unknown"
EndSection
Section "Screen"
Identifier "Screen0"
Device "ATI Rage 128"
Monitor "Sylvania F74"
DefaultDepth 24
Subsection "Display"
Depth 24
Modes "1400x1050" "1280x1024" "1152x864" "1024x768" "800x600"
EndSubSection
Subsection "Display"
Depth 16
Modes "1600x1200" "1400x1050" "1280x1024" "1152x864" "1024x768" "800x600"
EndSubSection
Subsection "Display"
Depth 8
Modes "1024x768" "800x600" "640x480"
EndSubSection
EndSection
Section "DRI"
Mode 0666
EndSection
</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
> Yours may look quite different. This is just one possible configuration with
gratuitous comments from Red Hat (and me), and is for a fairly ordinary set
up. There is nothing exotic here like multiple screens or displays. </P
><P
> It is beyond the scope of this document to explain this in detail. See the
<TT
CLASS="FILENAME"
>XF86Config</TT
> man page. Also, consider visiting
<A
HREF="http://xfree86.org"
TARGET="_top"
>xfree86.org</A
>
and look for specific options that might apply to your card or other
hardware. </P
><P
> Just one quick note on the <SPAN
CLASS="QUOTE"
>"Screen"</SPAN
> section above. Notice there are
three sub-sections, identified as <SPAN
CLASS="QUOTE"
>"Display"</SPAN
>. Each sub-section
has a different <SPAN
CLASS="QUOTE"
>"Depth"</SPAN
> specified, (a.k.a. ColorDepth). The
<SPAN
CLASS="QUOTE"
>"Modes"</SPAN
> also vary somewhat according to the respective
<SPAN
CLASS="QUOTE"
>"Depth"</SPAN
> setting. The active <SPAN
CLASS="QUOTE"
>"Display"</SPAN
> sub-section
that will be used, is determined by the <SPAN
CLASS="QUOTE"
>"DefaultDepth"</SPAN
> setting
(unless over-ridden by command line options). The default in this example is
defined as <SPAN
CLASS="QUOTE"
>"24"</SPAN
>, so the first sub-section will be used. Also,
the highest <SPAN
CLASS="QUOTE"
>"Mode"</SPAN
> listed in this sub-section will be the default
mode (resolution), which here is the first one listed. The first listed mode
also determines the viewable screen area, which can be smaller than the mode
(resolution) itself. In which case, you would have a virtual desktop that is
larger than the viewable screen. To have the viewable screen, and resolution
match, have the largest value as the first value listed for each
<SPAN
CLASS="QUOTE"
>"Mode"</SPAN
>. </P
><P
> Another note on the <SPAN
CLASS="QUOTE"
>"Modes"</SPAN
> here: what you see is the result of
my choices during Red Hat's <B
CLASS="COMMAND"
>Xconfigurator's</B
> configuration. These
are standard resolutions, but do not have to be! This is only limited by what
your hardware can support. And you don't have to use standard width x height
ratios either. Something like <TT
CLASS="LITERAL"
>1355x1112</TT
> is a valid setting (if
your hardware supports it and it floats your boat!). </P
><P
> The X server will reject any <SPAN
CLASS="QUOTE"
>"Modes"</SPAN
> it thinks are invalid. You
can cycle through valid modes to change screen resolution with
<TT
CLASS="LITERAL"
>Ctrl-Alt-+</TT
> and <TT
CLASS="LITERAL"
>Ctrl-Alt--</TT
> (that's the
keypad plus and minus keys). </P
><P
> In versions prior to v4.x, you would also see many <SPAN
CLASS="QUOTE"
>"Modeline"</SPAN
>
statements that attempted to define the monitor's capabilities. These
statements would look something like: </P
><P
> <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> # 1024x768 @ 100Hz, 80.21 kHz hsync
Modeline "1024x768" 115.5 1024 1056 1248 1440 768 771 781 802 -HSync -VSync
</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
> Explicit <SPAN
CLASS="QUOTE"
>"Modeline"</SPAN
> definitions are not required as of 4.x ;-)
This sometimes required hand editing to get optimal values in earlier versions of
XFree86, though is generally not necessary with v4.x. <I
CLASS="CITETITLE"
>The XFree86 Video
Timings HOWTO</I
>, <A
HREF="http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html"
TARGET="_top"
>http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html</A
>
has a nice, but rather technical, explanation of this. </P
><P
> If whatever configuration utility you are using, does not automatically
recognize your video card or monitor specifications correctly, you are
unlikely to get an optimal configuration. In such cases, you may have to
manually supply the correct values. This should be available from your
owner's manual (you kept that, right?). Or, check the manufacturer's web site. </P
><P
> Again, hand editing of this file is generally unnecessary. Should you decide
this is indeed necessary, be careful. One small error may cause
<SPAN
CLASS="APPLICATION"
>X</SPAN
> to fail. Any changes to this file will require
restarting <SPAN
CLASS="APPLICATION"
>X</SPAN
> for the changes to take
effect. </P
><P
> Using somebody else's <TT
CLASS="FILENAME"
>XF86Config</TT
> file, is generally a
bad idea since they are unlikely to have identical hardware. </P
></DIV
><DIV
CLASS="SECT2"
><H2
CLASS="SECT2"
><A
NAME="AEN290">2.3. xvidtune and Monitor Tuning</H2
><P
> You probably want to get the most out of your hardware. If
<SPAN
CLASS="APPLICATION"
>X</SPAN
> isn't configured optimally, consider re-running
your vendor's <SPAN
CLASS="APPLICATION"
>X</SPAN
> configuration utility and try to
get better results. It is highly unlikely that you could hurt anything by
experimenting. Most modern monitors now have safeguards that prevent a
meltdown ;-)
</P
><P
> If you over-do it though <SPAN
CLASS="APPLICATION"
>X</SPAN
> may not be able to
start. For this reason, I prefer to use the <SPAN
CLASS="QUOTE"
>"startx"</SPAN
> way of
starting <SPAN
CLASS="APPLICATION"
>X</SPAN
> (see below) while
<SPAN
CLASS="QUOTE"
>"experimenting"</SPAN
>. This way if <SPAN
CLASS="APPLICATION"
>X</SPAN
>
crashes, the display manager (GUI login) will not loop and cause you severe
headaches. <B
CLASS="COMMAND"
>startx</B
> just gracefully goes back to a text
console screen, where an error message may be visible. </P
><P
> Another way of tweaking monitor related settings is with XFree86's
<B
CLASS="COMMAND"
>xvidtune</B
> program. This is run interactively and can be
used to adjust various settings (see man page). The simple dialog box has
sliders and buttons that allow user input and adjustment. The top part has
horizontal monitor settings on the left, and vertical settings on the right.
The buttons just below the sliders can be used to adjust each. </P
><P
> This is sometimes used to adjust the viewable screen area, such as to center
it, or increase its size to fill the monitor's viewport. When
<B
CLASS="COMMAND"
>xvidtune</B
> is launched, it defaults to the current settings. </P
><P
> The bottom left corner has buttons that can <SPAN
CLASS="QUOTE"
>"Apply"</SPAN
> new
settings, <SPAN
CLASS="QUOTE"
>"Test"</SPAN
> new settings, or <SPAN
CLASS="QUOTE"
>"Show"</SPAN
> current
settings (i.e. dump to screen), among other things. Any changes made here are
not saved. If new settings are <SPAN
CLASS="QUOTE"
>"Applied"</SPAN
>, it is just for
the current session. Example output of <B
CLASS="COMMAND"
>xvidtune</B
>
<SPAN
CLASS="QUOTE"
>"Show"</SPAN
>: </P
><P
> <TABLE
BORDER="1"
BGCOLOR="#E0E0E0"
WIDTH="100%"
><TR
><TD
><FONT
COLOR="#000000"
><PRE
CLASS="SCREEN"
> Vendor: Unknown, Model: Unknown
Num hsync: 1, Num vsync: 1
hsync range 0: 30.00 - 70.00
vsync range 0: 55.00 - 120.00
"1400x1050" 122.00 1400 1488 1640 1880 1050 1052 1064 1082 +hsync +vsync
</PRE
></FONT
></TD
></TR
></TABLE
></P
><P
> The last line is the <SPAN
CLASS="QUOTE"
>"Modeline"</SPAN
> being used to drive the current
screen. See <I
CLASS="CITETITLE"
>The XFree86 Video
Timings HOWTO</I
>, <A
HREF="http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html"
TARGET="_top"
>http://www.linuxdoc.org/HOWTO/XFree86-Video-Timings-HOWTO/index.html</A
>,
for more on <SPAN
CLASS="QUOTE"
>"Modelines"</SPAN
>.
</P
><P
> You can test modifications, and apply them to the current session.
For changes to be made permanent, they will have to be added manually to
the <SPAN
CLASS="QUOTE"
>"Monitor"</SPAN
> section of <TT
CLASS="FILENAME"
>XF86Config</TT
> (or
<TT
CLASS="FILENAME"
>XF86Config-4</TT
> for v.4.x) with a text editor. </P
><P
> <B
CLASS="COMMAND"
>xvidtune</B
> will dutifully warn of you of the hazards of
playing with the monitor settings. It is unlikely you can hurt anything
with modern monitors. But it is best used to make minor adjustments. Use at
your own risk! </P
></DIV
></DIV
><DIV
CLASS="NAVFOOTER"
><HR
ALIGN="LEFT"
WIDTH="100%"><TABLE
SUMMARY="Footer navigation table"
WIDTH="100%"
BORDER="0"
CELLPADDING="0"
CELLSPACING="0"
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
><A
HREF="intro.html"
ACCESSKEY="P"
>Prev</A
></TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
><A
HREF="index.html"
ACCESSKEY="H"
>Home</A
></TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
><A
HREF="runningx.html"
ACCESSKEY="N"
>Next</A
></TD
></TR
><TR
><TD
WIDTH="33%"
ALIGN="left"
VALIGN="top"
>Introduction</TD
><TD
WIDTH="34%"
ALIGN="center"
VALIGN="top"
> </TD
><TD
WIDTH="33%"
ALIGN="right"
VALIGN="top"
>Running X</TD
></TR
></TABLE
></DIV
></BODY
></HTML
>
