Using XSettings

You can start XSettings by double-clicking on the XSettings icon in the WinaXe Programs' folder:

The XSettings dialog box will appear on your display:

By clicking OK, any new settings you make to the XSettings dialog box will be saved in the "[XSETUP]" section of the xwp.ini file (by default) and the dialog will be closed. (See also section Running XSettings with Command Line Parameters below.)

You can cancel any changes you have made to the dialog box and close it by pressing Cancel.

On how to port XServer's settings (i.e., the "[XSETUP]" section of the ini-file) onto other PCs, see subsection Exporting XServer's Settings During Installation in section Running Setup in chapter Installing WinaXe.

The following items are available:

Silent Bell

When enabled, this check box will block all sounds (internal sounds and the X-protocol XBell requests).

Auto Clipboard Copy&Paste

This check box controls the mode of connection between the MS Windows Clipboard and the current X Selection. When enabled, then changing of the MS Windows Clipboard contents will force the same change in the current X Selection. Also, changing of the contents of the current X Selection (from the active application window) will automatically cause copying it into the MS Windows Clipboard (so you are ready to paste).

The Mouse Settings Box

Middle Button Emulation

The default setting specifies a two-button mouse with Middle Button Emulation enabled. If you are using a 3-button mouse, click to disable the Middle Button Emulation check box. The middle mouse button is emulated by clicking simultaneously both left and right mouse buttons.

Use Mouse Wheel

This check box enables/disables XServer to process the mouse wheel (i.e. to translate its rotation to the Button4 and Button5 press/release X-events).

Note that the mouse wheel does not take effect in the non-maximized Single Window mode (because of Scrollbars).

The GLX Extension Box

GLX Extension

This check box enables XServer to work with X-Clients that use OpenGL.

XServer can work with a number of X-Clients simultaneously (in a multi-thread mode of GLX), and X-Clients may create several GLX windows.

Use Single Buffer

This button allows XServer and X-Clients to use one buffer for GLX operations (the GLX Single-Buffer mode).

Use Double Buffer

This button allows XServer and X-Clients to use two buffers for GLX operations (the GLX Double-Buffer mode). This is the default mode.

Use Mesa Emulation

This check box allows XServer and X-Clients to use Mesa.

Mesa is an open-source implementation of the OpenGL specification. OpenGL is a programming library for writing interactive 3D applications. Mesa 5.x supports the OpenGL 1.4 specification. Mesa is used as the core of the open-source XFree86/DRI hardware drivers. Mesa allows OpenGL to be used on systems that have no other OpenGL solution. See www.mesa3d.org for more information.

The Keyboard Settings Box

Keyboard File List

XSettings allows you to configure WinaXe for supporting different international PC keyboards. The package supplies a set of keyboard mapping files that define assignments of key functions to physical keys on appropriate keyboards. The files are listed in Appendix A.

You can enter any kmf-file name in the edit field or select an appropriate keyboard file from the Keyboard File List by clicking on its file name. The default keyboard is us.kmf.

For more information, see section Keyboard Definition Files in Chapter The WinaXe Database.

Local NumLock Key

If this check box is enabled, XServer (not X clients) will process the NumLock key.

Unlatched NumLock

If this check box is enabled, XServer will consider the NumLock key as a normal key (non-toggling). The NumLock key is unlatched by default. This was implemented to suppress the NumLock state's influence on some X-Window managers and programs.

Local ScrollLock Key

This is important only for the XServer's Full Screen mode. The key is used for iconifying the XServer's window. If this check box is enabled, XServer (not X clients) will process the ScrollLock key.

Unlatched ScrollLock

If this check box is enabled, XServer will consider the ScrollLock key as a normal key (non-toggling). The ScrollLock key is unlatched by default.

Block KeySyms Changing

If enabled, this check box prevents the XServer keyboard's KeySyms mapping from external changes (e.g., by the "xmodmap" utility). The default is On.

Block Modifiers Changing

If enabled, this check box prevents the XServer keyboard's Modifiers mapping from external changes (e.g., by the "xmodmap" utility). The default is On.

Keyboard Mapping for Linux

If this check box is enabled, XServer will provide a "close-to-Linux" keyboard mapping (i.e., the Linux console keyboard mapping). This setting would be useful when using some applications of the KDE 3.x package (e.g., the "kwrite" editor) that do not correctly recognize some keys (e.g., "Shift+arrows" key combinations).

Default

This button sets up the default values for check boxes and edit fields in the Keyboard Settings box.

The Screen Settings Box

Enable Animation

If checked, this check box causes XServer to more precisely display color images.

Local Screen Saver

