 
 
            ========================================= 
           |                                         | 
           |            Release Notes for            | 
           |                                         | 
           |      eXcursion V2.0 for Windows NT      | 
           |                                         | 
           |                May 1995                 | 
           |                                         | 
            ========================================= 
 
 
 
These Release Notes contain important information that is not included 
in the eXcursion User's Guide or eXcursion Online Help. They pertain to 
eXcursion for Windows NT, version 2.0. Windows 3.1 is not supported in 
this release. 
 
The following topics are discussed: 
 
1.0  eXcursion V2.0 Features 
 
2.0  Installation Notes 
 
3.0  Known Problems and Limitations 
  
4.0  Serial line support 
 
5.0  Hebrew-Specific Information 
 
6.0  Undocumented Features 
 
======================================================================= 
1.0  EXCURSION V2.0 FEATURES 
======================================================================= 
This version of eXcursion is a 32-bit implementation of the X11R6 
Server. While we have maintained the features of eXcursion V1.2, many 
new features have been added.  The following is a partial list of the 
new features. 
 
single-window mode: 
This allows you to run all your X applications in a virtual workstation 
desktop window. 
 
serial line support: 
Allows you to run X applications over serial line (including phone line) 
connections. 
 
XDMCP: 
The X Display Manager Control Protocol is now supported.  This includes a 
local "chooser" interface. 
 
Font Formats: 
Many more font formats are now supported.  This version of eXcursion 
supports the following font formats: .FON, .BDF, .PCF, Speedo, Type1, 
and SNF.  Font servers are now also supported. 
 
Xdefaults Initialization: 
eXcursion now lets you specify an Xdefaults file that is read when the 
server starts.  This eliminates the need to run applications such as 
XRDB to initialize application display preferences. 
 
XIE: 
The X Image Extension is now supported.  Both versions 3 and 5 are 
included.  See the notes on installation. 
 
Shape extension: 
Support for non-rectangular windows.  This has some limitations in 
multi-windows mode. 
 
Other extensions: 
eXcursion now supports several new extensions, including, Xtest, Record, 
BigRequest, XC-Misc, MIT-misc. 
 
SaveUnders & BackingStore: 
These are now supported fully in the single-window mode.  Only 
SaveUnders are supported in multi-window mode. 
 
Enhanced Logging: 
Messages from the server can now be written to either a log file, a 
message window or to the NT event logger. 
 
Mouse Button 2 Emulation: 
This version allows emulation of the middle mouse button by clicking on 
both mouse buttons simultaneously. 
 
Improved Alt Key Handling: 
eXcursion now allows the two Alt keys to act independently.  You can 
configure either Alt key or both to be passed to the X application 
rather than being processed by Windows. 
 
Motif Window Manager: 
We have included the Motif Window manager (mwm) on the CD.  This runs as 
an X application on your NT system. 
 
Sample X Applications: 
We have included sample NT X applications from the eXcursion SDK.  
Included are xeyes, ico and xeyes. Xeyes is a good demonstration of the 
use of the Shape extension. To get the full effect you should run it in 
single window mode with a remote window manager that supports the shape 
extension. 
 
======================================================================= 
2.0  INSTALLATION NOTES 
======================================================================= 
Kit Location: 
The default location for the eXcursion tree is now c:\win32app\xcursion.  
Setup will substitute your system drive for drive C.  The former default 
location was c:\xcursion.  The tree is otherwise similar to the former 
location, however font directories have been added and some renamed. 
 
Serial Line: 
For notes on serial line host software installation see section 4.0 of 
this document. 
 
MWM and Sample X Applications: 
The sample X applications are in subdirectories of the XAPPS directory 
on the CD.  These subdirectories corresponds to your hardware (Alpha, 
X86, Mips).  To install these, simply copy the programs you want to a 
directory that is in your PATH. You must also copy X11.DLL. 
 
Host Software: 
The host software for serial line and for remote starting applications 
over DECnet is now in the directory XCURSION\HOST.  Under this directory 
you will find a directory for each host platform. See the "Post 
Installation Tasks" section of chapter 2 of the eXcursion User's Guide. 
 
