README.TXT
Lotus cc:Mail Desktop for MS-DOS Release 4.02

The "cc:Mail Desktop for MS-DOS Release 4.02" contains important information 
that is not described in the "cc:Mail Administrative Utilities Administrator's 
Manual" and "cc:Mail for MS-DOS, Version 4.0, User's Guide."  

   Table of Contents
   ------------------------------------------

    1.  The INSTALL program and ccmail.ini
    2.  The Third-Party Catalog
    3.  Explaining TSRMAIL Notes
    4.  Integrating Applications
    5.  The Color Palettes
    6.  Explaining Dynamic Connections 
    7.  The 3270 Emulators
    8.  Documentation Updates 
    9.  Resolving Problems in Release 4.02 
   10.  Admin Utilities Release 5.10

----------------------------------------------------------------------------

1.  The INSTALL program and ccmail.ini

    If the INSTALL program detects an existing ccmail.ini file during the  
    installation, the existing ccmail.ini file is renamed to ccmail.bak
    and a new ccmail.ini file is created.  Any existing ccmail.bak files 
    are overwritten.

2.  The Third-Party Catalog

    This is a third-party software catalog, located on a separate 
    disk, which is included in the Lotus cc:Mail Desktop for MS-DOS package.  
    
    This catalog is a list of third-party applications that work with or 
    in conjunction with cc:Mail products.  The catalog is in a cc:Mail 
    archive format. 
    
    Copy this file from the floppy disk and move it to a bulletin board 
    in your post office, so that other cc:Mail users can access it.

