X-Win32 Users Manual
---------------------------------------------------------------------------
10 Jan 1996 (3.2.7)
StarNet Communications License Agreement
1. Read the following terms of the license agreement before
opening and using this product, otherwise opening the product
constitutes acceptance of this agreement. Should you disagree or refuse
to accept these terms, please return the entire package for a refund.
2. StarNet Communications provides the software program and hereby
"licenses its use" on a single computer and associated peripheral
equipment, all at one location.
3. You may copy the program in readable or printed form for
back-up in support of your own use.
4. You may only transfer this program and its "license to use" to
another party if the other party agrees to accept the same terms.
However, any failure on the part of the other party will be cause to
terminate your rights and to render an injunction against you.
5. You may not use, copy, modify or transfer the program except as
provided in this agreement.
6. Title and full ownership rights to the program shall remain the
sole property of StarNet Communications.
------------------------------------------------------------------------------
X-Win32, Copyright 1991-6, StarNet Communications.
All rights reserved. Use, duplication or sale of this product, except as
described in the StarNet Communications License Agreement, is strictly
prohibited. Violators may be prosecuted.
X-Win32 is a trademark of StarNet Communications.
X Window System is a trademark of MIT.
Ethernet is a trademark of Xerox Corporation.
UNIX is a registered trademark of AT&T.
MS-DOS is a trademark of Microsoft.
All other products mentioned in this manual are trademarks or
registered trademarks of their respective manufacturers.
---------------------------------------------------------------------------
---------------------------------------------------------------------------
Contents
---------------------------------------------------------------------------
Chapter 1 - Introduction 5
X-Win32 5
Software requirements: 5
Hardware Prerequisites 5
Chapter 2 Installation 6
PC Installation 6
Starting X-Win32 6
X-Win32 6
Messages 6
X-Util 7
Chapter 3 Using X-Win32 8
Initial Start-up 8
rsh or rexec 8
XDMCP 8
Window Manager 8
Auto Start-up 8
Starting Clients from the Menu 9
Starting Clients from Icons 9
Rsh... or Rexec... 9
X-Win32 Menu Selections 10
Messages Menu Selections 10
Copy & Paste Text 11
From MS Windows to Remote host 11
From Remote host to MS Windows 11
Sun Copy,Cut, & Paste keys 11
To Sun OpenWindows buffers 12
Copy Graphics 12
From Remote host to MS Windows Clipboard 12
Chapter 4 Using X-Util 13
X-Util Window 13
Sessions 14
rsh/rexec 14
Auto-Startup 14
Auto-Restart 14
Host Name 14
Login 14
Command 15
Variable Substitution 16
$DISPLAY 16
$MYIP 16
Sessions - Entry - xdmcp 16
Options - Window Mode... 17
Options - Xhosts... 17
Options - Mouse 17
Options - Resources... 17
Options - Clipboard 18
Options - Network Interface 18
Options - Access Control 18
Options - BackingStore 18
Keyboard - Select Keyboard... 19
---------------------------------------------------------------------------
Keyboard - Edit Keysyms... 19
Keyboard - Left Alt to X 20
Keyboard - Right Alt to X 20
Fonts - Make FONTS.DIR... 20
Fonts - Compile bfd fonts... 20
Fonts - Font Alias 21
Fonts - Modify FontPath 21
Colors - Edit Color Database 21
Colors - Compile Colors 21
Help 21
Help - About 21
Help - Contents - Search 21
Appendix A Host Access 22
Host Access 22
Appendix B XDMCP 23
xdm goals 23
Appendix C Transports 24
Trumpet.....Trumpet Winsock 24
Microsoft.....Win95 24
Ftp Software.....PC/TCP 24
Sun.....PC-NFS 24
Novell.....LWP4Dos 25
WinSock.....Various 25
IP Address Error 25
Appendix D Troubleshooting 26
No X Window(s) 26
Exits after XDMCP login window 27
Cannot open display 28
Cannot run olwm 28
Cannot read text in xterm 28
Client not authorized to connect to server 29
Connection Closed 29
Connection Refused: Host name not known 29
Connection Refused: My IP address not known 29
Connection Timed Out 29
Hanging of X server 29
Hostname: No such file or directory 29
LD:SO lib Xt.so.4 not found 30
Permission Denied: Rsh 30
Permission Denied: File 30
stty: Operation Not Supported 30
Warning: Cannot convert string "..." to type FontStruct 30
Will not start - screen blanks 31
X Toolkit Warning: Cannot allocate colormap entry ... 31
xlock 31
Appendix E Sample Start-up Script 32
Appendix F XWIN32.INI 33
XWIN32.INI 33
[settings] 34
[sessions] 35
[Xhosts] 35
---------------------------------------------------------------------------
Page 5
---------------------------------------------------------------------------
Chapter 1 Introduction
---------------------------------------------------------------------------
X-Win32 X-Win32 is a Microsoft Windows program that will turn an
386/486/Pentium PC into an X Window System server.
X-Win32-Win32 will allow X client programs located on other computers on
the local area network to connect to your computer, and will use your
computer to display the results using the MIT X11 graphical protocol.
Software requirements:
- DOS 5.0 or better
- Microsoft Windows 3.1, WFW 3.11. Window 95, or NT
- Winsock 1.1 (or better) compliant tcp/ip stack.
- Win32s ver 1.2 (or better) with Win 3.1 or WFW 3.11
Hardware Prerequisites
- IBM AT's and compatibles (386/486/Pentium).
- Sufficient memory - A minimum of 4MB of RAM.
- Graphics Card - Microsoft Windows supported VGA, 8514A,
graphic accelerator, or high resolution graphics card.
- Monitor - A monitor matching the supported graphics card.
- Mouse - A Microsoft (or fully compatible) 2 or 3 button
mouse with driver.
- Ethernet card - An Ethernet card that is supported by
the TCP/IP stack used.
- Hard Disk - Minimum of 6MB of free space.
---------------------------------------------------------------------------
Page 6
---------------------------------------------------------------------------
Chapter 2 Installation
---------------------------------------------------------------------------
PC Installation
---------------
1) Start MS Windows (or WFW or ...)
2) Use the Program Manager "Run" option.
A:INSTALL
The Install program will query the user for the drive and subdirectory
for selection. X-Win32 will be installed into that drive and
subdirectory. VBRUN300.DLL and XWIN32.INI will be copied to the
appropriate directory.
Starting X-Win32
----------------
The installation will create a program group named X-Win32.
In that program group will be two program items:
Double clicking on the X-Win32 icon will bring an icon outside of the
Program Manager, X-Win32. This icon will be used to control the
opeartion of X-Win32. Options for X-Win32 will be set using X-Util.
Note: If Win32s is not installed, X-Win32 will not gererate the proper
icon or start-up correctly.
X-Win32
Clicking on the X-Win32 icon in the X-Win32 Program Group will generate
a blue X-Win32 icon at the bottom of the screen. That X-Win32 icon is
used to control the active running of X-Win32. Clicking on this icon
will activate a pull-down menu. Sessions, the Messages window, and the
X-Util will be activated from here.
Messages
The Messages window is activated from the X-Win32 pull-down menu.
Error messages from remote hosts will appear here. If you are having
trouble getting your sessions to start, error messages from that host
should appear here.
Manual Rsh... or Rexec... sessions (only for the current running of
X-Win32) may be created from here. Output from the Rsh... or Rexec...
for commands such as "who" or "ls" will be shown in the Messages
windows.
Debug options (usually only valuable to StarNet support staff) are set
here.
---------------------------------------------------------------------------
Page 7
X-UTIL
------
The X-Util is started from the X-Win32 pull-down menu. X-Util
is used to configure/edit/create sessions, set options, manage the
xhosts table, manage keyboard modifications and mapping, font
compiling, font path management, font directory selection, and color
management.
There are sections for:
Sessions
Creating
Editing
Options
Window Mode
Xhosts
Panning
Manual copy - X to MS clipboard
Network Interface
Keyboard
Select Keyboard
Edit Keysyms
Left Alt to X
Right Alt to X
Fonts
Make FONTS.DIR
Compile .bdf fonts
Font Alias
Modify Fontpath
Colors
Edit color database
Compile colors
---------------------------------------------------------------------------
Page 8
---------------------------------------------------------------------------
Chapter 3 Using X-Win32
---------------------------------------------------------------------------
Initial Start-up
----------------
X-Win32 installs in a passive mode waiting for either an XDMCP, rsh, or
rexec session to be selected.
Clients may also be started by using telnet from the pc or by starting
them from the console (or other connections).
rsh or rexec
------------
rsh = remote shell
rexec = remote exec
Sessions are created using X-Util. A session is composed of a Host
name or ip address, a login for that host, and a command to be executed
on that host. The command may be a unix command or the name of a
script file in the user's home directory on that host.
XDMCP
-----
XDMCP is X Display Management Control Protocol. The user will have to
determine if it is being used. Refer to the troubleshooting section
"No X Windows" if you do not know how to determine if it is running.
XDMCP is not used on most Sun implementations. The modes of starting
an XDMCP session are: Query, Indirect, and Broadcast.
XDMCP can be enabled by selecting XDMCP and the desired XDMCP mode in a
named session. Selecting that session will start the XDMCP session.
If XDMCP is not to be used, then sessions will have to be started using
either an REXEC or RSH command to start an X session. Refer to later
sections in this chapter on the form of the session entries and how to
save them.
Window Manager
--------------
X-Win32 installs using MS Windows as the window manager. The Single
Window Mode is disabled. The Single Window Mode (SWM) must be enabled
(using X-Util) to allow use of a remote window manger such as Tab,
Motif, or Open Look or a desktop such as HP-Vue.
Note: If you are running on a Sun using Open Windows 3.0 and olwm, then
be sure that "Enable screen :0.1" is not selected during SWM
operation.
Auto Start-up
-------------
The "Auto Startup" selection in a named session must be set to have a
session automatically startup upon starting X-Win32. Only one XDMCP
session may be marked Auto Startup. If you mark an XDMCP session Auto
Startup, X-Win32 will automatically unmark all other Auto Startup
selections.
---------------------------------------------------------------------------
Page 9
Starting Clients from the Menu
------------------------------
The "Sessions" option provides a means of creating an rsh or rexec
command string or specifying an XDMCP selection and saving it under a
name.
An rsh and rexec command are provided (in the Messages window) to
immediately execute a command or script on a remote host. The contents
of the "Rsh..." or "Rexec..." commands are lost upon exiting X-Win32.
The results of a Rsh... or Rexec... command, such as ls, who, grep, or
netstat will be shown in the Messages window.
Use "Sessions" then "Edit Sessions" to create a saved rsh/rexec
command. Rsh requires only a "login", while rexec additionally
requires a "password". This command line will be executed on the
remote host selected. This command could simply be an xterm command to
get a single window started. It could also be the name of a script
file on the remote host which would bring the user up in a familiar X
environment.
Starting Clients from Icons
---------------------------
Icons can be generated to start individual clients. From the Program
Manager menu, use the New... option. Create it the same as the X-Win32
program item and add the name(s) of a session after the xwin command.
Multiple session names should be separated by commas, no spaces. The
command line would look like this:
C:\XWIN32\XWIN32 sun1
Multiple clients may also be started from the X-Win32 icon in the
X-Win32 program group. From the program manager, use the
Properties... option to add a string of session names (separated by
commas - no spaces). Thus the Command Line may look like:
Command Line: c:\xwin32\xwin32.exe sun1,sun2,hp1
The above example would automatically start the sessions
sun1
sun2
hp1
when X-Win32 is started.
Rsh... or Rexec...
------------------
This selection (from the Messages window) allows the user to create an
rsh/rexec command to be executed on remote hosts. A temporary (for
this loading of X-Win32 only) rsh/rexec function is provided for
testing and informational purposes. Results or error messages will be
displayed in the Messages window. The user could use this feature to
determine pathing, see a directory, check the environment, or verify
communications with the remote host.
---------------------------------------------------------------------------
Page 10
X-Win32 Menu Selections
-----------------------
Sessions Shows a list of named sessions. These sessions may be marked
Auto Startup.
Show Messages
Activates the Messages Window. Responses from the remote hosts appear
here. Rsh... and Rexec... sessions are created and executed from
here. Debug selections and results are managed here.
X-Util
Activated the utility for working with X-Win32 options, fonts,
keyboards, and colors.
Clipboard
If "Manual Copy - X to MS Clipboard" is selected in the X-Util, the
user will have a choice of pasting from XPrimary, XSecondary, or
XClipboard to the MS Windows Clipboard. The XPrimary selection is used
by the majority of clients.
Help
Starts the Help file. Information on serial number info (ver. 3.2.2
or later) can be found in the About X-Win32 selection.
Messages Menu Selections
------------------------
Rsh...
Lets the user create a Remote Shell command to be executed on the
remote host. Rsh requires a Login on the remote host. Rsh also
requires permission from the remote host. This is usually granted from
a .rhosts file in the Login's home directory or from the system-wide
/etc/hosts.equiv.
Rexec...
Lets the user creaet a Remote EXEC command to be executed on the remote
host. Rexec requires a Login and Password on the remote host.
Debugging
Various debug options may be turned on here. Operation of X-Win32 will
be greatly slowed down by using selections that produce many debug
lines. Normally this option should only be used at the direction of
authorized X-Win32 support people.
---------------------------------------------------------------------------
Page 11
Copy & Paste
------------
Text
Text can be cut and pasted to/from MS Windows and the remote host.
From MS Windows to Remote host
The user will use the standard MS Windows command sequence to cut &
paste to the Microsoft clipboard. The user may then place the contents
of the clipboard into an X window using the middle (or simultaneous
left/right) button.
From Remote host to MS Windows
The user will use the standard sequence (normally holding the left
button down and moving the mouse) to cut text from the X window which
will be placed into the Microsoft clipboard. The data in the clipboard
can be pasted using standard Microsoft paste procedures.
Sun Copy,Cut, & Paste keys
The first point to know is that the normal Sun keyboard under
OpenWindows does not have the keysyms "Cut", "Copy", and "Paste". We
can simulate the Sun operation by assigning F6 to Copy, F7 to Cut, and
F8 to Paste.
The OpenWindows applications use:
"F16" for 'copy'
"F20" for 'cut'
"F18" for 'paste'
Create a text file on the Sun with the following lines:
keysym F6 = F16
keysym F7 = F20
keysym F8 = F18
Then run "xmodmap -e filename".
If you put that in your .xinitrc file you may want to have a
conditional so that it doesn't run xmodmap when you are using the Sun
console. Something like:
if [ "$DISPLAY" != ":0" ]; then
xmodmap pckeys
fi
Where pckeys is the name of the file. If you didn't want to have
another file laying around, you could also do it this way:
if [ "$DISPLAY" != ":0" ]; then
xmodmap -e "keysym F6 = F16"
xmodmap -e "keysym F7 = F20"
xmodmap -e "keysym F8 = F18"
fi
---------------------------------------------------------------------------
Page 12
To Sun OpenWindows buffers
Additions to to .Xdefaults
~Ctrl~Meta:insert-selection(CLIPBOARD, PRIMARY, CUT_BUFFER0) \n\
~Ctrl~Meta:select-end(CLIPBOARD, PRIMARY, CUT_BUFFER0) \n\
Copy Graphics
-------------
From Remote host to MS Windows Clipboard
Graphics can be copied from an X window into the MS Clipboard. In the
selected X window, hold the ALT key down and then the left mouse button
to highlight the area to be copied. Releasing the left mouse button
causes that area to be copied to the Microsoft Windows Clipboard.
---------------------------------------------------------------------------
Page 13
---------------------------------------------------------------------------
Chapter 4 Using X-Util
---------------------------------------------------------------------------
X-Util Window
-------------
X-Util is used to configure/edit/create sessions, set options, manage
the xhosts table, manage keyboard modifications and mapping, font
compiling, font path management, font directory creation, and color
management.
Edit Sessions
Sessions can be created, edited, or deleted. A session can be rsh,
rexec, or xdmcp. A session may be marked auto-startup. At X-Win32
start-up, the marked session would automatically be started.
Note: Only one xdmcp session may be marked auto-startup.
Options
Various X-Win32 server options are grouped here. These options are
Window Mode, Xhosts, Panning, resourses, Manual Copy to MS Clipboard,
and Async Winsock.
Keyboard
A specific keyboard may be selected for X-Win32. Keyboard files can be
edited and saved. The left and right ALT keys may be programmed to go
to X or MS Windows.
Fonts
BDF fonts may be compiled into either .fon or .pcf files. The
FONTS.DIR can be created. Fonts may be aliased to other names. The
fontpath can be modified.
Colors
The color database can be edited and compiled.
Help
Access to X-Win32's help file.
---------------------------------------------------------------------------
Page 14
Sessions
--------
This selection allows the user to create a named (saved) session. This
session may be rexec, rsh or XDMCP. The session may be set to
auto-startup. Note: If an XDMCP session is set to auto-startup, ALL
other sessions will have their auto-startup flags turned off.
Rsh and rexec are both de-facto protocols created with BSD4.1 (TCP/IP
code from Berkeley). Once the connection is established, both
protocols function identically. The difference between the two
commands is in the information set at startup to authenticate the
user. Rexec requires a "Login" and a "Password". Rsh only requires a
"Login". The user may have to create an entry in his "Login" home
directory on the remote host in the ".rhosts" file. This will give
permission for that user to rsh to that host with that "Login".
rsh/rexec
---------
You have the choice of using REXEC or RSH. If "New Session" was
selected, the fields will be blank. If a session was selected, those
entries will be shown. The "Session" may be saved (Accept) or removed
(Delete).
Note: Use of rsh or rexec may not set the users environment. The
pathing may need to be set in .cshrc or .profile.
Auto-Startup
------------
If this box is checked, this session will be automatically started when
the server is started. Multiple (non-XDMCP) sessions may have this box
checked.
Auto-Restart This box only appears on XDMCP sessions. It will cause
the XDMCP session to restart after closing.
Host Name
---------
"Host Name" is the IP address or name of the remote host. Note that
some TCP/IP stacks (or some early versions) do not support host name
resolution, which means that the IP address must be used. Some TCP/IP
stacks have a "HOSTS" list into which the user must manually enter the
host names and corresponding I.P. addresses. This would allow the user
to use host names entered into this list. Forms of this entry may look
as follows:
192.1.1.1 or unix1
Login
"Login" is the users login name to the selected "Host Name".
dick or user1
If this field is left empty, the user will be forced to enter a login
into a window when that session is selected. If the type of session is
rexec, then a password will also be required.
---------------------------------------------------------------------------
Page 15
Command
-------
"Command" is the script file or command to be executed on the remote
host. The command may be only one line which starts an xterm window on
the X server. The following example would bring up an xterm window.
/path/xterm -ls -n WindowName -display xpc:0 &
A sample Xstart script file is included shown in Appendix D. The
following example would run that script file "Xstart" on the remote
host passing the parameter "xpc:0" or "192.1.1.23:0".
Xstart xpc:0 or Xstart 192.1.1.23:0
The command line in our example, 'Xstart xpc:0' contains not only the
script name on the remote host ('Xstart' in this case) but an
additional argument, the name of the 'display'. In X parlance, from
the user's perspective, every X server has a display name in this
form:
hostname:displaynumber.screennumber
X client programs use this information to decide how best to connect to
the X server and which screen should be used by default (on X displays
with multiple monitors). This can be confusing at first. The parts of
the display name are:
hostname - which machine the X display is physically connected to. If
the host name is not given, the X client program assumes that
it is to connect to a server on the same machine, which will
never be the case with a X-SERVER based X server.
displaynumber - in X, the word "display" is normally used to refer to
collections of monitors that share a common keyboard and mouse.
Most PC compatible machines tend to have only one keyboard, and
therefore only one display. A larger, multiuser system may have
more than one display, so that more than one person could be
using X simultaneously, To avoid confusion, each display on a
machine is assigned a display number (starting at 0) when the
X server for that display is started. On a computer running
X-SERVER, the display number will always be 0. The display
number must always be given in a display name.
screennumber - some displays share a single keyboard and mouse among
two or more monitors. Since each monitor has its own set of
windows, each monitor, or screen, is assigned a screen number
(beginning at 0) when the X server for that display is started.
This part of the display name is not required; if it is not
given, then screen 0 will be used.
What this means is that the display name which has been given in the
example command line is composed of the name of the PC running X-SERVER
(in this case, a machine called 'xpc') followed by a ':0'. As is the
case with the rest of the example, this is site-specific and you should
substitute your X-SERVER machine name for 'xpc'.
---------------------------------------------------------------------------
Page 16
Variable Substitution
---------------------
Where the string "$DISPLAY" (capitalization important!) or "$MYIP"
appears in the command field of rsh or rexec, but not preceding another
alphanumeric character, the variable "DISPLAY" or "MYIP" will be
substituted.
$DISPLAY
--------
The variable "DISPLAY" contains the hostname of the PC on which X-Win32
is running followed by ":0". If the hostname of the PC cannot be
determined, MYIP is substituted.
example:
user.company.com:0 = $DISPLAY
/usr/bin/X11/xterm -ls -display my_pcname:0 & is replaced by:
/usr/bin/X11/xterm -ls -display $DISPLAY &
$MYIP
-----
The variable "MYIP" contains the IP address of the PC on which X-Win32
is running in dotted quad notation.
example:
192.1.1.23 = $MYIP
/usr/bin/X11/xterm -ls -display 192.1.1.23:0 & is replaced by:
/usr/bin/X11/xterm -ls -display $MYIP:0 &
Sessions - Entry - xdmcp
This selection configures the xdmcp mode of the X server. You may have
to contact your network administrator to see if XDMCP is being used.
The following chart gives a quick guide:
Query X-Win32 sends an XDMCP query to "Host Name".
"Host Name" must be running XDMCP.
Indirect X-Win32 sends an XDMCP query to "Host Name"
to get another "Host Name" or list.
Old Indirect X-Win32 sends an XDMCP query to "Host Name" to
get
`another "Host Name" or list.
Broadcast X-Win32 sends a broadcast XDMCP query onto the
network. In effect, it says "I am here, manage
me".
Use "Indirect" if your XDMCP host does not run CHOOSER. Use "Old
Indirect" if your XDMCP host runs CHOOSER for your machine. The
optimum configuration is to use the (new) Indirect option and not run
CHOOSER on the host. Using the "Old Indirect" will cause X-WIN32 to
repeat the XDMCP query when the session is terminated. To stop the
query, select another XDMCP session or exit X-WIN32.
---------------------------------------------------------------------------
Page 17
Options - Window Mode...
------------------------
Single Window Mode (SWM)
Selecting the Single Window mode will bring up a Virtual Root window
the next time the server is started. X windows being created for
screen zero on the PC (":0.0") will be created inside the Single
Window. The Virtual Root window will be the size of the screen (minus
borders), if the width and height are not set
A remote window manager (such as twm, open look, motif, ...) may be run
in the Virtual Root window. It is still possible, while in single
window mode, to have X windows managed by the Microsoft window manager
by selecting "Enable Screen :0.1". These window screens would be
defined as:
application -display xpc:0.1
The first screen for xpc is ":0.0", the second screen for xpc is
":0.1".
Options - Xhosts...
-------------------
Xhosts is a host-based access control of those with access to the local
X server. The list is an all or none option. If the list is empty,
all hosts may have access to X-Win32. If there is at least one entry
in the list, then only those hosts who are in the list or those hosts
who pass the Magic-Cookie may have access to X-Win32.
Options - Mouse
---------------
3-button simulation
Simultaneously pressing the left & right mouse buttons will simulate
the middle mouse button.
Panning
Allows partially off-screen X windows (which have the focus) to be
panned on-screen by moving the cursor to the off-screen portion.
Options - Resources...
----------------------
The user will be able to select a level of GDI resources to be
maintained for X-Win32 and other MS Windows applications. The user may
see the current amount of free resources by placing the cursor in the
gray area of the X-Util window and pressing the left mouse button. GDI
resources is the most critical of the two values.
Windows 3.1 and WFW 3.11 have a limited amount of GDI resources
available to all applications. X-Win32 uses GDI resources for pixmaps,
regions, pens, and brushes. X-Win32 will try to maintain the selected
level of free resources. Setting this value too high will cause
X-Win32 to run slower. The optimal setting is 30%.
---------------------------------------------------------------------------
Page 18
Options - Clipboard
-------------------
The clipboard has three options Auto Copy, Manual Copy, and MS Windows
owns selection. Only one of these may be selected at a time.
Auto Copy
Default mode, text highlighted will be automatically copied to the MS
Windows clipboard.
Manual Copy
Turning this selection on will disable auto copying of highlighted text
to the MS Windows Clipboard. The user will be required to use an
option on the X-Win32 pop-up menu to manually paste highlighted text
into the MS Clipboard. Highlighted text may still be copied/pasted
from one X app to itself or another. Some clients, such as mathematica
will require that this entry be selected.
MS Clipboard owns selection
Highlighted text will be automatically copied to the MS Windows
Clipboard. MS Windows will then own the selection. The highlighting
of text will be turned off.
Options - Network Interface
---------------------------
Allows selection of three types of interface to Winsock tcp/ip stacks.
Those interfaces are Async, Blocking, and Polling.
Async
X-Win32 will wait for a message from the Winsock before attempting to
read from the network.
Blocking
X-Win32 calls the Select function from Winsock which returns when network
data is available.
Polling
X-Win32 continusously polls the Winsock interface. This mode is not
recommended if running under Win95 or NT.
Options - Access Control
------------------------
X-Win32 can notify the user when a connection is being
attempted. Access Control must be turned on and the name or Ip Addess
of the host attempting to open the connection must not be listed in the
Xhosts... table.
When Access Control is turned on, a pop-up window will show the user
the ip address of the client attempting to make a connection. If "Yes"
is chosen, the connection will be made. If "No" is chosen the
connection will be refused.
Options - BackingStore
----------------------
When selected, X-Win32 will do backingstore if requested by the X client.
---------------------------------------------------------------------------
Page 19
Keyboard - Select Keyboard...
-----------------------------
A specific keyboard may be selected for use with X-Win32. This may be
a keyboard for a specific country or a specially modified keyboard.
The selection will be displayed in the highlighted Select X keyboard
box.
If you wish X-Win32 to automatically select the .kbd file for you each
time X-Win32 is run, then select AutoSel.
CONTROLS
Keyboard File Box - This is the list of available .kbd files.
Selecting an entry will place that entry into the Select X keyboard
box.
Select X keyboard - This is the selected X keyboard. This will
be the keyboard used the next time X-Win32 is started.
AutoSel - Lets X-Win32 automatically select the keyboard.
OK - Saves selection Cancel - Clears selection and exits.
Keyboard - Edit Keysyms...
--------------------------
The keysym's for a keyboard file may be modified and saved. The user
may use this function to create a custom keyboard file. Keysym
selections are made from a list of standard X keysyms. The customized
file may be saved as a specified name and then selected for use using
Select Kybd.
Modifying a .kbd file is done by the following steps:
1. Select a .kbd file from the list box. Once selected, the list of
keysyms for that keyboard are shown in the Keycode box.
2. Enter a name to save the modified file in the Save .kbd file as:
data field. If the name used matches an existing file, the existing
file will be overwritten.
3. Selecting an entry in the Keycode box will display that data in the
above Unshifted, Shifted, and Alt data fields.
4. The data in the Unshifted, Shifted, and Alt data fields may be
modified by manual editing of the field or by using the down-arrow and
selecting on of the standard X keysyms. Once the entry has been
modified, use the Modify List key to change the Keycode box.
5. Once the Keycode box has the desired modifications, use of the OK
key will save it.
CONTROLS
Selected X kybd - The name of the keyboard selected from the Select X Kybd box.
Save .kbd file as: - The name for saving the modified .kbd file. The .kbd
extension will have to be used for it to appear in this list.
Select X Kybd - A list of the available X keyboards. This list will include
the standard .kbd files shipped with X-Win32 as well as any saved/modified
by the user as long as the .kbd extension is used.
Unshifted - The unshifted keysym. Selecting the
arrow will give a list of available keysyms.
Shifted - The keysym when
also using the shift key. Selecting the arrow will give a list of
available keysyms.
Alt - The keysym when also using the Alt key.
Selecting the arrow will give a list of available keysyms.
Keycode
Shifted Unshifted Alt - A list of the keysym for the selected
keyboard. Theentries are shown from left to right as shifted,
unshifted, and optionally alt. Selecting an entry will cause that data
to be entered into the Shifted, Unshifted, and Alt boxes. Using the
Modify key will replace the selected entry with the data in the
Shifted, Unshifted, and Alt boxes. Modify - Causes the data in the
Shifted, Unshifted, and Alt boxes to replace the data in the selected
entry in the Keycode Shifted Unshifted Alt box.
Cancel - Clears
selection and exits.
OK - Saves the contents of the Keycode Shifted Unshifted Alt box as
the Save .kbd file as: filename.
---------------------------------------------------------------------------
Page 20
Keyboard - Left Alt to X
------------------------
The left Alt key is sent to X and not to MS Windows.
Keyboard - Right Alt to X
-------------------------
The right Alt key is set to X and not to MS Windows. This is the key
that on many international keyboards is "AltGr". This will need to be
enabled to allow Alt+keycode sequences to be enabled.
Fonts - Make FONTS.DIR...
-------------------------
Creates a FONTS.DIR in the selected directory. FONTS.DIR provides the
link between the font description and the actual font file.
Use Select Directory to select the desired font directory. Select
Directory will open a Browse window for locating the desired font
directory. Files in the selected directory will be shown in the Files
list box. Once selected, use Make FONTS.DIR to create (or overwrite)
the FONTS.DIR file.
CONTROLS
Select Directory - Uses Browse to locate/select the desired
font directory
Make FONTS.DIR - Creates/updates the FONTS.DIR file from
existing .pcf & .fon files in the current directory.
Fonts - Compile bfd fonts...
----------------------------
The bdf (ascii) font files may be compiled into .fon or .pcf fonts.
The .fon fonts are faster and perferred in most cases. The .pcf
(portable compiled fonts) are 2-byte fonts suitable for very large
fonts, and required for those with more than 256 characters. Pcf fonts
may be compiled into .fon type fonts.
The fonts (.bdf) will be compiled from a source directory into a
destination directory. These directories may be the same, but will
need to be selected. The font type should be selected prior to
selecting the destination font directory.
CONTROLS
Select Source Dir - Uses Browse to select the source
directory. This directory should contain .bdf (text format) font
files. Once this directory has been selected, the files to compile
need to be selected. A individual file or a block of files may be
selected (highlighted).
Select Dest Dir - Uses Browse to select the destination directory.
This directory should/will contain .pcf or .fon X-font files.
Select Font Type - The two choices are .pcf (portable compiled fonts)
and .fon (MS windows format). The .pcf files are scalable and will
handle large 2-byte fonts. The .fon files are drawn using MS routines
and are thus faster.
Compile - Compiles the selected source fonts into the selected Dest
directory. Make fonts.dir - This option is the same as the higher
level Make FONTS.DIR. The user has the option of updating/creating the
fonts.dir file while using the compile option. The user may wish to
compile fonts from one directory and update the destination directory
and then compile fonts from another directory into yet another
directory and then update the fonts.dir in that directory, all without
leaving the Compile Fonts window.
---------------------------------------------------------------------------
Page 21
Fonts - Font Alias
------------------
A font may be aliased to another font. FONTS.ALI is searched for a
match, if found then that font description is used to search FONTS.DIR
to find the actual font file.
Fonts - Modify FontPath
-----------------------
The fontpath can be modified to include new font directories. The font
directories need not reside under the \xwin32 directory structure.
Colors - Edit Color Database
----------------------------
The color database may be edited (using the Notebook editor).
Colors - Compile Colors
-----------------------
The color database will be compiled.
Help
----
A help menu is provided to give the user information to help in the
installation and operation of X-Win32.
Help - About
The About section give the version number of X-Win32. It also gives
the email address and telephone number for customer support.
Help - Contents - Search
Help for X-Win32 is given under Contents or by searching on key words.
---------------------------------------------------------------------------
Page 22
---------------------------------------------------------------------------
Appendix A Host Access
---------------------------------------------------------------------------
Host Access
-----------
When an X client attempts to open an X display, the server checks to
see if that client is authorized to connect before it allows the
connection. If the client is not authorized, it gives a message such
as:
Xlib: Connection to "server:0.0" refused by server Xlib:
Server is not authorized to connect to host Error: Can't open
display
The X11R3 release gave only one method of authorizing clients to
connect. That method is giving access based on the IP address of the
host on which the client runs, also known as "xhost". The disadvantage
of this method is that when you give access to a host, call it "host1",
everyone who has an account on "host1" can access your display.
X11R4 introduced a new method of authorizing clients, called X
authorization, or MIT-MAGIC-COOKIE-1. When you log in using X11,
revision 4, xdm creates a file named ".Xauthority" in your home
directory. In this file is a 16-byte key, or cookie, that is sent to
the server as part of the connection setup information by X11R4
clients. If your client is running on a host that is not in the
"xhost" list, but the client sends the correct cookie, then it will
still be allowed to connect. Thus, when using an X11R4 xdm, your
"xhost" access list will typically be empty but clients will still be
able to connect.
X-Win32 obtains the "magic cookie" from xdm using XDMCP. The cookie is
generated by a random generator in xdm. If X-Win32 is started this
way, the initial "xhost" access list is empty, and access is
restricted. If it is not started with XDMCP, then access control is
disabled (any client is allowed to connect).
If you use an X11R4 xdm to get your login window, and want to bring up
older (R3) clients on your display, you need to add the hosts on which
those clients run to your access list. To do this, simply add the host
using the xhost command before bringing up the window. You can make a
permanent list of hosts that are in the access list of X-Win32 by
adding those hosts to the Xhost list under the Options selection. You
may want to do this in two cases:
1. You use X-Win32 in the non-XDMCP mode (any client can connect),
and want to limit the access list to "trusted" hosts.
2. You use it in the XDMCP mode (only R4 clients with correct
cookie allowed) and want to allow R3 clients from specific
hosts to connect to your server.
Clients are granted access if:
XDMCP
1. the client passes the correct MIT-MAGIC-COOKIE-1.
or
2. the client resides on a host whose IP address is in
the Host Access list.
Non-XDMCP
1. there are no entries in the Xhost list.
or
2. the client resides on a host whose IP address is in
the Xhost list.
A client can change the Host Access list (residing in local RAM memory)
if its entry in the Xhost list is preceded by a plus sign (+).
---------------------------------------------------------------------------
Page 23
---------------------------------------------------------------------------
Appendix B XDMCP
---------------------------------------------------------------------------
X-Win32 uses the standard protocol specified by the X Consortium for
use with X terminals, the X Display Manager Control Protocol, or
XDMCP. XDMCP is used by X terminals to control the xdm program on a
host on the network, The X terminal sends a request to the xdm host,
the host and the X terminal send a few XDMCP messages between
themselves, and then the xdm program brings up a login window on the X
terminal. XDMCP is a part of revision 4 of X version 11 and is
available from Sun as part of SunOS 4.1 or from DEC as part of Ultrix
4.2. If you have a host on your network with these versions or later,
you should run X-Win32 in one of the XDMCP modes if you want to use xdm
to manage your X server.
xdm goals
---------
A major goal of providing a display manager program is to integrate the
X terminal completely into a networked environment. As nearly as
possible the "log-in window" should automatically appear after the X
server is started.
Once you log in, an automatic initialization procedure should run to
bring up applications and position their windows as specified in your
personal session "profile" script. After you log out of the X session,
all connections should be closed, the terminal should be reset to a
known state, and a new log-in window should appear, ready for the next
user. This scenario can be achieved by having the X server communicate
with a display manager program between user sessions.
If you are running X11R4, you do not need to make any additions to the
host. However, if your are running X11R3, you may need to add a line
to the "Xservers" file on the host in the directory /usr/lib/X11/xdm.
The line you must add is "PC:0 foreign PC" where PC is the name of your
personal computer.
---------------------------------------------------------------------------
Page 24
---------------------------------------------------------------------------
Appendix C Transports
---------------------------------------------------------------------------
The supported winsock transports should already be configured to run
under Microsoft Windows. If it is not running properly, check the
following:
Trumpet.....Trumpet Winsock
---------------------------
For best use the Trumpet MTU setting should be 512.
It comes preset to 1500.
Microsoft.....Win95
-------------------
When using PPP it may be necessary to change the mtu setting to 552.
Hkey_Local_Machine\System\CurrentControlSet\Services\Class\NetTrans\00x
(Where x will be some integer depending on your system.)
1. From the Run menu enter "regedit"
2. Make selections on above path down to 00x.
Select the 00x section for "tcp/ip"
3. Select "New String Value".
Edit string to read "MaxMTU"
4. Under Edit, select Modify.
Enter "552"
5. Exit
000 ab(Default) (value not set)
ab DeviceVxDs
"vtdi.386,vip.386,vtcp.386,vdhcp.386.vnbt.386" ab
DevLoader "*ndis" ab DriverDesc
"TCP/IP" ab InfPath "NETTRANS.INF"
ab IPAddress "0.0.0.0" ab
Mask "0.0.0.0" ab
MaxMTU "552"
Ftp Software.....PC/TCP
----------------------
PC/TCP should be run in the 386 enhanced mode.
The following options should be used with the kernel startup:
[pctcp kernel] tcp-connections =15
The following may need to be added to SYSTEM.INI under [386Enh].
device=C:\ftp\vpctcp.386 UniqueDOSPSP=TRUE
PSPIncrement=5
Sun.....PC-NFS
--------------
The following may need to be added to SYSTEM.INI under [386Enh].
InDOSPolling=on UniqueDOSPSP=true PSPIncrement=5
TimerCriticalSection=1000
---------------------------------------------------------------------------
Page 25
Novell.....LWP4Dos
------------------
The default setting (no entry) in the net.cfg file for "tcp sockets"
is 8. To increase the number of sockets:
Protocol TCIP
tcp_sockets 16
Recommended changes to the net.cfg file
Link Support Buffers 16 3000 MemPool 8096 Max Stacks 16
WinSock.....Various
-------------------
Implementations and revisions of WinSock vary. The X server needs
to know the IP address of the PC. The above "IP Address Error"
may appear. It may be necessary for the user to either have:
1. the domain name server specified
(if the transport does host name resolution)
or
2. put an entry into the local HOSTS table for the PC.
(The entry should have the PC's name and IP address.
This file will usually look like the /etc/hosts file.)
IP Address Error It the error "I don't know my IP Address" appears
while trying to start-up in any mode, then the IP Address and Name of
the PC should be entered into TCPOpen under the DATABASE option into
HOSTS.
---------------------------------------------------------------------------
Page 26
---------------------------------------------------------------------------
Appendix D Troubleshooting
---------------------------------------------------------------------------
No X Window(s)
--------------
The X-Win32 icon was selected, and a session was then selected, but no
X windows appeared. When having trouble getting the connection
started, it is best to not have auto-startup turned on for any
sessions.
1. Check the Messages window for messages.
2. If one of the XDMCP modes was selected, you must make sure that xdm
is running. This can be done by using the Rsh... or Rexec...
function with the following command:
ps -ax | grep xdm
Look in the X-Win32 window for the results. If xdm is not
running, check with you system administrator. If xdm is
running, determine next if it is an X11R4 or later XDMCP
version:
netstat -an | grep 177
If an X11R4 or later xdm deamon running, the following line
will appear in the Messages window:
udp 0 0 *.177
3. A session will have to be started by selecting one of the
entered sessions. If there are not any entered sessions, then one,
or more, will have to be configured. All entries under the Sessions
list are started using either RSH or REXEC. The user should make
sure that the hosts can accept these commands. RSH may require an
entry in
.rhosts in that users home directory.
---------------------------------------------------------------------------
Page 27
Exits after XDMCP login window
------------------------------
After you log in to the XLOGIN window, xdm executes the script
Xsession, which is usually in /usr/lib/X11/xdm. (Sun's may be in
/usr/openwin/lib/xdm).
Note: If the login session is in failsafe mode (invoked by pressing
the F1 key instead of Return after you type your password) Xsession
simply runs an xterm.
If it is in normal mode, Xsession runs the file ".xsession" in your
home directory. In all cases, when Xsession exits, because the xterm
it runs exits or because the .xsession script exits, xdm will kill all
the windows on your display and log you out.
---------------------------------------------------------------------------
Problem:
Setting up a .xsession file with everything running in the
background causes .xsession to exit early.
For instance, if your .xsession file looks like this:
xrdb ~/.Xdefaults twm & sleep 4 xterm &
Then immediately after the xterm starts, .xsession will exit
which will cause you to be logged out. This will almost always
happen before xterm even has time to create a window.
Solution:
To fix this problem, change the last line to:
exec xterm
---------------------------------------------------------------------------
Problem:
Having a .xsession file in which the last program to be
executed fails and exits.
This could be for several reasons:
1. Because the program is not in your search path when
.xsession is run. To solve this problem make sure your path is
set up correctly in .xsession itself. Don't depend on the
program which calls .xsession to set it for you.
2. An X version incompatibility. In version 4 of the X
protocol, two things were added. The first was XDMCP. Thus,
if you are using XDMCP to get your XLOGIN window, you have at
least an X11 R4 version of xdm. The second thing added was the
MIT-MAGIC_COOKIE authorization. Under this scheme, a client,
upon connecting to the X server, sends some authorization
information. This is usually a 128-bit number that the server
has chosen and given to xdm using XDMCP. Xdm stores this
number in a file called ".Xauthority" in your home directory.
3. If X-Win32 is not in the Virtual Root (Single Window Mode)
and the last program is a window manager, then it will fail
because X-Win32-WIN32 uses the Microsoft window manager, which
will not allow an X window manager to run.
4. Virtual Root (Single Window Mode) is selected with the
"Enable Screen :0.1" selected and olwm is running under Open
Windows 3.0.
5. If you are using, for example, xterm from X11 R3 in the
last line of your .xsession file. It will not know how to send
this authorization information to the server. As a result, the
server will refuse the connection, xterm will exit, causing
.xsession to exit and your session will be terminated.
---------------------------------------------------------------------------
Page 28
Solution:
(1 thru 4) To solve the first problems you can start the X
server with XDMCP disabled, then log into your host system from
a different terminal. Set the environment variable "DISPLAY"
to your PC, set your PATH variable to the default (to
trouble-shoot problems with the search path), then run your
.xsession file by typing "./.xsession". If this terminates and
you get the shell prompt again, then something is wrong. Any
error messages should have appeared on your screen to help you
trouble-shoot the problem.
(5) Use the "Xhost" menu to add the IP address of your host to
the list of hosts that can connect without authorization.
---------------------------------------------------------------------------
Cannot open display
-------------------
Usually this error will occur if the display has not been properly defined.
As an example, the form of a display statement in an xterm command is:
-d dispname
Specifies the display screen on which xterm displays its window. If
the display option is not specified, xterm uses the display screen
specified by your DISPLAY environment variable. The display option has
the format hostname:number. Using two colons (::) instead of one (:)
indicates that DECnet is to be used for transport.
-display dispname
This option is the same as the -d option.
xterm -display 192.1.1.23:0 xterm -display davepc:0
Cannot run olwm
---------------
Cannot run OpenLook window manager (olwm)If you are running on a Sun
using Open Windows 3.0 and olwm, then be sure that:
"Enable screen :0.1"
is not selected during Virtual Root (single window) mode operation. If
"Enable screen :0.1" is enabled, then olwm should be started using the
form:
olwm -single &
Cannot read text in xterm
-------------------------
An xterm has come up, but the text is not readable. The cursor changes
as it is moved into and out of the xterm indicating that it is active.
This is usually a color problem. Either the colors selected for the
xterm are not correct or not available. It MS Windows is set to 16
colors and the xterm colors have been selected based on 256 colors, it
is possible to have both foreground and background mapped to the same
color.
This problem can also be caused by using "crystal fonts" on the ATI
video boards. The ATI software locks around 247 palette entries. This
is most noticeable when 256 colors is selected under the MS Windows
video driver setup.
---------------------------------------------------------------------------
Page 29
Client not authorized to connect to server
------------------------------------------
This happens because the client does not have authorization to connect
to this X server (X-Win32). Use of the Xhost table or the Host Access
List will give access to that client. Use the X-Utility to add needed
clients (hosts).
REMEMBER that the Xhost table is an all or none type list. If one host
is in the list, then ALL hosts which wish to have access to X-Win32
will either have to:
1. be in the Xhosts table
or
2. pass the magic cookie
Connection Closed
-----------------
I.P. Address or Hostname: connection closed.You should contact your
system administrator. A connection was made and the host closed the
connection. This may occur if:
1. you are trying to connect using rexec and rexecd or
in.rexec will not allow the connection to continue.
2. your host is running Sun OS and /etc/inetd.conf is not
correct or is trying to run something that does not exist.
3. your host is running a tcp wrapper that closes the
connection for security reasons.
Connection Refused: Host name not known
---------------------------------------
The Winsock compliant TCP/IP stack is responsible for resolving host
names to IP addresses. It may do it by using a DNS or by a local HOSTS
table. It may be necessary to enter the host names and ip addresses
into a local HOSTS table. Check the docs on your TCP/IP software. It
may be necessary to enter the name and ip address of the local pc
also.
Connection Refused: My IP address not known
-------------------------------------------
The TCP/IP stack needs to tell the X server (X-Win32) the IP address of
the PC. This information may need to be added to the local HOSTS
table.
Connection Timed Out
--------------------
You tried to connect to a host that is currently down or otherwise
unreachable.
Hanging of X server
-------------------
The user may encounter cases where the X server hangs. If running
under Windows 3.1 or WFW 3.11, try turning off the Async Interface
option using X-Util.
Hanging of the X server has only been observed using older versions of
Novell's tcp/ip winsock implementation. Report any other occurrances
of hanging to support@starnet.com.
Hostname: No such file or directory
-----------------------------------
You are likely trying to use rsh, but are running the restricted shell
instead of the remote shell. You should change your path to get the
remote rsh.
The remote shell is normally /usr/bin/rsh. The restricted shell is
normally /usr/lib/rsh.
---------------------------------------------------------------------------
Page 30
LD:SO lib Xt.so.4 not found
---------------------------
This is the result of the host (Sun SPARC) system being shipped or
installed with some files being placed in a different directory.
Either the shared library cache is out of date, the shared library is
missing, or the shared library is not in your LD_LIBRARY_PATH. You
should either set the LD_LIBRARY_PATH environment variable ot the
appropriate value, run ldconfig to update the library cache, or install
the missing library. Try placing the following command into your home
directory, into the .cshrc file:
setenv LD_LIBRARY_PATH /usr/lib:/usr/openwin/lib
The directory path and the location of this file should be verified on
the host system prior to inserting the setenv line.
Permission Denied: Rsh
----------------------
A user must have an account on the remote host. A .rhosts file entry
allows a user who has an account on that host to log in from a remote
node without supplying a password. The .rhosts file must be in the
user's home directory. The format of a .rhosts file entry is:
hostname [username]
The hostname is the name of the local node (PC) from which the user
wants to log into the remote host. The username is the user's login
name on the PC. If you do not specify a user name, the user must have
the same login name on both the remote host and PC.
Each remote machine may have a file named /etc/hosts.equiv containing a
list of trusted hostnames with which it shares usernames. Users with
the same username on both the local and remote machine may rsh from the
machines listed in the remote machine's /etc/hosts file.
Permission Denied: File
-----------------------
If a script file is being executed, it must have execution permission.
Use:
chmod 775 script_filename
to allow execution and r/w permissions.
stty: Operation Not Supported
-----------------------------
If you are using rsh, the .cshrc file on the remote host probably has
an interactive command in it, such as stty.
Warning: Cannot convert string "..." to type FontStruct
-------------------------------------------------------
You cannot access the specified font, either because it does not exist
or because X-Win32 does not have access to it.
---------------------------------------------------------------------------
Page 31
Will not start - screen blanks
------------------------------
This can happen when running unders Windows 3.1 or WFW 3.11 and Win32s
has not been installed. Check to see if Win32s is installed. Check
the file \windows\system\win32s.ini. If it does not exist or the
version is 1.15 or less, then the current version of Win32 will need to
be installed.
Win32s is available from Microsoft at ftp.microsoft.com in
/Softlib/MSLFILES. Check the INDEX file in /Softlib for the filename
of the current version of Win32s (usually PW1118.EXE).
X Toolkit Warning: Cannot allocate colormap entry for ...
---------------------------------------------------------
Your color database is corrupted. You need to recreate the color
database. Use the X-Utility to verify and recompile the color
database.
xlock
-----
X-Win32 requires that the IP address of the host running xlock to
be in the XHOST table. Use of the -remote option is also required.
---------------------------------------------------------------------------
Page 32
---------------------------------------------------------------------------
Appendix E Sample Start-up Script
---------------------------------------------------------------------------
The user may wish to use a script start-up file in conjunction with the
RSH or REXEC commands. This start-up script file would reside on the
remote host in the users login directory. This would allow the user to
create his own X environment each time the X session is started. The
following example will set the display and then provide an xterm, an
xclock, and an xlogo each time this file is run.
The session entries may look as follows:
unixhost
dick (not needed for PC-NFS)
Xwin xpc (using the nickname of the PC)
or
Xwin 192.1.1.23 (using the IP address of the PC)
The start-up script file, which resides on the remote host, may be as
follows:
#!/bin/sh if [ "$1" ]; then (Set the display to the value
DISPLAY=$1:0.0 passed from RSH/REXEC)
export DISPLAY
fi
/usr/bin/X11/xterm -n Login -ls &
/usr/bin/X11/twm & (Use only if SW Mode)
/usr/bin/X11/xlogo &
for Sun Sparc's the path may be:
/usr/openwin/bin/xterm
---------------------------------------------------------------------------
Page 33
---------------------------------------------------------------------------
Appendix F XWIN32.INI
---------------------------------------------------------------------------
XWIN32.INI is a text file residing in the appropriate WINDOWS directory
which controls the set-up of X-Win32.
XWIN32.INI
--------------------------------------------------------------------------
[settings]
directory=c:\XWIN\lib
fontpath=c:\XWIN\lib\fonts\misc,c:\XWIN\lib\fonts\75dpi
rootname=X-Win32
mouse=2
debug=0
single=0
width=1016
height=732
screen1enable=0
Alt=2
debug=61440
KBDfile=us.kbd
resources=30
display=0
[sessions]
bart_ultrix=1:bart:demo::Xwin dick:0
esix=2:192.1.1.6:demo::./Xwin dick:0
sparc=1:sparc:demo::/usr/openwin/bin/xterm -ls -n sparc -display
192.1.1.13:0 & sun_360=1:192.1.1.15:dick::Xwin dick:0
[Xhost]
---------------------------------------------------------------------------
Page 34
[settings]
directory=c:\XWIN\lib
This directs X-WIN32 to the subdirectory that contains the keyboard,
rgb, and font files.
fontpath=c:\xwin32\lib\fonts\misc,c:\xwin32\lib\fonts\75dpi
mouse=2
One (1) = on and zero (0) = off.
0 = no 3-button simulation & no panning
1 = 3-button simulation & no panning
2 = no 3-button simulation & panning
3 = 3-button simulation & panning
Panning will move the selected X window on-screen by moving the cursor
to the edge of the window which is off-screen. Panning is not
operational inside the Virtual Root.
debug=0
One (1) = on and zero (0) = off.
Debug gives a list of the X requests being processed by the X server
(X-Win32). These requests are shown in the X-Win32 window. The
X-Win32 window may be resized to view more past requests.
single=0
width=1016
height=732
One (1) = on and zero (0) = off.
Single controls the Virtual Root Mode. If it is turned on, then a
single X window, whose dimensions are described by width and height, is
generated. A remote window manager should be used to manage the
windows created in this Virtual Root Window (single window).
screen1enable=0
One (1) = on and zero (0) = off.
Screen1enable, when turned on, allows the generation of X windows to
xpc:0.1, the second screen. This second screen is managed by the
Microsoft window manager.
KBDfile=us.kbd
This entry tells X-Win32 which keyboard file to use. The available
.kbd files are in \xwin\lib. If this field is not present X-Win32
checks MS Windows to select the proper keyboard. If it cannot
determine the proper .kbd file it will default to the built-in us.kbd
file.
Alt=2
This entry directs the left and right Alt keys. 0 = both to MS,
1 = left to X, 2 = right to X, 3 = both to X.
resources=30
Microsoft Windows 3.1 and WFW 3.11 have limited GDI (graphics)
resources. X-Win32 will try to maintain the selected level of % of GDI
resourses free. Obviously, you must start with greater than the amount
selected for X-Win32 to try to maintain that level. Setting the level
too high will cause X-Win32 to run slower.
---------------------------------------------------------------------------
Page 35
display=0
The X Window system allows more than 1 X server, also called a display,
to run on one machine (IP address). To distinguish between diferent X
servers (displays) on the same IP address, different TCP ports are used
starting with 6000. Display 0 listens on TCP port 6000, display 1
listens on TCP port 6001, display 2 listens on 6002, and so on.
The "DISPLAY" parameter to an X client tells it to which port to
connect. The display number is the first number to the right of the
colon (:).
X-Win32 can be configured to serve as any display number. The display
number is specified in the XWIN32.INI file as "display=n" where n is
the displaynumber, which defaults to 0. X-Win32 can only be run once
per PC serving as only one display at a time.
[sessions]
Named rsh, rexec, or xdmcp sessions.
[Xhosts]
A list of those hosts having access to X-Win32. No entries mean that
all hosts have access to X-Win32. If one entry is made to allow
access, then all hosts that wish to have access to X-Win32 will either
need to pass the magic cookie or be in this list also. It is an all or
none type field.
---------------------------------------------------------------------------