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

			  eXceed/NT Version 3.3.3

                 Information not Covered in the User's Guide

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

1)  Setup

Version 3.3.3 now uses the NT registry database and no longer uses the
WIN.INI file.  This means that users of previous releases of eXceed/NT
cannot perform an update intallation, all users must perform a COMPLETE
installation.

If you are upgrading from an earlier release, you may remove the [EXCEEDNT]
section from your WIN.INI file.

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

3)  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 ==================================