3.  Explaining TSRMAIL Notes

    Expanded-Memory Usage

     The TSRMAIL program resides in conventional memory; this is the default.  
     When you use a keyboard shortcut to select MAIL, TSRMAIL swaps memory 
     to accommodate MAIL.  TSRMAIL first swaps to EMS.  If EMS is not 
     available or not sufficient, TSRMAIL writes the memory image to disk.
  
     The default is not the most efficient method for using memory.  
     To use the minimum conventional memory, use the /EMS option to move 
     most of the resident program into the expanded memory. This method 
     only allows a very small portion of the conventional memory to be used.

     The disadvantage of using the /EMS option is that it may be 
     incompatible with some memory managers or applications. This can cause 
     the system to lock up.  An example of a conflict is QEMM, Version 6.0, 
     with the STEALTH feature. Use the /EMS/ND option described 
     below (or in the default) to resolve this conflict.

     If your system does not work with the /EMS option, use the /EMS/ND 
     option.  The TSR program moves the code portion of the program
     into the expanded memory and allows the data portion to remain in 
     the conventional memory.  This allows TSRMAIL to function with 
     other programs.  The conventional memory that is used by /EMS/ND 
     is more than the /EMS option but less than the default.  If the  
     Novell EMS Workstation Shell (EMSNET) is detected, the /EMS/ND 
     option is automatically enabled.

     Memory Requirements for TSRMAIL

	Amount of Memory Required by the Resident Portion of TSRMAIL:

	+----------+-------------+-------------+------------+
	|          |   1 User    |  16 Users   |  EMS Used  |
	+----------+-------------+-------------+------------+
       
	| default  |  16 Kbytes  |  26 Kbytes  |  0 Kbytes  |    
	| /EMS/ND  |   8 Kbytes  |  17 Kbytes  | 32 Kbytes  |    
	| /EMS     |   1 Kbytes  |   1 Kbytes  | 32 Kbytes  |   
	+----------+-------------+-------------+------------+

     The EMS usage described above does not include the EMS that is used 
     to bring up the MAIL program. To prevent TRSMAIL from using 
     all the EMS memory, use the /NOEMS option.

     To bring up the MAIL program, TSRMAIL requires the following: 
     
     o  About 400 Kbytes of conventional memory (starting from where TSRMAIL 
	is loaded) 

     o  A swapping space of about 400 Kbytes, either in expanded memory,
	or on disk.

 Problems that have been resolved in Release 4.02

     o  Previous releases of TSRMAIL had problems with changing the
        video-screen mode. This problem has been resolved in this release. 
	
     o  Previous releases would lock with WordPerfect and
	PC-Docs.  This problem has been resolved in this release.
	
     o  Previous releases of TSRMAIL had problems with the /S option 
	(Dynamic Network Connection).  This problem has been resolved in this 
	release, and TSRMAIL works with Dynamic Network Connections. 
	See "Dynamic-Connection Explanation" in this document for more 
	information.
	
     o  A switch has been added to TSRMAIL: MOD/xxx

	"xxx" can contain one or more of the integers and the  
	keywords listed below.  

        NOTE:  Any keyword can be used to replace its equivalent
        integer syntax, or vice versa.

		#   keyword     Feature
		-----------------------

		1   SABER       This resolves problems with Saber Menu 
				Systems spawning MAIL via TSRMAIL.
		
		2   SCANUMBS    This switch permits TSRMAIL to scan the UMBs 
				for its TSR signature. 
				
				This release includes code that does NOT 
				scan UMBs.  This feature was added to enable 
				TRSMAIL to operate with certain DTC SCSI 
				interfaces; however, this feature has NOT 
				been implemented in this release, but will be 
				enabled in a future release of TSRMAIL.  
				
				NOTE: If you want this feature and do not
				have conflicting hardware, contact Technical 
				Support.
		
		3   INT21       This switch resolves interacting problems 
				with Novell/FTP and TSRMAIL.  Novell changed 
				the INT21 3F call to correct incompatibility 
				problems with many popular-TSR type programs.  
				
				This switch also ensures that TRSMAIL operates 
				successfully with local area networking (LAN) 
				Workplace.  Using it disables TSRMAIL,
				in some instances, when DOS is busy.  
				
				NOTE: Do not use this switch if you  are
				running Version 4.11 or a later version of 
				LWP. 
				
		4   NETBIOS     This switch resolves "PO not found" errors in 
				heavily loaded network environments and allows 
				TSRMAIL to operate normally. 
				
		Examples:

		MOD/1              The Saber fix
		MOD/"1 INT21"      The Saber fix and the Novell/FTP fix
		MOD/"NETBIOS 1"    The NETBIOS fix and the Saber fix

		NOTE: You must quote combined options.
		      Options 2-4 are valid for MAIL.EXE. 
		      Option 1 is ignored.

		An error in the syntax results in the following error message:
		"Valid options are within the range 1 - 4"
    
    o   The algorithms for MAIL swapping (EMS as well as conventional memory)
	have been improved in this release.   

    o   The error "Post office file not found" has been resolved in this 
	release.

    o   Versions prior to this release scanned the UMB block when swapping.  
	This caused problems with some hardware configurations; therefore, 
	this release does not scan the UMB area.  If you want TRSMAIL to 
	scan the UMB block, contact Technical Support at 415-966-4900. 
	
    o   If you are in a graphics application when new messages arrive, you 
	are notified by tone only; not by the notification window  
	and tone.  
	
    o   Load SHARE.EXE, network drivers, or any memory manager programs PRIOR 
	to loading TSRMAIL. If you load these programs after TSRMAIL, 
	there is a risk that they will be swapped and lock up the system.  
	This also applies to any other TSR programs that you wish to use 
	when you're in the MAIL program.                                                

    o   Before running Microsoft Windows, either remove or disable 
	TSRMAIL (using the /SLEEP option).  DOS TSR programs do not run 
	well while Windows is running.

    o   In order to reduce the memory required by TSRMAIL, the full 
	notification algorithm (as implemented in NOTIFY) has been
	modified.  
	
	This means that even though TSRMAIL uses less code and has a
	very small memory requirement, it still provides most of the
	NOTIFY functions.  
	
	However, TSRMAIL recognizes that new mail is received, but it 
	does not always know if you have read your messages.  When you 
	are notified that you have a new message and you read your mail 
	using something other than TSRMAIL, TSRMAIL does not know that you 
	have read your mail.  It continues to notify you of unread messages.  
	
	This also applies if TSRMAIL is installed on more than one machine 
	for the same user.  To make sure that you know your current 
	mail-message status, run only one copy of TSRMAIL per user, or use 
        the more extensive capability of the NOTIFY program.

    o   Once you enter in MAIL, TSRMAIL is suspended; then, you
	cannot use keyboard shortcuts to invoke TSRMAIL again and 
	you are not notified of any new messages.  
    
    o   NOTE: If you exit cc:Mail by using another TSR program's 
	keyboard shortcut, you may cause problems for other cc:Mail users 
	in your post office.  If you access the mail database files
	from another TSR program, no other cc:Mail user on your post office 
	can access those locked files until you return to
	the mail program.  
	
	NOTE:   DOS is NOT a multi-tasking operating system.
		Do not use non-cc:mail keyboard shortcuts to exit mail.

    o   When you do not exclude certain areas of memory on your system, 
	problems with TSRMAIL and QEMM can occur.  When you add new 
	applications to your system, memory-address conflicts can occur 
	and cause problems. 
	
	NOTE: Make sure that you find all the memory usage on your system, 
	particularly after installing any new application. Make sure that you
	exclude these areas from certain memory-manager operations.  
	
	To determine the memory used in your system, run OPTIMIZE.
	Run the complete optimize process--not the abbreviated version-- 
	particularly after installing any new applications.  Do not  
	running QEMM in stealth mode.

    o   If you run a memory manager and forget to exclude the addresses for 
	the RAM buffer (if it has one) for your network interface card, 
	problems can occur. Here are examples for CONFIG.SYS:

		   DEVICE=QEMM386.EXE X=C800-C9FF NOEMS        
	or
		   DEVICE=EMM386.EXE X=C800-C9FF 2048 RAM

	See your MS-DOS manual for more details.

    o   If you use 386MAX for your memory manager, refer to the documentation
	provided by Qualitas for configuring memory, as each 386MAX 
	configuration is unique.

    o   If you are running multiple TSRs and find memory conflicts, 
	unload all the TSRs and run TSRMAIL.  The order in which you load 
	TSRs can affect the usage. Load your most used TSR last.

    o   Novell recommends that you do not load any TSR from a system login 
	script. Load TSR programs in a batch file or from 
	the command line.  See the Novell Netware Installation Manual, 
	Appendix A, for more information.

    o   If you encounter RTLink cache errors when trying to run TSRMAIL, 
	set the following environment variable:

	SET RTOVEXP=0

    o   Sometimes TSRMAIL has problems with old video hardware.  If problems 
	occur, set the following environment variable:

	SET RTOVCONV=100%,120

	The 120 can be increased until the problem is resolved.
	(For example,   140, 160,....)

    o   Do not load both TSRMAIL and NOTIFY; TSRMAIL has the NOTIFY
	functionality built in.  Use MAIL and NOTIFY together or 
	just use TSRMAIL.

    o   The "Memory Commander" can solve some memory conflicts with  
	TSRMAIL for users with a 386 or higher. For more information about
	this product, contact:

	Mike Mazi          
	V Communications
	4320 Stevens Creek Blvd. STE 275 
	San Jose, CA  95129    (408)296-4224

    o   The /REMIND command-line parameter is new in Release 4.0 and above.
	You can set this feature to remind you of unread mail. See 
	"cc: Mail for MS-DOS, Version 4.0 User's Guide" for more details.

    o   Although the /Files option is not supported by TSRMAIL, it can be 
	passed on the command line of TSRMAIL to the MAIL program.