======================================================================= 
3.0  KNOWN PROBLEMS AND LIMITATIONS 
======================================================================= 
Platforms: 
This release of eXcursion only supports Windows NT version 3.5. 
 
Copying Font Directories to Vms Systems: 
If desired, The eXcursion X fonts can be be copied to a VMS system and 
accessed over DECnet (DAP). File Manager is one tool that may be used to 
copy the files to the VMS system. Users doing this should be aware of 
one effect: The x11r6 font index file is named FONTS.DIR. On VMS 
systems, .DIR is a special extension that signifies a directory. Because 
of this, some file-transfer programs will rename the FONTS.DIR file to 
have a different extension, e.g., FONTS.__DIR. If this happens, simply 
rename the file b 
 
$ rename fonts.__dir fonts.dir 
 
Full Drag: 
X windows will not repaint until the window being moved has been 
released. 
 
Changing Program Group Icons When Password Changes: 
When your account password changes, the applications icons in the 
eXcursion Program Group do not record that change. Add the apps icons 
associated with that account using the Add Icon button on the 
Applications Page. Note that it is not necessary to delete the old icon 
first -- the new icon replaces the old one automatically. 
 
Drawing to the Root Window: 
The root window drawing has the following known problems in multiwindows 
mode: 
 
 - eXcursion does not capture mouse input to the root window. 
 
 - Expose events on the root window are not sent back to the X 
applications using the root window. 
 
Starting X Applications on an OpenVMS Host using TCP/IP: 
Note the following when you try to start X applications on an OpenVMS 
host using TCP/IP: 
 
 - For DEC TCP/IP (UCX) Version 2.0, the maximum number of simultaneous 
connections to the REXEC server defaults to 3, and any further 
connection requests will fail.  Unfortunately, because of a limitation 
in UCX, eXcursion cannot determine the cause of the failure. 
 
In this case, eXcursion displays the following error message: 
 
     TCP/IP Remote Startup Error 
     REXEC session aborted by node: <node> 
 
You should check the value and increase it if necessary.  To check the 
current UCX REXEC configuration, enter the following command in your 
account on the UCX host: 
 
     $ UCX SHOW SERVICE REXEC /FULL 
 
 - For DEC TCP/IP (UCX) Version 2.0, repeated login failures will cause 
an OpenVMS "login breakin evasion."  When this occurs, all users will 
get the following error message when starting applications from 
eXcursion: 
 
     Remote Start: 'INTERnet ACP AUXS failure Status = %LOGIN-F-EVADE' 
 
To clear the "breakin evasion" state, enter the following DCL command 
from an account with CMKRNL and SECURITY privileges: 
 
     $ DELETE /INTRUSION_RECORD "INTERnet" 
 
 - If a version prior to Version 2.0 of DEC TCP/IP (UCX) software is 
installed on the host, you cannot start X applications from eXcursion. 
(REXEC is not supported by early versions of UCX.) You must log in to 
your account on the host and enter commands to display the application 
on your PC. 
 
For more information on displaying X applications from the host, see 
eXcursion online help. 
 
 - For DEC TCP/IP (UCX) Version 3.0, if you receive the following 
message from OPCOM on an OpenVMS system when trying to remote start 
applications from eXcursion: 
 
     "INTERnet ACP REXEC Reject Request - unprivileged port - from Host" 
 
you should modify UCX with the following commands: 
 
     UCX> SET SERVICE REXEC /FLAG=PRIV 
     UCX> DISABLE SERVICE REXEC 
     UCX> ENABLE SERVICE REXEC 
 
 - For Wollongong WIN/TCP Version 5.2 for OpenVMS, you must copy the 
WOLL.COM file to the OpenVMS host in addition to the PCX.COM file. 
Follow the instructions at the beginning of the WOLL.COM file. 
 
 - For Multinet Version 3.1, you must copy the MN.COM file to the 
