Print Job Stuck In Queue Using Profound 3.0

DocumentID: 635883
Revision Date: 29-Feb-96 3:04:01 PM

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

Problem

Symptoms: The customer is running WordPerfect 5.1 for DOS from a third-party shell program called Profound. When he upgraded Profound from version 2.1 to version 3.0, he began having problems printing in WP. In a multi-server environment (Novell 3.11) if the user's default directory is on Server1, and he executes WP, which is on Server2, and then prints to a queue that is not on Server1, the job is added to the queue but is stuck there with an Adding status. If the user changes the default directory to one that is located on Server1 or if he prints to a captured port, there is no problem. Solutions: Profound is a document management program. It internally shells to DOS to check its overlay code (the equivalent of the WP Go to DOS command) when it searches for documents. When this is done during a print job, the print job is interrupted. When it resumes, WP has lost track of the server it was printing to. Since the print job was not closed by WP, it becomes stuck in the Adding status (which can be seen in PCONSOLE). Status: Sent to Development ***|sent to dev|*** Press Enter on link token.

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.