KnowledgeBase Archive

An Archive of Early Microsoft KnowledgeBase Articles

View on GitHub

Q35534: Why the Editor Cannot Find or Load TOOLS.INI

Article: Q35534
Product(s): See article
Version(s): 1.00   | 1.00
Operating System(s): MS-DOS | OS/2
Keyword(s): ENDUSER | appnote | mspl13_basic
Last Modified: 6-JAN-1989

The following information is taken from an application note called
"Microsoft Editor Questions and Answers." The application note also is
available from Microsoft Product Support Services by calling (206)
454-2030.

Why the Editor Can't Find or Load the TOOLS.INI File

There are several reasons this problem may occur. First of all, you
may have never created a TOOLS.INI file. If TOOLS.INI is not in the
working directory, the INIT environment variable must specify the
directory that contains this file. Within the TOOLS.INI file, there
must be a tag that has the same name as the editor (M.EXE), as
follows:

   [m]

If you have renamed the editor you also must rename the tag. Entries
concerning the editor then would follow after this tag. Under DOS
Versions 2.x, the Microsoft Editor looks for a [c] tag rather an [m]
tag or whatever you have renamed M.EXE to.

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.