Publisher 2002 stops responding when you open or save a Publisher file

When you open or save a Microsoft Publisher file in Publisher 2002, you may receive the following Office Application Error Report message, and Publisher stops responding (hangs): The details of the crash state that the crash occurs in module PTXT9.dll.

This problem can occur if more than 250 device fonts or PostScript Level 1 fonts (ATM fonts) exist on the same system where Publisher 2002 is installed.

NOTE: To identify device fonts or PostScript Level 1 fonts (ATM fonts) in Publisher, view the Font menu. On the Font menu, all device fonts and PostScript Level 1 fonts (ATM fonts) are represented by a printer icon next to the actual font name.

To resolve this problem, obtain the latest service pack for Microsoft Office XP. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

To work around this problem, reduce the number of device fonts or PostScript Level 1 fonts (ATM fonts) on your computer system to fewer than 250 by following these steps.

NOTE: Because there are several versions of Microsoft Windows, the following steps may be different on your computer. If they are, see your product documentation to complete these steps.

1. Use Microsoft Windows Explorer to access the Fonts folder. In most versions of Windows, the Fonts folder appears under the Windows folder.
2. In the Fonts folder, locate the fonts that are identified by a red "A" icon next to the font name.
3. Select several device fonts/PostScript Level 1 fonts (ATM fonts) by clicking each font name while holding CTRL.
4. With several device fonts selected, right-click the selected fonts, and then drag them to another location where you want to store them.
5. When you release the right-click, click Move from the list that appears.
6. Repeat steps 2 through 5, until the total number of device fonts/PostScript Level 1 fonts (ATM fonts) in the Fonts folder is fewer than 250.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article. This problem was first corrected in Microsoft Office XP Service Pack 2 (SP-2).