4.  Integrating Applications

    For Application Integration to be most effective, use applications 
    that support the passing of a filename on the command line.  Once
    the proper statements are entered in the configuration file, Application
    Integration is a seamless operation.  

    Application Integration only works properly when the external 
    application accepts a filename as a command-line parameter.  
    Many Lotus applications, such as 1-2-3 and Freelance, work this way.

    Here is an example:

	[Application Integration]

	; This definition will not work
	wk3=c:\lotus\123.exe ^.wk3

	; This definition will work (as described below)
	wk3=c:\lotus\123.exe

    Lotus 1-2-3 does not accept the filename as a command-line parameter.  
    To correct this problem, complete the following steps:

    1. Go to the mail message with the attachment and select the attachment.

    2. Execute Application Integration.  (Shift-Enter)

    3. Using the application, open the attached file. This file is
       placed in the directory defined by the TEMP environment variable.
       When TEMP is not defined, you can find it in the directory where
       you're running MAIL.EXE.  
       
       NOTE:  When a file with the same name already exists, a temporary
       file is created with a new name.

    4. View, print, and make changes to the file.

    5. Save any changes made to the file under the same filename. 

    6. Exit the application and return to cc:Mail.
       
    Later releases of Lotus 1-2-3- support a filename on the command line 
    using the -w parameter.  For these versions of Lotus 1-2-3, use the 
    following Application Integration statement:

	[Application Integration]

	wk1=i:\apps\123r31 -w^.wk3

    Earlier versions of Lotus 1-2-3 automatically load either the AUTO123.WK1 
    or the AUTO123.WK3 file.  To operate Lotus 1-2-3, use the following 
    settings in the CCMAIL.INI file and the example batch file:

	[Application Integration]

	wk1=command /c c:\temp\go.bat ^.wk1 i:\apps\123r23\
	wk3=command /c c:\temp\go.bat ^.wk3 i:\apps\123r23\

    - go.bat is the name of the batch file.
    - i:\apps\123r23 is the directory where 1-2-3 is located.

    Make sure that GO.BAT contains the following information:

	@Echo Off
	Copy %1 %2AUTO123.WK1
	%2123.EXE
	Copy %2AUTO123.WK1 %1
	Del %2AUTO123.WK1
	Exit

    NOTE:  To call a batch file or an "internal" DOS command (Type, Copy,
    and Move) from Application Integration, use the following command 
    processor: 
    
	[Application Integration]
	; This shows an incorrect specification of a batch file
	txt = doit.bat ^.txt

    ----------------------------------------------------------------

	[Application Integration]
	; This shows how to specify a batch file correctly
	txt = command /c doit.bat ^.txt

