|Products||DownloadPrice & OrderSupportCompanyTutorialsSitemap|
back | index | next
You can start XSettings by double-clicking on the XSettings icon in the WinaXe Plus Programs' folder:
The XSettings dialog box will appear on your display. It consists of 7 tabs described below.
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.)
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 Plus.
You can cancel any changes you have made to the dialog box and close it by pressing Cancel.
The Startup Tab
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.)
The Use XDMCP Box
X Display Manager Control Protocol (XDMCP) is a popular method of starting remote login sessions. Once XServer configured to use XDMCP has initiated X-session for the first time, it contacts an 'xdm' process running on a host system.
XDMCP settings are used to control the XDMCP startup method. The Use XDMCP check box lets you specify the XDMCP settings.
Change XDMCP settings only after consulting with your system administrator.
The XDMCP Mode Box
You can check one of the following XDMCP modes:
This field is used to specify a network node name or IP address for the host you want to connect to in the Query or Indirect startup mode.
When you click on the scroll arrow beside the Connect Host box, a drop-down box will display host definitions listed in your hosts file. To select a host, just click on an appropriate definition.
If the hosts file does not contain the host definition you need, you can enter the host's IP address in the field (in the standard dotted IP address notation).
Broadcast List File
In the Broadcast startup mode, specify a file that contains a list of hosts that your PC will transmit a 'broadcast' message to.
The file consists of text lines each of the following format:
Names must be specified as official host names or aliases in your hostsfile. Note that the syntax allows you to use the hosts file as the Broadcast List File.
Note: if you leave this field empty or enter either 0.0.0.0 or 255.255.255.255 (these special destination addresses specify a broadcast), then this will provide the XDMCP broadcast mode (when your PC will transmit a 'broadcast' message to every host on your local network to query all XDMCP daemons).
Reset XServer at XDMCP Close
If checked, this check box enables closing all X clients if the remote XDM daemon terminates the XDMCP session with XServer.
XDM/CDE Special Processing
Check this check box if you are going to use the CDE XDMCP mode, i.e. with CDE installed on the remote XDMCP host (for the XServer's Multiple window mode only).
This check box allows you to enable the XDM-AUTHENTICATION-1 and XDM-AUTHORIZATION-1 schemes. If your host is using XDM authentication or XDM authorization scheme, set up the values in the Display ID, Display Class, and Key fields and report them to your system administrator.
If you disable XDM authentication/authorization, then XServer will use the default client authorization scheme, MIT-MAGIC-COOKIE-1.
According to the XSECURITY manual page of X Window System, X provides mechanism for implementing many access control systems. The sample implementation includes some mechanisms with MIT-MAGIC-COOKIE-1 (using shared plain-text "cookies") and XDM-AUTHORIZATION-1 (using secure DES-based private-keys) being two of them.
This button sets up the default values for check boxes and edit fields in the Use XDMCP box.
The XDM Authentication/Authorization Parameters Box
If XDM authentication or XDM authorization has been enabled on the XDM host, your system administrator will need to know the value displayed in this field. This field should normally never be changed. The Display ID value consists of these two parts separated by hyphen: the Display Class value and the arbitrary numerical value.
In very rare cases, your system administrator may determine that your Display ID
is a duplicate and will ask you to generate a new one. To do this, use arrows on the right
side of the Display ID field. The up arrow increases the numerical value of the
Display ID, and the down arrow decreases it.
This field can be used to group classes of XDM nodes. The field should only be modified at the request of your system administrator. Otherwise it should be left unchanged.
This field defines the key used in XDM authentication. If your host is using XDM authentication, your system manager will need to know the contents of your XDMCP Key and Display ID fields. This field should only be modified at the request of your system administrator. Otherwise it should be left unchanged.
The Mouse_Keyboard Tab
The Mouse Settings Box
Middle Button Emulation
The default setting specifies a two-button mouse with the check box enabled. If you are using a 3-button mouse, click to disable the 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 Keyboard Settings Box
Keyboard File List
You can configure XServer to support 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 file is us.kmf.
For more information, see section Keyboard Definition Files in chapter The WinaXe Plus Database.
Local NumLock Key
If this check box is enabled, XServer (not X clients) will process the NumLock key.
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.
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).
This button sets up the default values for check boxes and edit fields in the tab.
The Screen Tab
The Screen Settings Box
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
This option can be used if the Backing Store mode is enabled. (See the Advanced Tab.)
If this check box is checked, the Backing Store mode will be used with all X clients. The option will cause XServer to use Backing Store on all windows, even if the X-application does not request it.
Certain X-applications will request the Backing Store mode on windows that are complicated to draw. If this check box is clear, XServer will only use Backing Store on those windows that the X-application does request it.
Enable RENDER Extension
This option enables XServer to use the RENDER extension (not available in the 8-bits X depth mode). This also provides a wider range of available pixmap depths.
Color Mouse Cursor
If this check box is checked, then XServer is allowed to use the color mouse cursor when X clients use it.
The Display Number Box
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, xserver[N].out, with N being Display Number.
This check box enabled 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 system (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. This 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 selected, this check box allows you to skip input for virtual Width and Height. XServer will use the values returned by the MS Windows display driver for a single display.
If this check box is clear, you can specify the Width and Height fields as the default size in pixels that XServer will use for its root window.
If the Width and/or Height fields are zero or negative values, then the actual screen size will be the sum of the value and the corresponding dimension of the PC's screen. For Multiple and Multiple+RWM modes, the "0" and "-1" values are only allowed.
The X depth (bits per pixel) Box
These radio buttons let you choose the color depth and visual mode that XServer will use:
The Auto choice causes XServer to use current video settings of MS Windows (except for 32-bit, in which 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 FullScreen Mode Box
The Image Format Box
This button sets up the default values for check boxes and edit fields in the tab.
The GLX Extension Box
The GLX Extension 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.
Use the Mesa Emulation mode together with the Enable RENDER Extension check box selected.
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 Font Control Tab
This tab allows you to manage font sources that can be used in X-sessions and to specify how XServer will use fonts in X-sessions.
The Font Manager item in the XServer's Run menu allows you to see: actual Font Path; the font list of each font directory; font information, properties, metrics, and images of any available font. (See section Font Service 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.
This button sets up the default values for check boxes and edit fields in the tab.
The Font Search Path Box
A font directory contains a number of font description files in the X11 format. Setup installs a set of font directories under the FONTS subdirectory in the WinaXe Plus home directory (by default).
Any font directory must have the fonts.dir file (that contains the font description list according to font files of the directory), the fonts.ali file (with font aliases), and a set of font description files (with the .pcf, .snf, or .pgz file name extension).
XServer must have access at least to the fixed and cursor fonts. The \FONTS\MINIMAL and \FONTS\MISC font subdirectories contain them. So Font Path must contain these font directories at least.
See section Font Directory in chapter Font Control for more details.
You can specify that you want to use a font server running on one or more hosts. Font servers are defined in the X11 R6 release of the X Window System. Instead of forcing XServer to read all fonts from your PC, the X FontServer Protocol makes it possible to manage fonts separately from XServer, directing XServer to request fonts from a font server via the X Consortium standard network protocol. In addition, for fonts that take a long time to open, this allows XServer to continue with other clients while the font server services the font requests.
For example, the following path specifies the font server host called hp9000 on port 7000:
See section Font Server in chapter Font Control for more details.
The Priority ordered path Box
Font Path is an ordered table of font sources (the priority list). A font source is one of the following: a font directory, a reference to a remote font server, and a pseudo font directory. XServer uses Font Path on X client's requests for any font. XServer searches for the required font according to the order of font sources till the first matching occurs.
If you highlight a font path in The Priority ordered path and press OK, then the selected path will appear in the Font directory edit field. You can enter a font directory path in the Font directory edit field or use the Browse button to select it.
Also, see Appendix C Troubleshooting for examples.
To insert the Font directory edit field into Font Path, select a path in the Priority ordered path list box and then click the Insert before button.
To insert the Font directory edit field into Font Path, select a path in the Priority ordered path list box and then click the Insert after button.
To remove a highlighted font source from Font Path, press the Delete button.
To move a highlighted font source from Font Path to the Font directory edit field, press the Cut button.
If you plan to use MS Windows fonts in an X-session, press the Pseudo fonts button to choose MS Windows fonts and assign aliases to them. This means creating pseudo fonts.
You can compile a pseudo font into the X11 format and save it in any font directory for later use.
You can also create a pseudo font directly in the X-session on particular X client's font requests. To enable this, switch on the Use pseudo fonts and Create pseudo on X client request check boxes in the Pseudo fonts dialog box. Pseudo fonts created in the X-session will only become accessible after restarting XServer.
If you need some X font that is inaccessible, XServer allows you to use any MS Windows font instead of it. MS Windows fonts do not support X11 font naming conventions. Therefore, pseudo names (aliases) are used to access them. To use a MS Windows font, you should create a pseudo font for it, i.e. choose one and assign a desirable alias. Pseudo fonts can be created in advance or immediately in the X-session.
MS Windows font specifications and aliases for Pseudo Fonts are stored in the Pseudo Fonts Directory. The Pseudo Fonts Directory, WINFONTS subdirectory, is located under the WinaXe Plus home directory (by default).
You can manage pseudo fonts by using the Pseudo fonts dialog box.
Creating Pseudo Font
To create a pseudo font, press the Create pseudo button in the Pseudo fonts dialog box. The Font dialog box will appear on your display. Select a suitable font and press OK. In the Specify alias for selected font box, enter a pseudo font alias and click OK.
The created pseudo font will appear in the Select pseudo font list box lexicographically ordered.
The alias must only contain alphanumeric characters (including the 'underscore' sign). The alias must be unique among existing pseudo fonts.
The Save button writes all changes to Pseudo Fonts Directory. This cannot be undone if you press Cancel in the Pseudo fonts dialog box or in the The Font Control Tab afterwards.
Viewing Pseudo Font
To view a pseudo font, select it in the Select pseudo font list box and click the View button. The Font sample window will appear with the font sample in it.
Note that the font image is displayed by the MS Windows (not by XServer). This option is for font identification only.
Deleting Pseudo Font
To delete a pseudo font, highlight it in the Select pseudo font list box and click the Delete pseudo button. You can delete more than one font at a time. You should confirm removing each font and the total number of the selected fonts.
Compiling Pseudo Font to the X11 format
Loading pseudo fonts takes some time to create their images. Reading font image from the X11 format file is faster. It becomes essential if X client uses a lot of fonts. To prevent this time loss, you can save images of frequently used pseudo fonts in the X11-like format in your Pseudo Fonts Directory. This will require some disk space.
To save the image, highlight the required font in the Select pseudo font list box and click the Compile into X11 button. In the Place X11 font to box, specify a font directory to store the X11 font file.
You can enter the font directory path in the Font directory edit field or use the Browse button to select it. If the specified directory is not the font directory (e.g., it is empty), then the fonts.dir file will be created in it.
You should confirm compiling each font. To use the font directory, include it into Font Path.
Creating Pseudo Fonts on X Client Request
Pseudo fonts can be created immediately in the X-session on particular requests of X clients. If the requested font is not found, you will be prompted to create a new pseudo font. Creating pseudo fonts in the X-session is especially useful when you run X applications for the first time.
Creating pseudo fonts in an X-session is the same as in the Pseudo fonts dialog box. You can use the requested font name as the pseudo font alias. To enable creating pseudo fonts in the X-session, check on the Create pseudo on X client request check box. For batch X clients, it is preferable to disable the option to avoid interactive requests.
Unfortunately, pseudo fonts created on X client's requests become accessible only after restarting the X-session. In the current X-session, XServer uses the default font instead of requested one.
Enabling to Use
You can define whether to use pseudo fonts in the X-session or not.
To disable pseudo fonts, check off the Use pseudo fonts check box. Pseudo Fonts Directory will be removed from Font Path. XServer will only use X fonts. You will not be able to create pseudo fonts in the X-session.
To enable pseudo fonts, check on the Use pseudo fonts check box. The Pseudo fonts priority dialog box will appear.
You should define priority of Pseudo Fonts Directory among other font sources in Font Path. To insert Pseudo Fonts Directory into Font Path, select a position and use the Before selection or After selection buttons. XServer will use pseudo fonts as well as X fonts.
The Advanced Tab
In this entry field, you can specify your title for an X-session (and its icon) instead of
its default title.
Initial TCP port number
In this entry field, you can change the default (6000) initial port number for your X-session that XServer will use.
Max size of XSELECTION
This option is used to change the default (1MB) size for X-Selection that may be copied to/from the MS Windows' Clipboard (in Bytes).
Total multi-monitors width