****************************************************************************

		      eXceed/NT Version 3.3.4 (Intel)
                          
                 Information not Covered in the User's Guide

****************************************************************************


1)  SETUP

After installation, if you have a copy of the eXceed/NT XDK installed as 
well, then you must make sure that you put the latest XLOCAL.DLL and 
XPORT.DLL (which can be found in the HOME directories of eXceed/NT and the
eXceed/NT XDK) in a directory on the path.  These should be the only
XLOCAL.DLL and XPORT.DLL files on your machine.  We suggest renaming
the originals in your HOME directories for backup purposes.


INSTALLATION PROCEDURE FOR SYSTEM ADMINISTRATORS

If you are a member of the Administrators Group, you can install eXceed/NT
in any of the following ways:


i.  MULTIPLE USERS SHARE ONE USER DIRECTORY

    If you would like multiple users to share one USER directory and one
    copy of the configuration files, perform a PERSONAL installation
    and select "Yes" when given the option to share USER files for users 
    that have not performed a PERSONAL/USER install on the machine. 

    NOTE:  If the shared USER directory is on an NTFS partition, you may
    need to set permissions to allow those users sharing the directory
    appropriate access.  

    Those users who would like their own unique USER directory and
    configuration files must perform their own USER installation.  
 
    If as system administrator, you would like your own USER directory and
    configuration files then you must also perform a USER installation
    and select "No" when given the option to share USER files and provide
    a unique USER directory name.


ii. MULTIPLE USERS ON A SINGLE MACHINE

    If you would like multiple users on a single machine to have individual
    USER directories and configuration files, perform a SHARED install 
    and have every user perform a USER install.


iii.INSTALLING FOR PERSONAL USE

    If you would like to install the product for your own personal use,
    perform a PERSONAL install and select "No" when given the option
    to share USER files for users that have not performed a PERSONAL/USER
    install on the machine.


2)  SERVER

TERMINATING CLIENTS

If you are running eXceed/NT in Multiple Window Mode and terminate
a client by using the End Task button in the Windows NT Task List, it will
terminate ALL clients and the server.  To terminate a single client, use
the method you would normally use to terminate that client or select Close
from the Client's Control Menu.

USER LEVEL SECURITY

Release 3.3.4 now supports security at the user level (as opposed to the host
level) without using XDMCP.

User level security is controlled through an .Xauthority file that is read
each time the server is started or reset.

To enable user level security:
	
	(i)  Create an .Xauthority file using a host based xauth utility.
	(ii) Copy this file to your USER directory (by default,
	     c:\exceednt\user) as XAUTH.

To disable host based security fallback, place a /SECURITY line in the 
Access Database.

COPY/PASTE MENU ITEMS

"Copy X Selection to Clipboard" and "Paste X Selection from Clipboard" menu 
items have been added below the "Edit" popup menu on the client window system 
menu in Multiple Window Mode.  These menu items have been duplicated from the 
"Edit" popup menu for convenience of access.


3)  XCONFIG

The Font Database (Font Settings, Font Database button) dialog box
now includes the CHANGE ALL button.  The Change All button displays 
the Change All Font Directories/Servers dialog box.  This dialog box allows
you to search for all font directories/servers with a specific prefix (path)
pattern and replace the pattern with another pattern.  It also allows you
to change the Status (Load, Keep or Inactive) or Match Physical Font Name
setting.  For more information, see Xconfig's on-line help.


4)  LAUNCH PAD

Launch Pad's Virtual Desktop facility is not able to track activity in a
protected subsystem window.  For example, when a command prompt window in 
windowed mode is sized, the Virtual Desktop window does not reflect the change.  
Presently, command prompt windows that are running Posix, OS/2, DOS or NT
console applications cannot be tracked by Launch Pad.  Essentially, Launch
Pad cannot track any command prompt window.

Launch Pad is unable to process button events when the focus is switched to and
from a protected subsystem window.  For example, if the shift plus left mouse
button combination brings up a menu and this combination is toggled while in
a command prompt window, Launch Pad will not be able to bring up the menu.
Similarly, if the shift key is depressed while a command prompt window has the
focus and you then press the left mouse button on the desktop, the shift
action is not seen by Launch Pad and consequently the menu will not pop up.  To
bring up the menu you will have to repeat the shift button press combination
on the desktop.


========================= END OF DOCUMENT ==================================