OpenVMS host in addition to the PCX.COM file. Follow the instructions at 
the beginning of the MN.COM file. 
 
 - For Process Software TCPware Version 3.1-3 for OpenVMS, you must: 
 
1.  Edit the PCX$SERVER.COM file. 
 
2.  Locate the following line: 
 
     /transport=tcpip 
 
3.  Change the /transport= switch to the following: 
 
     /transport=tcpware 
 
DECterm Displays: 
The following is a list of known problems with DECterm displays: 
 
 - Can't open display 
 
 - You may receive one of the following errors while you are trying to 
start X applications from an OpenVMS DECterm session created by 
eXcursion: 
 
     Can't Open Display 
     %SYSTEM-W-NOSUCHDEV, no such device available 
 
If you receive one of these messages, you should add the following DCL 
commands to the beginning of your LOGIN.COM file: 
 
     $ Assign NL: SYS$OUTPUT 
     $ On Warning Then GoTo NoDisplay 
     $ Show Display/Symbol 
     $ Set Display /Create /Node='DECW$DISPLAY_NODE' - 
                           /Screen='DECW$DISPLAY_SCREEN' - 
                           /Server='DECW$DISPLAY_SERVER' - 
                           /Transport='DECW$DISPLAY_TRANSPORT' 
     $ NoDisplay: 
     $ Deassign SYS$OUTPUT 
 
These commands will create a permanent DISPLAY from the temporary 
DISPLAY in effect when the DECterm was created.  If you want this change 
to affect all users, you can put these commands into SYLOGIN.COM 
instead. 
 
Redirecting STDOUT and STDERR for UNIX Applications: 
If you use X applications that write warning and error messages to 
"standard out" or "standard error" files from UNIX nodes over TCP/IP, 
you should consider redirecting these messages to a log file or to the 
null device.  Failure to redirect the messages may cause the X 
application to fail. 
 
For example, if you are using the Bourne shell, you can define your 
xterm application command line as one of the following: 
 
     xterm > xterm.out >& xterm.err 
     xterm > /dev/null >& /dev/null 
 
See your UNIX documentation for more information about command syntax. 
 
Deleting Remote Processes Created by eXcursion: 
If you use X applications running over TCP/IP from a UNIX node and you 
turn off or reboot your PC before exiting eXcursion or stopping the X 
applications, the processes may continue to use process space on the 
UNIX host and must be deleted manually. 
 
For DECnet, this deletion process is handled automatically. 
 
Requested Environment Variables for Sun OpenWindows Applications: 
If you use Sun OpenWindows applications, you must set the three 
environment variables in your shell initialization file on the Sun host. 
 
Use the following table to set your environment variables: 
 
----------------------------------------------------------- 
Set this environment 
variable...               To... 
----------------------------------------------------------- 
 
LD_LIBRARY_PATH           /usr/openwin/lib 
 
XAPPLRESDIR               /usr/openwin/lib/X11/app_defaults 
 
OPENWINHOME               /usr/openwin 
 
Motif Defaults: 
Some keyboards may experience problems echoing "<" and ">" keys in 
DECterm unless a DECW$XDEFAULTS.DAT file is present in the user's 
SYS$LOGIN directory.  This file must contain at least one nonblank line. 
 
 
======================================================================= 
4.0  SERIAL LINE - SUPPORTED HOSTS 
=======================================================================
eXcursion serial line support is provided by XRemote technology by NCD 
Corporation.  The following is the list of operating systems that are 
supported for XRemote. 
 
Digital Unix/Alpha         V3.0 
Digital Ultrix/MIPS        V4.3 
VMS/Alpha                  V6.1 
VMS/VAX                    V5.5-2 
 
AIX                        V3.2 
HP  800                    V8.0 
Motorola 880x0	 
SUN                        V3.2 
 
======================================================================= 
5.0  HEBREW-SPECIFIC INFORMATION 
======================================================================= 
This section discusses the following: 
 
    o	Hebrew features 
 
    o	General Installation Information 
 
    o	Post-installation tasks 
 
    o	Use of the Keyboard Manager (KM) 
  
