           
            ==============================================
           |                                              |
           | Release Notes for                            |
           |                                              |
           |   eXcursion for Windows, Version 1.2         |
           |   eXcursion for Windows NT, Version 1.2      |
           |        January 1994                          |
           |                                              |
           |                                              |
           |                                              |
           ================================================



These Release Notes contain important information that is not
included in the eXcursion Installation and Reference Guide or
in eXcursion online Help. These notes pertain to Version 1.2
of eXcursion for Windows and eXcursion for Windows NT.

These notes cover the following topics:

    1 - New Features in this release

    2 - Installation of eXcursion

    3 - Known Problems and Limitations

        A. eXcursion for Windows NT

        B. eXcursion for Windows NT and eXcursion for Windows

    4 - Hebrew specific information



          
          ====================================================== 
          1 - NEW FEATURES IN EXCURSION, VERSION 1.2
          ======================================================

New features in eXcursion, Version 1.2, include:

   o Dual-network software support

         With Version 1.2 of eXcursion for Windows, you can
         simultaneously run X applications over both DECnet and
         TCP/IP.

   o DECnet support (eXcursion for Windows NT)

         eXcursion for Windows NT now supports DECnet as will be shipped
         with PATHWORKS for Windows NT, Version 4.1.  PATHWORKS for
         Windows NT is currently in external field test.

   o Support for additional network software (eXcursion for Windows)

         This release of eXcursion for Windows supports
         many more third party TCP/IP versions.  In particular, this
         version supports Windows-socket-compliant TCP/IPs, so any
         TCP/IP stack that supports Winsock will now work with eXcursion
         for Windows.

   o Hebrew fonts

         Hebrew fonts are available on the CD-ROM distribution media.
         Both 75- and 100-dpi collections are included.  

   o Internationalization/Localization

         You can display the eXcursion user interface, online help,
         and messages in the following languages:

             Danish
             Dutch
             English
             Finnish
             French
             German
             Italian
             Norwegian
             Spanish
             Swedish

	In addition, Hebrew X applications are supported (though the eXcursion
        user interface is displayed in	English)

   o Motif language property

         A language selection has been added to the Session dialog
         box.  The language you select here not only determines the
         language of the eXcursion user interface, but it also sets
         the Motif language property on the root window.  Motif
         applications that check for the language property of the
         root window will automatically be displayed in the specified
         language. (Not all Motif applications check this setting.)

   o Dynamic keyboard mapping changes

         Changes to the key definition file no longer require that you
         restart eXcursion.

   o Secondary key definition file

         You can specify two key definition files. When enabled,
         the Ctrl/Shift key combination lets you switch between
         the two key definition files. For example, you can
         switch between key definition files mapped to two different
         languages.

        
   o Windows system key handling

         eXcursion now lets you select the behavior of the Windows
         special system keys (Alt/Space and Alt/Function keys) when
         X applications have the focus.

   o Window creation

         You can set an option in the user profile (DelayWindowCreation)
         to change the behavior of eXcursion's allocation of Windows window
         structures.  This entry in the profile can have the following
         values only:

             0 - Windows window structures are allocated when top level
                 X windows are created.

             1 - Windows window structures are allocated when top level
                 X windows are first mapped.

         Setting this value to 1 will reduce the eXcursion's use of
         Windows resources.  The default value is 1.
         Note: there is no user interface in the eXcursion Control Panel
         for this option.

         Note: If you use eXcursion for Windows, the default file name
         for the User Profile is XCURSION.INI. If you use eXcursion
         for Windows NT, User Profile information is contained in your
         Windows Registry. The Registry location for eXcursion is:
         \HKEY_CURRENT_USERS\Software\DigitalEquipmentCorporation\eXcursion.

   o Process priority

         You can set an option in the user profile (HighPriority) to
         run eXcursion high priority.  The default value for this option
         is 0, or normal priority.  Any non-zero value causes eXcursion
	 to run at high priority.  Note: there is no user interface for
	 this option in the eXcursion Control Panel.
         
   o Sizeable Transient Windows

         An option in the user profile (Transients_Sizeable) lets you
         control whether or not "transient" windows are sizeable.
         Any value other than 0 enables them to be sizeable.
         The default value for this is 0.

         
           =========================================================
           2 - INSTALLATION OF EXCURSION, VERSION 1.2
           =========================================================

    o If you reinstall the eXcursion files after having run eXcursion you
      may encounter "locked" files during the installation.  It may be
      necessary to reboot and try again (or simply rename the locked files).

    o If you are running Windows in Enhanced mode and you are using the
      DECnet transport, eXcursion requires that the DECnet VKD (virtual
      device driver) is installed to ensure correct serial access to the
      underlying network.  Run Windows SETUP and select Pathworks as your
      network and it will install DECNET.386 and add it to the network=
      line in your SYSTEM.INI.  (Or you can perform these steps manually.)
     
    o If you are upgrading from a previous version of eXcursion, you
      can delete some files from your previous version of
      eXcursion.

      Fonts with Version 1.2 of eXcursion are contained in
      \XCURSION\FONTS\directory (for example, \XCURSON\FONTS\MIT).
      New fonts work with older versions of eXcursion. You can delete
      fonts in the following directories and then delete the directories:

	\XCURSION\FONTS100
	\XCURSION\FONTS75
	\XCURSION\FONTSMIT
	\XUCRSION\FONTSOL

      You can delete the following Version 1.0 files located in the
      \XCURSION directory (they are now located in \XCURSION\WIN16 and
      \XCURSION\COMMON directories):

	XCURSION.EXE
	XCURSION.RGB
	XCURSION.HLP
	SETUP.EXE
	SETUP.HLP
	SETUP.INF
	XREMOTE.EXE

      The following files currently reside in the \XCURSION\COMMON
      directory. You can delete the following files from the
      \XCURSION\platform, directory (for example, the \XCURSION\INTEL
      directory):

	R_NOTES.TXT
	SETUP.HLP
	SETUP.INF
	XCURSION.RGB
	XCURSION.HLP
	XFC.EXE

      With Version 1.2, files that were previously placed in
      the \XCURSION\INTEL directory are now placed in the
      \XCURSION\X86 directory to take advantage of the
      %PROCESSOR-ARCHITECTURE% environment variable. You can
      delete the \XCURSION\INTEL directory and any files
      located in it.                 


                    ==================================
                    3 - KNOWN PROBLEMS AND LIMITATIONS
                    ==================================


