<qandadiv id="configuration">
<title>Configuration</title>

<qandaentry>
<question id="q-why-no-xf86config">
<para>Is there an xorg.conf or XF86Config file?</para>
</question>

<answer>
<para>No.  Options which are configurable are available as command line options.
For example, for more information on configuring other
keyboard layouts using command line options, see <xref
linkend="q-non-U.S.-keyboard-layout"></xref></para> </answer>
</qandaentry>


<qandaentry>
<question id="q-command-line-args">
<para>What are the command line options for &XWin;? How do I add command line options for &XWin;?</para>
</question>

<answer>
<para>The <ulink url="&project-url-ug;">&project; User's Guide</ulink>
and <ulink url="http://x.cygwin.com/docs/man1/XWin.1.html"><command>man XWin</command></ulink>
document the command line options for &file-server-exe;.</para>

<para>
To supply a command line option to &XWin;:

<itemizedlist spacing="compact">
<listitem>
<para>
If you use the start menu shortcut to start the X server, you will need to amend it's target to add an option, e.g. <command>C:\cygwin\bin\run.exe --quote /usr/bin/bash.exe -l -c "/usr/bin/startxwin -- -nolock"</command>
</para>
<note><para>Note well that the entire command after <parameter>-c</parameter> is quoted</para></note>
<note><para>Note that this start menu shortcut is created by the <filename>xinit</filename> package, and your changes will be overwritten when the <filename>xinit</filename> package is updated.</para></note>
<note><para>Note that X server options to <command>startxwin</command> are preceded by <parameter>--</parameter>.</para></note>
</listitem>

<listitem>
<para>
If you use <command>startxwin</command>, <command>xinit</command> or <command>startx</command> to start the server, run it as e.g. <command>startxwin -- -nolock</command>,  <command>xinit -- -nolock</command> or <command>startx -- -nolock</command>
</para>
</listitem>

<listitem>
<para>
If you use <filename>startxwin.bat</filename> or <filename>startxwin.sh</filename> to start the server, add e.g. <parameter>-nolock</parameter> to the <command>XWin</command> line in that script.
</para>
</listitem>
</itemizedlist>
</para>

</answer>
</qandaentry>


<qandaentry>
<question id="q-display-depth-ignored"> 
<para>Why does &XWin; ignore the display depth that I pass
on the command line?</para>
</question>

<answer>
<para>When running in windowed mode or GDI-based fullscreen mode,
&XWin; must run the X Server at whatever display depth
Windows is currently using; in these cases the display depth passed on
the command line is ignored.  &XWin; only uses the display
depth parameter when running in a DirectDraw-based fullscreen mode, as
DirectDraw allows applications to change the display resolution and
depth when running in fullscreen mode.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="q-three-button-emulation">
<para>I have a two button mouse, can I emulate a three button mouse?</para>
</question>

<answer>
<para>Yes.  Pass the <parameter>-emulate3buttons <replaceable
class="option">timeout_in_milliseconds</replaceable></parameter>
parameter to &XWin;, where <replaceable
class="option">timeout_in_milliseconds</replaceable> is the, optional,
maximum number of milliseconds between a button release and opposite
button press that will trigger an emulated third button press.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="window-auto-focus">
<para>Is there a Focus-Follows-Mouse feature (Auto-Focus)?</para>
</question>
<answer>
<para>This is a setting of the window manager used. The default window manager
<command>twm</command> has no such feature. But with <command>fvwm2</command>
this can be achieved with the this configuration entry:
<screen>Focus FocusFollowsMouse
</screen>
Other window managers (eg. <command>windowmaker</command>) have similar features too.</para>
<para>If you are using the &multiwindow; mode you can not set this behaviour
in the window manager but you can use the TweakUI tool to enable this feature
for all windows, not limited to &project; windows.</para>
</answer>
</qandaentry>


<qandaentry>
<question id="disable-terminate-server">
<para>The option -nounixkill has no effect. How can i prevent the server 
shutdown an Ctrl-Alt-BackSpace?</para>
</question>
<answer>
<para>
This question should be obsolete as the TerminateServer keybinding is
no longer present by default.
</para>
<para>
The TerminateServer keybinding can be enabled with
<screen>setxkbmap -option terminate:ctrl_alt_bksp</screen> 
</para>
</answer>
</qandaentry>

<qandaentry>
<question id="q-multihead">
<para>I have a multihead system. Do I need special options to make it work?
I have a multihead system.  Why are my X-application windows white?</para>
</question>
<answer>
<para>You should start &XWin; with the &multiplemonitors; option.</para>
<para>Note that this option is enabled by default in &multiwindow; mode.</para>
</answer>
</qandaentry>

<qandaentry>
<question id="q-firewall">
<para>I have a firewall. Is there anything I have to take care of?
</para>
</question>
<answer>
<para>&XWin; uses port 6000/TCP when the option <parameter>-listen
tcp</parameter> is used. You will have to allow incoming and outgoing traffic on
this port even if you are only using local clients. &XWin; has a builtin access
control so you won't have to worry about opening the port. If you are still
concerned about security, you may limit the allowed hosts to the local IP
addresses.</para>
<para>
If you use a different display number check section
<xref linkend="display-and-screen"/> for details about which ports are
used. For additional information about firewalls and XDMCP connections check
<xref linkend="q-xdmcp-query"/>.
</para>
</answer>
</qandaentry>

</qandadiv>
