    What's New in Remote Desktop 32 v2.1.2
      Copyright 1994-1997 by McAfee, Inc.
              All Rights Reserved.


Thank you for using McAfee's Remote Desktop 32. 
This What's New file contains important information 
regarding the current version of this product. It is 
highly recommended that you read the entire document.

McAfee welcomes your comments and suggestions. Please 
use the information provided in this file to contact us.

___________________
WHAT'S IN THIS FILE

- New Features
- Important Notes
- Known Issues
- Additional Information
- Documentation
- Contact McAfee
- Bug Report Format


____________
NEW FEATURES

1.  Full screen MS DOS box support for Windows NT 4.0 and Windows 95.
2.  16 bit Remote Control Viewer integration allows connections to
    Windows 3.11 and DOS.
3.  Mouse position feedback synchronizes the controller's mouse cursor
    with the agent's.
4.  Mouse cursor shape feedback synchronizes the agents cursorshape on
    the controller computer.
5.  "Connect As" functionality enables the local user to connect as a
    different user than the currently logged in.
6.  Faster updates on dragging and resizing if connected to a Win95 agent.
7.  NT compatible security configuration on Windows 95 computers.
8.  User definable auto logoff after closing connections.
9.  Agent may be configured which protocols it is waiting for connections.
10. Improved 64k and True color mode significantly speeds up Remote Desktop
    sessions.
11. Selectable default boot operating system for the agent machine.

_______________
IMPORTANT NOTES

1.  Please deinstall any previous Remote Desktop 2.12 build, before
    installing this 2.12 version.

2.  Remotely rebooting a Windows NT system will not work, if the currently
    logged on user on the remote machine does not have the user right 
    "Shut down the system". This is a Windows NT security requirement.

3.  Controlling a Windows 95 machine with the 16 bit Host installed is
    not recommended, as the session window may not always be notified of
    remote machine's changes. Installing the 16 bit Viewer on a Controller's
    machine however does not affect Remote Desktop 32.

____________
KNOWN ISSUES

1.  If the agent is installed on a remote computer, Setup evaluates default
    security configuration files locally and is not able to resolve local 
    users of the remote machine. Setup ignores them, if this is the case.

2.  No mouse support for Windows 95/Windows NT full screen DOS console.

3.  Remotely installing the agent on an NT 3.51 machine may cause wrong
    links in the Remote Desktop program group, if the path contains
    one or more blanks.

4.  If your remote Windows 95 computer runs 16 colors, mouse cursor shape
    feedback will not work.

5.  If the controller computer's screen resolution is bigger than the remote 
    computer's screen resolution, the right side of the controller window
    displays White. This does not impact any of the display or functionality
    of the remote window.

6.  Controlling your own computer gives you a number of repetitive windows--
    no further impact.

7.  In order to increase performance of Remote Desktop connections cursor
    shapes are always transmitted black and white.
 
8.  If you are connecting from a Windows 95 controller and you are using 
    TCP/IP as transport protocol you may get an error message when using 
    the Remote Desktop File transfer option. If you receive this error, 
    launch Windows Explorer manually.

9.  If you send a CTRL-ALT-DEL sequence from the controller to an NT agent
    instead of using the toolbar, you may not be able to enter keystrokes 
    on the agent because the CTRL+ALT+DEL key sequence will not be completely
    cleared. If this occurs, press the CTRL and ALT keys individually
    on the agent or the controller during an active session to reset the key 
    buffers.

10. If your controller machine has 256 colors and you have multiple agent 
    connections, the colors of the remote computers' desktops will be transmitted
    correctly, however non-active connection windows may display the wrong colors
    because of color management limitations in the operating system.
   
11. To avoid system conflicts, make sure that no other remote control package is 
    installed on the computer you are installing the Remote Desktop Agent 
    component.

12. The controller of Remote Desktop 2.12 is compatible with earlier versions of 
    Remote Desktop (2.02, 2.10, 2.11); however maximum performance is available
    only by updating the agent to version 2.12. 

13. Enabling the PowerGDI option or using the DeskNav utility of MGA PowerDesk 
    Drivers 3.20.055W on Win 95 machines may cause some display update
    problems on the Remote Desktop controller.