5.  The Color Palettes

    The "cc:Mail for MS-DOS, Version 4.0, Administrator's" Guide incorrectly
    defines the name of the monochrome color palette as MONO.PAL.  The 
    correct name is either MONONEW.PAL or MONOOLD.PAL.  A third color VGA 
    palette, specified as DEVELOP.PAL, is also available. 

6.  Explaining Dynamic Connections

    The /S Dynamic-Connection option behaves in various ways depending
    on whether the computer is connected to the redirected device.
    
    If you are connected

	The computer breaks the connection and displays the message:
	"Connection cannot be established."  The application executes again 
	and successfully connects.  When the application terminates, the 
	connection also terminates.

    If you aren't connected

	The application executes again and successfully connects.  When
	the application terminates, the connection also terminates.

7.  The 3270 Emulators
        
    TSRMAIL 4.02 operates correctly with the following 3270 emulators:

	Emulator                Version
	--------                -------
	IBM PC/3270             3.0
	PCSupport/400 (5250)    2.0, Release 1.0 with DOS Extenders

8. Documentation Updates

    The "cc:Mail for MS-DOS, Version 4.0, User's Guide" has been updated 
    as follows:

    On Pg. 82, change the last sentence before "About the Mail
    Directory" to "The Message Log folder feature must be enabled by 
    your administrator before you can create it."

    On Pg. 99, in the first paragraph, change the third sentence to "You
    can have up to 200 folders.  Each folder can store up to 32,000
    messages; only the first 1600 messages are displayed."

    On Pg. 155, change item 2 to "You are prompted for your cc:Mail name 
    (and password, if you specified the /HEADINGS parameter), if you have 
    not already entered them."

    On Pg. 169, change Note to "Note  Graphics options will not appear on 
    the cc:Mail for MS-DOS menus if you have a VGA or EGA graphics adapter 
    and a monochrome monitor, or if you have a monochrome display adapter
    card (MDA)."

    On Pg. 198, change the error message "insufficient memory" to "cc:Mail 
    for MS-DOS requires 400 Kbytes of memory to run."