If enabled, this check box causes a Local Screen Saver program to be run (for the XServer's Full Screen and Single modes only).

Forced Backing Store

If this check box is checked, the Backing Store mode will be used with all X clients. This allows X Window System displays to be saved off-screen so that X clients do not have to refresh a window display after it has been obscured by another window. Saving a copy of the information obscured when windows overlap each other reduces network traffic. Certain X-applications will request the Backing Store mode on windows that are complicated to draw. The option will cause XServer to use Backing Store on all windows, even if the X-application does not request it.

If this check box is not checked, the Backing Store mode will be turned off so copies of windows information will not be saved and X clients will have to refresh their obscured windows.

Color Mouse Cursor

If this check box is checked, then XServer is allowed to use the color mouse cursor when X clients use it.

Default

This button sets up the default values for check boxes and edit fields in the Screen Settings box.

The Display Number Box

Display Number

You can specify a display number for a particular X-session. This allows you to run simultaneously several X-sessions, each with different Display Number (e.g., several Window Managers). Section Running Several X-sessions in chapter Using XServer describes examples of using the Display Number setting.

(According to X11 documentation, from the user's prospective, every X server has a display name of the form: hostname:displaynumber.screennumber .This information is used by the application to determine how it should connect to the server and which screen it should use by default (on displays with multiple monitors).

The hostname specifies the name of the machine to which the display is physically connected. For the TCP/IP type of connections, the hostname part of the display name should be the server machine's IP address name. Full Internet names, abbreviated names, and IP addresses are all allowed.

The phrase DisplayNumber is usually used to refer to collection of monitors that share a common keyboard and pointer (mouse, tablet, etc.). Most workstations tend to only have one keyboard, and therefore, only one display. Larger, multi-user systems, however, frequently have several displays so that more than one person can be doing graphics work at once. To avoid confusion, each display on a machine is assigned a display number (beginning at 0) when the X server for that display is started. The display number must always be given in a display name.

Some displays share a single keyboard and pointer among two or more monitors. Since each monitor has its own set of windows, each screen is assigned a screen number (beginning at 0) when the X server for that display is started. If the screen number is not given, screen 0 will be used.)

Each Display Number corresponds to the known Port Number of XServer (0-6000, 1-6001, etc.).

Note that output log files for different Display Numbers have different names.

Auto

If this check box is checked, then it activates XServer to dynamically generate Display Number.

In this mode, any new X-session will have new Display Number and a lot of XServer instances (X-sessions) can be started with no changes in the ini-file. This feature is especially useful with NT/2000 Terminal Servers.

Note: No XServer instances must use equal Display Numbers when running simultaneously on your PC (even for different users).

The Virtual Root Size Box

When you select either Single or Full Screen modes for XServer, you can fill in the Width and Height fields in the Virtual Root box. This box lets you set the default size in pixels for the XServer's root window. You can make the virtual screen size larger than your display if you want to (e.g., for multi-monitor systems).

The maximum virtual root size is limited by the expression of "width*height sq. pixels <= 56Mbyte" pixels.

Fit to Screen Size

If enabled, this check box allows to skip input for the virtual Width and Height (XServer will use the values returned by the MS Windows display driver for a single display).

The X depth (bits per pixel) Box

The radio buttons let you choose the color depth and visual mode that XServer will use:
- 8-bit or 256-color visual mode (up to 256 colors);
- 16-bit or HiColor visual mode (up to 65536 or 32768 colors);
- 24-bit or TrueColor visual mode (up to 16777216 colors).

The Auto choice causes XServer to use current video settings of MS Windows (except for 32-bit; in this case, XServer can use up to the 24-bit mode).

Note: If MS Windows is set up to the 8-bit visual mode (256 colors), then XServer will use the same mode.

The Image Format Box

LSB

This sets up the Image Format to the LSB (LeastSignificant Byte/Bit first) mode (when every X client must work with XServer using imageByte- and bitmapBit- orders in the LSB format, e.g., X clients on Intel-platform machines).

This is the default setting (since XServer works with X clients without Image Format conversion).

MSB

This sets up the Image Format to the MSB (MostSignificant Byte/Bit first) mode (when every X client must work with XServer using imageByte- and bitmapBit- orders in the MSB format, e.g., X clients on SUN workstations).

Auto

This specifies that X clients will define the Image Format for XServer.

The FullScreen Mode Box

The following check box is available when you choose either Full Screen or Single mode for XServer.

Minimize on Activity Losing

If this check box is enabled, the XServer's window will be iconified each time the focus changes to another window. Otherwise, it can be obscured by other windows.

The Startup Box

The Window Mode List

This item allows you to make a choice of the XServer startup mode. Select a desired window mode by clicking on a mode name. (For more information, see related sections in Chapter Using XServer.)

• Multiple
  

  In this mode, MS Windows works as a local window manager for your X clients. When an X client starts, it appears in a window like any other displayed by MS Windows. Each client you start creates its own window on your display. The client window's controls (i.e. its borders, the Control Menu box, move window functions, etc.) are all handled by MS Windows on your PC.

• Single
  

  This mode presents all X clients in a single X-session window. Within the window, the window management and all other functions are typically controlled by an X Window System manager you start on a host. The X-session window itself can be sized and moved like any other MS Windows window.

• Full Screen
  

  This mode presents all X clients in a single root window taking up full the screen outside the MS Windows graphical environment. The window management and all other functions are typically controlled by an X Window System window manager you start on a host.

• Multiple+RemoteWM
  

  This mode is the above Multiple mode, but the local MS Windows window manager does not control windows of X clients and a user has to run any suitable remote window manager. The mode is very convenient when users use CDE-like interface where a remote window manager provides its own tool/task bar.

The XDMCP Box

Use XDMCP

X Display Manager Control Protocol (XDMCP) is the popular method of starting remote login session. Once the WinaXe's XServer program, configured to use XDMCP, has initiated X-session for the first time, it contacts an 'xdm' process running on a host system. The Use XDMCP check box toggles this method. The default setting is disabled.

Settings

This button allows you to set up parameters and modes of the XDMCP startup method. The button is available only if you check the Use XDMCP check box. See section XDMCP Settings below for description of XDMCP customisation.

The Access Control Box

This box contains the following items that allow you to restrict access to your XServer from remote hosts. You can give access only to the hosts you authorized in the Authorize File and/or you specified in the Valid Hosts File.

Default

This button sets up the default values for check boxes and edit fields in the Access Control box.

Host Access Check

If this check box is checked, then XServer will check host access by using a file you specify in the Valid Hosts File field.

If this check box is disabled, then XServer will not check host access, so every host on your network will have access to your XServer (and the Authorization Check state does not matter).

Valid Hosts File

Use this field to specify a file you created to give access to hosts (and X clients) you wish to connect to your XServer.

This file will be used only if the Host Access Check check box is checked.

The file consists of text lines each of the following format:

IP_address comment
or
name comment

IP addresses are specified in the dotted IP address notation. Names must be specified as official host names or aliases in your hosts file.

Note that the host definition syntax allows you to use your hosts file as the Valid Hosts File.

Authorization Check

If this check box is checked, then XServer will make standard authorization check by using a file you specify in the Authorize File field.

If this check box is disabled, then XServer will not make standard authorization check.

Authorize File

Use this field to specify a file you created to give access to hosts you wish to connect to your XServer (for either XDM and non-XDM clients).

This file will be used only if the Authorization Check check box is checked.

Note: to use the Authorize File, you should copy the standard authorization binary file, ~HOME/.Xauthority, created with the 'xauth' utility on your host.

Auto-reject non-authorized X-Clients

If this check box is checked, then XServer will suppress the Authorization Audit message. This setting is useful if you want to reject any unauthorized X clients automatically (with no confirmation dialog).

Some Hints about Authorization and Host Access Policy

XServer checks permissions of hosts (and X clients) to establish connection by the following rules:

1. XServer will (firstly) make standard authorization check (if the Authorization Check check box is checked) and will (secondly) check host access (if the Host Access Check check box is checked).
   
   So if the Host Access Check check box is disabled, then every host on your network will have access to your XServer.
   
   
2. If the Authorization Check check box is enabled, and a host is found in the Authorize File, then XServer will give access to the host.
   
   
3. If the Host Access Check check box is enabled, and a host is found in the ValidAccessFile, then XServer will give access to the host.
   
   
4. If the Host Access Check check box is enabled, but the ValidAccessFile field is empty or the file you specified in the field cannot be normally read or the file is empty, and the Authorization Check check box is disabled, then access to your XServer is disabled for all hosts.
   
   
5. To authorize hosts that are absent in the ValidHostsFile, you can enable the Authorization Check check box and specify the Authorize File.

The Font Control Box

Font Path

This button allows you to manage font sources that can be used in X-sessions.

Pseudo Fonts

This button allows you to define how XServer will use MS Windows fonts in X-sessions.

Both options are described in detail in chapter Font Control.

Enable Scaled Fonts

If this check box is checked, then it allows XServer to use scaled fonts.

Trace Fonts Requests

If this check box is checked, then all font requests from X clients (with resolve messages) will be stored in the xserver.out file. This option is useful for analysis of the font accessibility and resolving font problems by XServer.