How TSR's Affect Printing

DocumentID: 651642
Revision Date: 29-Feb-96 8:29:08 PM

The information in this document applies to:
WordPerfect® 5.1 for DOS

Problem

Symptoms: After editing a table, the document takes over six minutes to print, before it only took 45 seconds. The document contains two Bitstream fonts, one marked with a plus, the other with an asterisk. Solutions: After cleaning out the customer's AUTOEXEC.BAT, the document printed correctly. Apparently a resident program was taking control of the CPU at print time, and not returning control to WordPerfect. When the interrupt is called at print time, all programs, loaded resident, have a chance to capture that information. The priority of which resident program gets to look at it first is based on the last in/first out rule. The last program loaded resident will look to see if it needs to perform a function if this interrupt is called. If it doesn't, it is supposed to pass that to the next resident program loaded in memory. This goes on for all TSR programs until the last passes the control back to the operating system, which WP will act on. If any of these TSR's does not pass on the interrupt it can cause a lock up. If there are printing problems, removing TSR's is a valid troubleshooting step.

Answer:

Details:

Product specifications, packaging, technical support and information (*Specifications*) refer to theUnited States retail English version only. Specifications for other versions may vary. All Specifications, claims, features, representations, and/or comparisons provided are correct to the best of our knowledge of the date of publication, but are subject to change without notice.OUR MAXIMUM AGGREGATE LIABILITY TO YOU AND THAT OF OUR DEALERS AND SUPPLIERS IS LIMITED. IT SHALL NOTEXCEED THE AMOUNT YOU PAID TO ACCESS THE INFORMATION. SEE LEGAL DISCLAIMER.