9. Resolving Problems in Release 4.02

    TSRMAIL.EXE

	This release corrects a number of problems and inconsistencies 
	that occurred when using TSRMAIL with other applications. 

	TSRMAIL includes the following revisions:

	o TSRMAIL can search for MAIL.EXE in the executable directory 
	  and in the environment-variable PATH statement.

	o TSRMAIL works correctly with a WordPerfect add-on product called
	  PC-Docs.

	o False-message notification has been corrected.

	o Restoring video to previous settings has been corrected.

	o Video problems occurred when applications called TSRMAIL while 
          in the 43/50-line video mode have been corrected.

	o 3270 emulators and TSRMAIL coexist better.  See "3270
	  Emulators" section above for specifics.

	o When TSRMAIL disconnects from the UNIX host, TSRMAIL reconnects 
	  using LAN Workplace.  See "TSRMAIL Notes" above.

	o TSRMAIL works correctly with Paradox 3.5.

	o TSRMAIL works correctly with QEMM 6.0 memory manager.  See 
	  "TSRMAIL Notes" above.

	o TSRMAIL /S, dynamic network connection has been corrected and
	  documented above.  See "TSRMAIL Notes" and "Dynamic-Connection 
	  Explanation" above.

	o TSRMAIL works correctly with Saber Menus.
	    
	o TSRMAIL works correctly with Xtree.

	o TSRMAIL takes corrective action when the computer hardware utilizes
	  a DTC SCSI hard-disk controller card.  See "TSRMAIL Notes" above.

    MAIL.EXE

	MAIL includes the following revisions:

	o Directory Fullview correctly displays ASCII characters above 127.

	o Writing to an ASCII file with a PostScript-printer selection strips
	  PostScript imbedded commands.

	o The cc:Mail editor now allows the insertion of "+" and "-" using
	  the keypad.

	o MAIL now handles a TEMP environment variable, which is longer than
	  24 characters.

	o MAIL now has correct screen deinitialization when exiting cc:Mail.

	o MAIL now recognizes monochrome display with graphics
	  capabilities.

	o Spell Replace correctly displays ASCII characters above 127.

	o Search and Search/Replace works correctly with ASCII characters
	  above 127.

	o MAIL displays the correct messages for the last Inbox or Folder
          message.

	o MAIL corrects for minimum-memory configurations while
	  viewing a fax on a monochrome monitor.

	o MAIL offers corrective action when the computer hardware utilizes
	  a DTC SCSI hard-disk controller card.  See "TSRMAIL Notes" above.

	o MAIL now prints faxes longer than 8.5 x 11.

	o MAIL displays an error message for a misspelled word at the
          end of a sentence. 

	o MAIL correctly displays information for a folder when you 
          use /REENTER.

	o MAIL correctly recognizes PS/2 monochrome monitors.

	o Press the ESC key to cancel importing a text file into a
          message.
	
	o MAIL allows the "," character in a folder or mailing-list name.

	o MAIL correctly displays deleted items in draft folder. 

	o MAIL displays a time-stamp on each edit of a draft message.

	o MAIL correctly displays a Help message after fax printing is
          complete.

	o Updated reconnection/resynch algorithm for File Access Protection
	  (FAP) occurs when automatic reconnect facility is utilized on 
          the LAN.

    NOTIFY.EXE

	NOTIFY includes the following revision

	o NOTIFY works correctly with QEMM 6.0 memory manager.  See 
	  "TSRMAIL Notes" above.

10. Admin Utilities Version 5.10

    The admin utilities consist of the following programs:

	ADMIN.EXE          ANALYZE.EXE
	CHKSTAT.EXE        DIALIN.EXE
	RECLAIM.EXE        CCSAVE.EXE
	NPODOWN.EXE

    These admin utilities have changed in many ways.  A new manual has been
    written.  See the "cc:Mail Administrative Utilities Administrator's 
    Manual" for details.

    Caution:  If you have batch files that you used with previous
    versions of the cc:Mail admin utilities, you must change them.   