14. Renderings made by applications using OpenGL or Direct Draw (including
    graphic drivers) may be visible on the agent's side only. The same
    problem arises with Direct Draw graphic drivers, which may also result
    in inaccurately transmitted bitmaps. To avoid such complications, you
    may choose non Direct Draw graphic drivers on the remote computer.

15. When you install a different display adapter or change the display
    driver on a Windows NT 4.0 agent, you need to reinstall the Remote
    Desktop Agent to re-establish the GDI Hooking. This is possible by 
    reinstalling the Remote Desktop agent or launching the agent manually.



______________________
ADDITIONAL INFORMATION

McAfee Remote Desktop 32 uses the following ports for each protocol:

Protocol      Ports

IPX/SPX       4044, 4045
TCP/IP        5044, 5045
NetBios       144, 145


How to connect via IPX/SPX (Novell):
------------------------------------

Remote Desktop 2.12 is also compatible with Novell Netware Client for
NT4.0/Win95 and Microsoft Netware Client for NT3.51/NT4.0/Win95.

When opening the Remote Desktop 'Connect ...' dialog, you need to
specify which computer you want to connect to. 

There are two ways to specify the agent computer:
* by the remote machine's name (= NETBIOS identification)
* by the remote machine's IPX/SPX address (leaded by ~).
  The following format is used: ~xxxxxxxxyyyyyyyyyyyy
  (x = network address, y = node address)
  Example: ~0000002298ab320012a0

Running an environment without NT domain controller we recommend 
using IPX numbers for identifying the remote computer. Also we 
recommend not using currently logged on user credentials instead 
explicitely specifying username / password. Deselecting the item 
'Use current user credentials' allows you to explicitely specify 
different username/password. Please keep in mind, that you need 
to enter a valid Window NT user account that has proper permissions
controlling the remote computer (do not use Novell user names!).

You may use NETBIOS-names instead of IPX-adresses for connecting to 
NT4 agents. For supporting this you need to install the SAP-agent 
on your agent computer. You may install this service via the 
Network Neighborhood properties.


How to increase performance on Remote Desktop 32 connections:
-------------------------------------------------------------

1.  Setting the palette slider in the menu SETTINGS/OPTIONS/TRANSMISSION to
    the most left position transmits color palettes only initially and therefore
    reduces the amount of color information that needs to be transmitted.
    However some color inaccuracy may occur.
 
2.  If you are running high color modes on your agents, which carry a lot of
    color information you may reduce the amout of data transferred by using the
    option "Optimize Color Depth" in the menu SETTINGS/OPTIONS/COMPRESSION.
    This changes the display settings on the remote computer to 256 colors 
    when you establish of a connection and restores the display settings when
    end a connection.
 
3.  Any zoom factor different from 100% on displaying the connection window
    causes additional CPU-load on the controller.

4.  If you are running Remote Desktop via low speed connections, i.e. modem, 
    ISDN, you can select "Optimize for low speed" in the connection dialog. This 
    option scales any color depth on the remote computer to 16 colors for
    reducing transmission overhead. Additionally screen changes will be
    transmitted interlaced. You can specify additional optimization for slow
    speed connections in the menu SETTINGS-CUSTOMIZE-CONNECTIONS.


_____________
DOCUMENTATION

For more information, refer to the Remote Desktop 32
User's Guide, available from McAfee's BBS and FTP site.
This file is in Adobe Acrobat Portable Document Format
(.PDF) and can be viewed using Adobe Acrobat Reader.
This form of electronic documentation includes hypertext
links and easy navigation to assist you in finding
answers to questions about your McAfee product.

Adobe Acrobat Reader can be downloaded from the
World Wide Web at:

http://www.adobe.com/Acrobat/readstep.html

Remote Desktop 32 documentation can be downloaded 
from McAfee's BBS or the World Wide Web at:

http://www.McAfee.com or 205.227.129.97


______________
CONTACT McAFEE

* FOR GENERAL QUESTIONS, ORDERS, PROBLEMS, OR COMMENTS *

Contact McAfee's Customer Care department: 

1.  Call (408) 988-3832
    Monday-Friday, 6:00 A.M. - 6:00 P.M. Pacific time

