Office 4.x: Misccm.c Line Error 447 or 448 During Setup

• Microsoft Office for Windows, versions 4.2, 4.2c, 4.3, 4.3c
• Microsoft Windows NT version 4.0

SYMPTOMS

When you run the Setup program for the versions of Microsoft Office listed at the beginning of this article, you receive one of the following error messages multiple times:

   Setup Message
   Setup has encountered a problem.
   Please report File='.\misccm.c', Line='447' to Microsoft Product
   Support Services.

   -or-

   Setup Message
   Setup has encountered a problem.
   Please report File='.\misccm.c', Line='448' to Microsoft Product
   Support Services.

CAUSE

This problem may occur if the following conditions are true:

• You are installing Microsoft Office on a computer running Microsoft Windows NT version 4.0.

  -and-

• Fonts are installed on the computer's hard disk in two different folders:

        Winnt\Fonts
        Winnt\System
  

WORKAROUND

To prevent this problem from occurring, remove all fonts from the Winnt\System folder before you run Microsoft Office Setup. To do this:

1. On the Start menu, click Run. In the Open box, type "cmd" (without the quotation marks), and click OK.

2. At the MS-DOS prompt, type the following commands, in the order given. Press ENTER after you type each command:

         C:
         CD\
         MD OLDFONTS
         MOVE C:\WINNT\SYSTEM\*.TTF C:\OLDFONTS
         EXIT
   

   Substitute the appropriate path to your System folder in the MOVE command (for example, C:\WINNT40\SYSTEM).

After the fonts have been removed from the Winnt\System folder, run Microsoft Office Setup. Setup should run successfully and you should not receive any further error messages.

After Microsoft Office Setup is complete, you can move your fonts back to the Winnt\System folder if you want. You can use Windows Explorer to do this, or you can type the following command at the MS-DOS prompt:

   MOVE C:\OLDFONTS\*.TTF C:\WINNT\SYSTEM

STATUS

Microsoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available.