            *********************************************************
            *****                                               *****
	    *****   eXceed/W & eXceed/Xpress Version 3.3.1	*****
            *****                                               *****
            *****  Information not Covered in the User's Guide  *****
	    *****		or Release Notes		*****
            *****                                               *****
            *********************************************************

	
============================================================================

Documentation Omissions/Corrections:
------------------------------------

For eXceed/Xpress users only
----------------------------

1) The settings dialog box now allows the following flow control settings:
hardware, XON/XOFF or None.  Previously eXceed/Xpress always used hardware 
flow control.  This is still the recommended setting.  If you are having 
difficulty configuring your modem, try setting flow control to None.  
XON/XOFF while supported is not recommended.

2) Modem connect detection is now configurable in the settings dialog box to
Carrier detect or Pattern.  Carrier detect requires a hardware signal which 
must be correctly provided by the modem.  Pattern waits for incoming data 
to match the specified pattern.

3) Some communications drivers may not support a baud rate of 14.4K.  If your
modem supports 14.4K and you cannot connect with this setting, try 19.2K.
Some modems will automatically switch down to 14.4K.  If this does not work,
select 9600.

For additional information, consult the online help provided for the settings
dialog box.


General information
-------------------

1) eXceed/W 3.3 provides a 32-bit and a 16-bit X server.  If your PC is a
386 or better and Windows is running in 386 Enhanced Mode, the 32-bit server
runs by default.  With certain graphics-intensive clients the 16-bit server
may outperform the 32-bit server.  If you wish to force use of the 16-bit 
server, consult the eXceed/W server help topic "How To: Force use of the
16-bit X Server".

2) The Launch Pad window "Arrange" functions (such as ArrangeHorz, 
ArrangeVert, Cascade and Stack) are virtual desktop aware (ie. these 
functions will not arrange the virtual desktop window or any window that is
currently off-screen).  As well a "Gather" function has been added to Launch
Pad which gathers all off-screen windows and stacks them in the upper 
left-hand corner of your display when invoked.

3) The release notes incorrectly document the following aspects of the 
Virtual Desktop facility in Launch Pad: 

Virtual Screen Representation - the area of the screen that is currently 
displayed is represented by a dotted box in the virtual desktop.  This box
is always topmost so that it can be easily seen at all times.

Virtual Desktop Colors - the virtual desktop window background is white; 
an inactive virtual window is filled with light gray; virtual windows
are framed using the Windows window frame color; active virtual windows
are filled with the Windows active title bar color.

For a description of the options available from the Options item on 
the Virtual Desktop's Control menu consult Launch Pad help.

4) Support for the Microdyne Inc. EXOS Net Station TCP/IP transport 
Version 3.7 or higher has been added.  For installation and configuration 
information consult transport help which can be viewed by double-clicking on
the Transports icon in Xconfig/W.

5) Note that the Version 3.3 of Hummingbird's eXtend product documents a 
means of interfacing Hummingbird X servers to non standard devices and TSRs.

============================================================================

Mouse erratic problem in Windows 3.0/3.1 386 Enhanced Mode:
-----------------------------------------------------------

Windows 3.0/3.1 has a problem in standard mode and 386 enhanced mode where 
the mouse suddenly begins to behave erratically under certain circumstances
on some systems.  Microsoft states the problem can be solved on a case by 
case basis and is not directly related to Windows or Microsoft's mouse 
drivers, but is the result of external factors.

To solve the problem if it occurs using a Logitech Series 9 mouse,
Microsoft suggests loading Logitech's DOS based mouse driver in either 
your AUTOEXEC.BAT or CONFIG.SYS.

To solve the problem if it occurs on IBM PS/2s, Microsoft suggests using 
the /m:2 or /m:ps2 parameter on your HIMEM.SYS command line in your 
CONFIG.SYS.  If this does not solve the problem, try using a serial port
mouse instead of the bus mouse port or obtain an add-in bus mouse board and
attach the mouse to the add-in board's port instead of the motherboard mouse
port or upgrade the keyboard ROM BIOS in your PS/2.

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