<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<TITLE>Configuring X for Your Hardware</TITLE>
</HEAD>
<BODY BGCOLOR="#efefef" TEXT="black" LINK="blue" VLINK="#551A8B" ALINK="red">

<A HREF="OS2.html"><EM>README for XFree86 on OS/2</EM></A>
 <b>:</b> <EM>Configuring X for Your Hardware</EM><BR>
<b>Previous:</b> <A HREF="OS210.html"><EM>Remarks on the Network Configuration</EM></A><BR>
<b>Next:</b> <A HREF="OS212.html"><EM>Running X</EM></A>


<HR NOSHADE>
  <H2><A NAME="13"></A>11. Configuring X for Your Hardware</H2>
<p>After you have added the required settings and setup a working network,
run the <code>xf86config</code> program to create a standard configuration file
in <code>Y:\XFree86\lib\X11\XF86Config</code> from a windowed
or full screen OS/2 text session:
<blockquote><code>
<pre>
[C:\] xf86config
</pre>
</code></blockquote>
</p>
<p>The <code>xf86config</code> program will ask a number of questions. You will need 
the information obtained from the SuperProbe program here. The program should 
be self explanatory; if you have problems to understand something though, seek
assistance in the newsgroups.</p>
<p>It is possible, but strongly discouraged for the non-expert, to edit the
<code>XF86Config</code> file with a text editor. In a few situations as described in
the FAQ, however, this might even be mandatory. This file is not a hacker's area,
such as the Win95 registry, but it has in common with it that you can
easily cause damage.</p>
<p>For details about the <code>XF86Config</code> file format, refer to the
<em>XF86Config(4/5)</em> manual page.</p>
<p>If you know the configuration process from Linux or other XFree86 platform, 
you will encounter a few differences:
<ul>
<li>There is no configuration for the mouse type or device. The mouse
device name is fixed to OSMOUSE, and this cannot be changed.
If you have a three-button-mouse, install the correct OS/2 driver 
for it, such as
<blockquote><code>
<pre>
DEVICE=D:\OS2\BOOT\PCLOGIC.SYS SERIAL=COM1
DEVICE=D:\OS2\BOOT\MOUSE.SYS TYPE=PCLOGIC$
</pre>
</code></blockquote>

for a MouseSystems compatible mouse, for instance.</li>
<li>The X server does not read the native OS/2 keyboard map, but the new XKB
server extension might already give you a correct keyboard layout,
provided your language was selectable in the <code>xf86config</code> program. If you
encounter incorrect settings, please send a mail to <code>XFree86@XFree86.org</code>
describing in detail what is wrong. Even with XKB, you have the option
to replace some key settings with a xmodmap file. See the man page
for xmodmap for details (or use some available xmodmap file from Linux -
they are the same).</li>
<li>There is no support for the Wacom and Elographics input devices yet.</li>
</ul>
</p>
<p>In most cases, an existing <code>XF86Config</code> file for the same XFree86 version
from Linux or another platform may be used without changes. There is one 
prominent exception: some S3 805 based VLB cards put their video memory
in odd locations. The X server can search for this memory by experimentally
mapping and unmapping possible memory regions. In XFree86/OS2, the OS may
run out of memory tiles during this process. If this happens, you must
find out the location of the memory yourself and add it as an option
<blockquote><code>
<pre>
	MemBase 0x12345678
</pre>
</code></blockquote>

to the XF86Config file.</p>
<p>Once you've set up a XF86Config file, you can fine tune the video
modes with the <code>xvidtune</code> utility. </p>

 <HR NOSHADE>
<A HREF="OS2.html"><EM>README for XFree86 on OS/2</EM></A>
 <b>:</b> <EM>Configuring X for Your Hardware</EM><BR>
<b>Previous:</b> <A HREF="OS210.html"><EM>Remarks on the Network Configuration</EM></A><BR>
<b>Next:</b> <A HREF="OS212.html"><EM>Running X</EM></A>



</BODY>
</HTML>