===================
X APPLICATION ICONS
===================

   o If you use eXcursion for Windows NT, only one X application
     icon can be put in the Startup program group.  To start more than
     one application you put the eXcursion Control Panel icon in the
     Startup group and choose "Run at eXcursion startup" in the Applications
     dialog box for those applications you wish to auto-start.

   o If you use eXcursion for Windows, the following characters cannot
     be used in the Description text box of the Add Icon To Program Manager
     dialog box: [ ] ( )

==========================
DRAWING TO THE ROOT WINDOW
==========================

   o If you use eXcursion for Windows NT, root window drawing has the
     following known problems:

         1. eXcursion does not capture mouse input to the root window.

         2. Expose events on the root window are not sent back to
            the X applications using the root window.


=======================
STARTING X APPLICATIONS
=======================

   Occasionally, conditions may occur in which the network software
   does not return a message for unsuccessful attempts to start an
   X application.

   If you are unable to start an X application and no message
   is displayed:

   o You may have reached the maximum number of links allowed.

     Check the Status box (accessed from the Help menu on the
     eXcursion Control Panel) to see how many links are in use.
     Close one or more applications to free up a link, or
     increase the number of maximum links allowed. (For information
     on increasing the number of maximum links, see the
     documentation for your network software.)

   o Ensure that the application startup information is correct.


=============
COLOR PALETTE 
=============

   Running a Windows or Windows NT application that uses colors
   from the System Palette interferes with the display of colors
   from X applications. This is because available color slots
   from the 256-color palette are being reserved and cannot be
   used by eXcursion.

   This is most noticeable when you have a 256-color Windows
   or X background pixmap displayed on your root window.
   The colors on the background pixmap display incorrectly if
   other color-allocating applications are running.



=============================
SUPPORT FOR X WINDOW MANAGERS
=============================

   o If you use a remote window manager, an X application and
     a Windows application may both appear to be active at the
     same time. In this case, the Windows application is the
     active window.

   o If you are running decw$winmgr (and possibly some other
     X window managers), Windows applications will always be
     concealed behind the X root window. This is the result of
     actions taken by the X window manager. Remember that X window
     managers do not know anything about a foreign (in this case,
     Microsoft Windows) windowing system and they act accordingly.


=============
COLOR SUPPORT
=============

   o eXcursion supports 4- and 8-bit color boards. 16- or 24-bit
     color boards are unsupported.

   o Monochrome StaticGray is supported; there is no support
     for GrayScale.


========================
TRUE TYPE FONT SELECTION
========================

   eXcursion will not display fonts correctly if the user has
   selected "Show Only True Type Fonts" from the Windows Control
   Panel. Users should instead select "Enable True Type Fonts".
   True Type font support will be added to eXcursion in a future
   version.


