WordArt Doesn't Recognize Installed TrueType Fonts

Last reviewed: August 4, 1997
Article ID: Q104153
The information in this article applies to:
  • Microsoft Publisher versions 2.0, 2.0a
  • Microsoft Creative Writer for Windows, version 1.0

SYMPTOMS

In the Microsoft Products listed above, you may receive an error message in WordArt indicating that you do not have TrueType fonts installed even if you do. When you try to launch WordArt, the following error message may appear:

   WordArt needs TrueType fonts to produce WordArt effects. There are
   no TrueType fonts accessible on your computer. See your Windows
   manual for more information on TrueType fonts.

When you click OK, a message similar to the following appears:

   Unable to launch or communicate with server application.

   Publisher is unable to open the application needed to complete this
   task. Your system may be low on memory. Save your work, and close
   any other applications to free up memory, and then try again. If
   you've already done this, the application may not be accessible.
   Press F1 if you want more information.

To verify that TrueType fonts are installed and enabled, follow these steps:

  1. In the Windows Control Panel, choose Fonts.

  2. Scroll through the Installed Fonts list. TrueType fonts will have the word "TrueType" in parentheses following the name of the font.

  3. Select some TrueType fonts and make sure that samples of them appear in the Sample area at the bottom of the Fonts window.

  4. Choose the TrueType button.

  5. Make sure the Enable TrueType Fonts check box is selected and choose OK.

  6. In the Fonts dialog box, choose Close.

To double-check that TrueType fonts are available, try using them in another Windows application.

CAUSE

If TrueType fonts really are installed and enabled, but WordArt still is unable to recognize them, you may be experiencing one of the following problems:

  • You may not have a SETUP.INF file in your Windows SYSTEM subdirectory. If SETUP.INF is missing, correct this problem by copying the SETUP.INF file from the Windows Setup disks to your SYSTEM subdirectory.

    -or-

  • This problem may also occur if the SETUP.INF file in the Window SYSTEM subdirectory is too big. If this is the case, the [Language] section cannot be read because it is at the end of the file and too close to the 64K memory limit.

RESOLUTION

To resolve this problem in Publisher, try any of the following solutions.

NOTE: A similar problem occurs in Microsoft Creative Writer for Windows. Use Solution 2 below to correct this problem in Creative Writer.

Solution 1

To avoid this problem, upgrade to version 2.0a.

To obtain new or updated Microsoft products, call Microsoft End User Sales at (800) 426-9400. International customers should see Microsoft's World Wide Offices Web site at:

   http://www.microsoft.com/worldwide/default.htm

Solution 2

Copy the original SETUP.INF file from the original Windows disks to the WINDOWS\SYSTEM subdirectory, overwriting the existing setup.inf file.

Solution 3

Delete the WordArt 2.0 entry from REGEDIT, then re-register WordArt 2.0.

STATUS

Microsoft has confirmed this to be a problem in Publisher version 2.0. This problem was corrected in Publisher version 2.0a.


Additional query words: 2.00 mspub pub20 win31 wa can't run fail
true type word art Can't find TT font w_works wm_writer writer kids
mskids pub_pp errmsg wm_writer homekids creative
Keywords : kberrmsg kbtool
Version : WINDOWS:2.00,2.00a
Platform : WINDOWS
Issue type : kbbug
Solution Type : kbworkaround


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.

Last reviewed: August 4, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.