OSOTCOM2 - SYS1718 AT STARTUP AFTER INSTALLING COMMUNICATIONS MANAGER/2
01/26/96

=======================================================================
     SYS1718 at Startup after Installing Communications Manager/2
                       All OS/2 Warp Releases
=======================================================================

Please Read Entire Document for Full Explanation of Procedures
--------------------------------------------------------------

DESCRIPTION

After installing Communications Manager/2, the following error message 
is received when the system is started:

   SYS1718: System cannot find ARDERR.
 
The message is followed by garbled characters.

RESOLUTION

1. Open an OS/2 Window.

2. Type E CONFIG.SYS and press Enter.

3. Change: RUN=C:\OS2\SYSTEM\LOGDAEM.EXE
   To:     REM RUN=C:\OS2\SYSTEM\LOGDAEM.EXE  

4. Save and exit the file; then restart the system.

This resolves the SYS1718 error.  

The LOGDAEM.EXE file is an FFST (First Failure Support Technology) OS/2
Diagnostic tool (which is one of the choices in Selective Install). 
Communications Manager/2, LAN, and others add 
RUN=C:\OS2\SYSTEM\LOGDAEM.EXE to the CONFIG.SYS file when they are 
installed, regardless of whether OS/2 Diagnostics has been selectively 
installed or not.

Unless you specifically know how to use the FFST Diagnostic tools, you 
won't need them. Remarking-out the statement in the CONFIG.SYS file 
will prevent the error from occurring at startup.

______________________________________________________________________
IBM disclaims all warranties, whether express or implied, including 
without limitation, warranties of fitness and merchantability with 
respect to the information in this document. By furnishing this 
document, IBM grants no licenses to any related patents or copyrights.  
Copyright (c) 1994, 1996 IBM Corporation. Any trademarks and product 
or brand names referenced in this document are the property of their
respective owners. Consult your product manuals for complete trademark 
information.