A font conflict can cause system errors (for example, Invalid Page Fault errors) when you work in applications. A font conflict can occur when you use a damaged font, have too many fonts installed in the Windows registry, or use an old or incompatible font. The troubleshooting steps in this document help you isolate a font conflict and ensure that you use the current version of a font.
- Isolate damaged fonts in Windows NT, Me, 98, or 95
- Isolate damaged PostScript fonts in Windows NT, Me, 98, and 95
- Isolate damaged TrueType fonts in Windows NT, Me, 98, and 95
- Isolate damaged fonts in Windows XP and 2000
- Isolate fonts managed by ATM in Windows XP and 2000
- Isolate fonts managed by the Fonts utility in Windows XP and 2000
- Check font integrity
- Show all
Isolate damaged fonts in Windows NT, Me, 98, or 95
In Windows NT, Me, 98, and 95, you install and remove PostScript fonts (Type 1 fonts) using Adobe Type Manager Light or Deluxe. You can also use ATM Deluxe to activate and disable TrueType fonts. To isolate a damaged font, you can prevent fonts from being loaded and then load the fonts in small groups. After loading each group of fonts, work in your applications until the problem recurs.
Isolate damaged PostScript fonts in Windows NT, Me, 98, and 95
To isolate a damaged PostScript font in Windows NT, Me, 98, or 95, remove all fonts from ATM. Then, remove font references from the Win.ini file and the Atm.ini file. Finally, reinstall the fonts in small groups from their original disks.
Isolate a damaged PostScript font:
Isolate damaged TrueType fonts in Windows NT, Me, 98, and 95
You can isolate a TrueType font conflict by removing the fonts from the Fonts folder and then adding them in small groups. Or, you can use ATM Deluxe to enable and disable fonts. If you use a font management utility other than ATM Deluxe, disable the utility to ensure that Windows doesn't load the fonts.
Isolate a damaged TrueType font using the Fonts folder:
Isolate damaged fonts in Windows XP and 2000
In Windows 2000 and XP, PostScript fonts can be installed and removed using either the Windows Fonts utility or ATM Light or Deluxe. TrueType fonts can be installed and removed using the Fonts utility in the Windows Control Panel, or by using ATM Deluxe. To isolate a damaged font, you can prevent fonts from being loaded and then load the fonts in small groups. After loading each group of fonts, work in your applications until the problem recurs.
Isolate fonts managed by ATM in Windows XP and 2000
To isolate a damaged font installed using ATM in Windows 2000 or XP, remove all fonts from ATM. Then, reinstall the fonts in small groups from their original disks.
Isolate fonts managed by the Fonts utility in Windows XP and 2000
To isolate a damaged font installed using the Fonts utility in the Windows Control Panel, remove fonts from the Fonts folder. Then add them in small groups.
- Try to re-create the problem. If the problem occurs, it can be related to a font installed by Windows. (To reinstall fonts installed by Windows, you must reinstall the Windows operating system.) If the problem doesn't occur, move a small group of fonts back into the Fonts folder, and then restart Windows.
Check font integrity
System errors can also occur when applications access damaged fonts. You can use the Fonts folder to check for damaged fonts, or you can use ATM Deluxe 4.x.
Check for damaged fonts with ATM Deluxe:
- Deactivate and reactivate the font by clicking the Sets tab, selecting the font, clicking Deactivate, and then clicking Activate.
- If the font isn't stored on the local hard disk, make sure that ATM can access the font. Reconnect to the drive or other media where the font is installed.
- Delete and reinstall the font from the original font installation disk or CD.
Check for damaged fonts with the Fonts folder:
Note: It's possible that damaged TrueType fonts still display sample text, so viewing sample text doesn't guarantee a font's integrity.
Check dates of PostScript font files
Older fonts can cause errors in newer operating systems and applications. To ensure compatibility with current applications and operating systems, make sure that the PostScript fonts you use are dated 1993 or later. Before 1993, Adobe revised a large portion of its type library, mostly to accommodate cross-platform naming conventions, although some font information was also revised. Older fonts work fine on most computers, but some newer applications and operating systems cannot interpret the older font information. You can check the date of your font in Windows Explorer or in ATM. For information about updating Adobe PostScript fonts, contact Adobe Customer Service at 800-833-6687.
To check the date of a PostScript font in Windows Explorer, select the .pfm or .pfb file and choose File > Properties.
To check the manufacturer and date of a PostScript font in ATM, do the following:
Reduce the amount of font information in the Windows registry key
All TrueType font files are registered in a single key in the Windows registry. PostScript font paths can also take up space in the registry key.
If the registry key contains too much information, your system can behave erratically (for example, return errors). To reduce the amount of information stored in a registry key, remove fonts. If you need the fonts, reinstall them in their default folders (C:\Windows\Fonts for TrueType fonts; C:\Psfonts and C:\Psfonts\Pfm for PostScript fonts). If font files are in a folder other than the default folder, the full path to the font is included in the registry. The full path occupies more space in the key and reduces the number of fonts you can install without errors. For example, if the path to font files is C:\Mystuff\Business\Fonts\Truetype Fonts\A-E\xxxxxx.ttf, the path to the font file takes up more space than the path to fonts installed in the C:\Ttfonts folder.