========================
DECTERM DISPLAY PROBLEMS
========================

   If while you are trying to start X applications from a VMS
   DECterm session created by eXcursion, you receive one of the
   following errors:

     Can't Open Display
     %SYSTEM-W-NOSUCHDEV, no such device available

   You should add the following DCL commands to the beginning of
   your LOGIN.COM:

     $ 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.


=================================================
STARTING X APPLICATIONS ON VMS HOSTS USING TCP/IP
=================================================

   o 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,
     due to a limitation in UCX, eXcursion cannot know the cause of
     the failure.  In this case you will get the following error
     message from eXcursion:

         TCP/IP Remote Startup Error
         REXEC session aborted by node: <node>

     We recommend that you check the value and increase it if
     necessary.  To display the current UCX REXEC configuration,
     enter the following command in your account on the UCX host:

         $ UCX SHOW SERVICE REXEC /FULL


   o For DEC TCP/IP (UCX) Version 2.0, repeated login failures
     will trigger VMS "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"

   o 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.

   o For DEC TCP/IP (UCX) Version 3.0, if you receive the following
     message from OPCOM on the VMS 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

   o For Wollongong WIN/TCP Version 5.2 for VMS, you must copy the
     WOLL.COM file to the VMS host in addition to the PCX.COM file.
     Follow the instructions at the beginning of the WOLL.COM file.

   o For Multinet Version 3.1, you must copy the MN.COM file to the
     VMS host in addition to the PCX.COM file. Follow the
     instructions at the beginning of the MN.COM file.

   o For Process Software TCPware Version 3.1-3 for OpenVMS, you must
     modify the PCX$SERVER.COM file.  The line

             /transport=tcpip

     must be changed to

             /transport=tcpware


======================================================
REDIRECTION OF 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 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 power off or reboot your PC without
   first exiting eXcursion or otherwise stopping the
   X applications, the processes may continue to use process
   space on the UNIX host and must be deleted manually.
   (For DECnet, this process deletion is handled automatically.)



===============================================================
REQUIRED 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.


    
-----------------------------------------------------------
    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.


======================
UNSUPPORTED X REQUESTS
======================

The following X requests are ignored:

   o RecolorCursor

   o Screen Saver requests

   o Plane Mask functionality is not supported with some
     combinations of raster operations and graphics functions.

     Plane Mask functionality does work with PolyFillRectangle,
     solid fill style.


-----------------------------------------------------------------------------
		======================================
		    4 - Hebrew specific information
		======================================



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


- additional Keymap files to support Hebrew characters to be used with KM 
(keyboard manager).




Post-Installation
=================

After installing eXcursion/IL and before starting it you will have to do
the following :


1) If you have installed eXcursion on MS-Windows/Hebrew, type at the dos 
prompt,the following command :

  c:> markbidi -R   path\xcursion.exe

Where path represents the directory where eXcursion is installed.




2) 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 VMS or Ultrix machine.

The switching mechanism between keyboard of different types 
(LK250/101-102 enhanced ) IS NOT SUPPORTED. 


3) When using the MS-windows/hebrew local window manager, you may encount 
problems with titles in the reverse order . To fix this problem you can enable 
a routine of conversion by setting the field after the keyword 
"Reverse_Hebrew_titles=" to 1 in xcursion.ini.
Note that this solution, doesn't solve all the title problems. The workaround 
solving all those problems is to use a remote Motif Window Manager.  



Use of KM
==========

You can use the keyboard manager KM from the platform of your choice VMS or 
Ultrix.Note that you only need to run it once and from one platform even if 
you start client on both platforms.
In order to use KM properly you will have to do the following :

1)copy the files *.key from the directory c:\xcursion\remote, to the VMS or 
Ultrix machine where you will run KM. You will have to copy those files in the 
directory containing the VMS or Ultrix keymaps files, and rename them to change:

- the file extension to decw$keymap for VMS or decw_keymap for Ultrix.
- the name to a format: language-keyboard.

For instance on VMS :

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 VMS) 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 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 .



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 thus can not 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 key (F7 for 
instance) has to be remapped as F17 in the corresponding keysym file .

Note that for compatibility with some softwares you will need to assigned the 
remapped key (F7) to an inexistant scancode (6A).
Note also that the remapping of F17 on 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 the 
english_lk250d.decw$keymap if you use KM).
Note that for compatibility with some softwares the F7 should be kept but
assigned to a inexistant scancode (6A)