2.  Fax (408) 970-9727
    24-hour, Group III fax 
		
3.  Fax-back automated response system (408) 988-3034
    24-hour fax

Send correspondence to any of the following McAfee
locations.

    McAfee Corporate Headquarters		
    2710 Walsh Avenue
    Santa Clara, CA 95051-0963

    McAfee East Coast Office					
    Jerral West Center
    766 Shrewsbury Avenue
    Tinton Falls, NJ 07724-3298

    McAfee Central Office			
    4099 McEwen, Suite 500
    Dallas, TX 75225

    McAfee Canada
    178 Main Street
    Unionville, Ontario
    Canada L2R 2G9

    McAfee Europe B.V.			
    Orlyplein 81 - Busitel 1		
    1043 DS Amsterdam				
    The Netherlands	 		

    McAfee (UK) Ltd.
    Hayley House, London Road
    Bracknell, Berkshire  RG12 2TH
    United Kingdom 

    McAfee France S.A.			
    50 rue de Londres				
    75008 Paris					
    France					

    McAfee Deutschland GmbH
    Industriestrasse 1
    D-82110 Germering
    Germany

Or, you can receive online assistance through any of the 
following resources:

1.  Bulletin Board System: (408) 988-4004
    24-hour US Robotics HST DS

2.  Internet e-mail: support@mcafee.com

3.  Internet FTP: ftp.mcafee.com or 205.227.129.134

4.  World Wide Web: http://www.mcafee.com or 205.227.129.97

5.  America Online: keyword MCAFEE

6.  CompuServe: GO MCAFEE

7.  The Microsoft Network: GO MCAFEE

Before contacting McAfee, please make note of the following 
information. When sending correspondence, please include 
the same details.

- Program name and version number
- Type and brand of your computer, hard drive, and any 
  peripherals
- Operating system type and version
- Network name, operating system, and version
- Contents of your AUTOEXEC.BAT, CONFIG.SYS, and 
  system LOGIN script
- Microsoft service pack, where applicable
- Network card installed, where applicable
- Modem manufacturer, model, and baud, where 
  applicable
- Relevant browsers/applications and version number,
  where applicable
- Problem
- Specific scenario where problem occurs
- Conditions required to reproduce problem
- Statement of whether problem is reproducible on demand
- Your contact information: voice, fax, and e-mail

Other general feedback is also appreciated.


* FOR ON-SITE TRAINING INFORMATION *
 
Contact McAfee Customer Service at (800) 338-8754.


* FOR PRODUCT UPGRADES *

To make it easier for you to receive and use McAfee's
products, we have established an Agents program to 
provide service, sales, and support for our products 
worldwide. For a listing of agents, see the file 
AGENTS.TXT, where applicable, or contact McAfee Customer
Service for agents near you.


_________________
BUG REPORT FORMAT

When submitting issues and problems regarding Remote Desktop 32, please use
the following format:


___________________
GENERAL INFORMATION

Reported by....................: (Name, address, and phone)
Date...........................:
Remote Desktop version.........:

______________________
CONTROLLER WORKSTATION

Processor, MHz, bus system.....:

Video adapter..................:
Display driver
(original, OEM, other)........:
Screen resolution, no of colors:

Operating system & version.....:
Installed service pack, version:

Installed protocols............:
Installed network clients......:
Domain/Workgroup, name.........:

_________________
AGENT WORKSTATION

Processor, MHz, bus system.....:

Video adapter..................:
Display driver
(original, OEM, other)........:
Screen resolution, no of colors:

Operating system & version.....:
Installed service pack, version:

Installed protocols............:
Installed network clients......:
Domain/Workgroup, name.........:
___________________________
REMOTE DESKTOP CONFIGURATION

Type of connection:
Modem ( )       ISDN ( )        LAN ( )         WAN ( )

Controller's protocol order
(Customize/Transports).......:

Content from controller's statusbar: 

Affected component:
Controller ( )  Agent ( )  Help ( )  Doc ( )  General ( )

Bug occurrence:
Local Machine ( )   Remote Machine ( )

Reproducable:
Yes ( )         No ( )
Steps for reproduction (1,2,3) :

________
SYNOPSIS 

(including report of error messages):