5.1 Hebrew Features: 
 
In order to support the hebrew requirements this version of eXcursion 
contains: 
  
- additional Hebrew Fonts (VGA and High resolution) 
 
- Cut and Paste between X-Window and MS-Windows/Hebrew supporting 
Compound strings on X-Window (for full support a prerequisite is to have 
an Hebrew version of MS-Windows) 
 
- additional Keymap files to support Hebrew characters to be used with 
KM (keyboard manager). 
 
5.2 General 
 
To use eXcursion with Hebrew X Window you have to: 
  
1) Install the English language version of eXcursion 2.0 
 
2) Select the Hebrew language in the Display page of eXcursion  2.0 
Control Panel 
  
3) Define the Hebrew keyboard as the secondary keyboard (English as 
primary) in the keyboard page of eXcursion 2.0 Control Panel 
 
5.3 Post-Installation 
 
After installing eXcursion and before starting it you will have to do 
the following : 
 
If your application controls the keyboard by switching keyboard 
language, you will have to use a remote keyboard manager (KM). 
 
You will have to start the application decw$km on a OpenVMS or Ultrix 
machine. 
 
The switching mechanism between keyboard of different types (LK250/101-
102 enhanced ) IS NOT SUPPORTED. 
 
5.4 Use of KM 
 
You can use the keyboard manager KM from the platform of your choice 
(OpenVMS or Ultrix). Note that you only need to run it once and from one 
platform even if you start clients on both platforms. In order to use KM 
properly you will have to do the following : 
 
1)copy the files *.key from the directory 
drive:\win32app\xcursion\keysyms, to the OpenVMS or Ultrix machine where 
you will run KM. You will have to copy those files in the directory 
containing the OpenVMS or Ultrix keymaps files, and rename them to 
change: 
 
- the file extension to decw$keymap for OpenVMS or decw_keymap for 
Ultrix. 
- the name to a format: language-keyboard. 
 
For instance on OpenVMS : 
 
rename ISENHDIL.KEY to hebrew-isenhd.decw$keymap 
rename ISENHDUS.KEY to english-isenhd.decw$keymap 
rename ISENHIIL.KEY to hebrew-isenhi.decw$keymap 
rename ISENHIUS.KEY to english-isenhi.decw$keymap 
rename LK250DIL.KEY to hebrew-lk250d.decw$keymap 
rename LK250DUS.KEY to english-lk250d.decw$keymap 
rename LK250IIL.KEY to hebrew-lk250i.decw$keymap 
rename LK250IUS.KEY to english-lk250i.decw$keymap 
 
2) Modify the file DECW$KM.DAT (for OpenVMS) or DXkm (for Ultrix) in 
your login directory, to reflect the keyboard you use, and the key 
sequence of your choice for the keymap switching. 
 
For instance: 
 
!DECW$KM.DAT 
km.mode:        0 
km.primaryKeyboard:     english-lk250d 
km.secondaryKeyboard:   hebrew-lk250d 
km.stickyWindow:        TRUE 
km.grabKey:     Multi_key 
km.modifierKey: Control_L 
 
In this example we are using the LK250 keyboard. The Multi_key is the 
Hebrew key, which appears on the Hebrew LK250 keyboard. The Ctrl/Hebrew 
key combination will switch the keyboard language. 
 
For an Industry Standard keyboard, the Multi_key does not exist. The 
user should define his own key combination for keyboard switching. For 
example: 
 
!DECW$KM.DAT 
km.mode:        0 
km.primaryKeyboard:     english-lk250d 
km.secondaryKeyboard:   hebrew-lk250d 
km.stickyWindow:        FALSE 
km.grabKey:     F2 
km.modifierKey: Control_L 
 
 
Note that for Industry Standard, grabKey must be defined explicitly in 
order for KM to work properly. 
 
3) You can now start KM from eXcursion as a normal application. Note 
that you can even set up KM to be started automatically when starting 
eXcursion. 
 
