Microsoft KB Archive/246166
Article ID: 246166
Article Last Modified on 11/14/2003
- Microsoft Internet Explorer 5.5
- Microsoft Internet Explorer 5.01
- Microsoft Internet Explorer 5.0
This article was previously published under Q246166
IMPORTANT: This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
When you upgrade from Internet Explorer version 3.02 or 4.01 to Internet Explorer 5 on Microsoft Windows NT 4.0 with the Show only TrueType fonts in the programs on my computer setting enabled, special characters such as "1/2" or language-specific characters may appear with a different font than the system font and may be unreadable. For example, the floppy disk icon may exhibit this problem.
During the Internet Explorer 5 installation, MS Sans Serif is set as the system font. MS Sans Serif is not a TrueType font, so if the Show only TrueType fonts in the programs on my computer option is set, non-TrueType fonts and special characters are not displayed properly.
Use one of these two methods to resolve this problem:
- Click Start, point to Settings, and then click Control Panel.
- Double-click Display, click the Appearance tab, and then click Icon in the Item box.
- In the Font box, click Arial, or another TrueType font, and then click OK.
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To modify the registry to disable the TrueType Only option:
- Start Regedit.exe and view the following key:
- Set the value for TTonly to 1.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Keywords: kbprb KB246166