IMPORTANT: If you use KM, it is recommended to select in the eXcursion 
keyboard dialog box the US industry standard keyboard. 
 
5.5 KNOWN PROBLEMS AND LIMITATIONS 
 
1) KM. (Keyboard manager) 
------ 
 
You cannot use all the possible keys for keyboard switching with KM. For 
example, the Ctrl/Shift combination doesn't work. The Alt key is 
intercepted by MSwindows and thus cannot be used by KM for keyboard 
switching. 
 
2) Industry standard keyboard and F17 function key 
-------------------------------------------------- 
 
In order to support the use of the F17 function key on a Industry 
standard keyboard (F17 doesn't exist on those keyboards), one of the 
function keys (F7 for instance) has to be remapped as F17 in the 
corresponding keysym file. 
 
Note that for compatibility with some software you will need to assigned 
the remapped key (F7) to an nonexistant scancode (6A). Note also that 
the remapping of F17 to the F7 key is already done on the keymaps files 
used with KM. 
 
*4) LK250 keyboards and F17 function key 
--------------------------------------- 
 
As the F17 key (scan code) is used to change the mode of the keyboards 
LK250 (between Industry standard mode to Digital LK250 mode), the keysym 
F17 should also be moved to the F7 key (in order to avoid conflict 
between the use of F17 for changing the mode of the keyboard and the use 
of F17 in Windows Motif for switching between left-to-right and right-
to-left). You can change this mapping by modifying and recompiling the 
LK250DIL.txt, and LK250DUS.txt files (or modifying the 
hebrew_lk250d.decw$keymap and t 
 
======================================================================= 
6.0  COMMAND LINE SWITCHES 
======================================================================= 
 
-ac                    disable access control restrictions 
-audit int             set audit trail level 
-auth string           select authorization file 
bc                     enable bug compatibility 
-bs                    disable any backing store support 
-co string             color database file 
-dpi int               screen resolution in dots per inch 
-deferglyphs [none|all|16] defer loading of [no|all|16-bit] glyphs 
-fc string             cursor font 
-fn string             default font name 
-fp string             default font path 
-help                  prints message with these options 
-I                     ignore all remaining arguments 
-r                     turns off auto-repeat 
r                      turns on auto-repeat  
-su                    disable any save under support 
-terminate             terminate at server reset 
-to #                  connection time out 
-tst                   disable testing extensions 
-wm                    WhenMapped default backing-store 
-query host-name       contact named host for XDMCP 
-broadcast             broadcast for XDMCP 
-indirect host-name    contact named host for indirect XDMCP 
-port port-num         UDP port number to send messages to 
-once                  Terminate server after one session 
-class display-class   specify display class to send in manage 
-cookie xdm-auth-bits  specify the magic cookie for XDMCP 
-displayID display-id  manufacturer display ID for request 
-trap[=trapfile]       save requests to file 
-replay[=replayfile]   replay saved requests from file 
 
 
Trap/Replay 
The Trap/Replay feature is a way to capture all X requests from a 
session and play them back at a later time.  We had this feature in 
version 1.2, but we have made it much more robust for version 2.0.  To 
use this feature start the X server with the command line "wxserver.exe 
-trap".  All X requests for this session are then captured.  To play 
back the session start the server with the command line "wxserver.exe -
replay". Optionally trap files can be specified by using the switches "-
trap=file.req" and "-r 
 
======================================================================= 
7.0  Undocumented Configuration SWITCHES 
======================================================================= 
HighPriority: specifies the scheduling priority given to the X server 
              0 = normal priority, 1 = high priority 
              This switch is for WNT only.  The default value is 1. 
 
ActionAtReset: specifies the action of the X server when the last client 
disconnects. 
               0=continue, 1=terminate, 2=reset 
               The default value is 0. 
 
GDIBatchLimit: specifies the Windows GDI batch limit. 
               0 - sets the default Windows GDI batch limit 
               n (n > 0) sets the GDI batch limit to the specified 
               value. 
               If not specified, the server sets this to 30. 
 

