Registrations are now open. Join us today!
There is still a lot of work to do on the wiki yet! More information about editing can be found here.
Already have an account?

Microsoft KB Archive/172799

From BetaArchive Wiki
Knowledge Base


Article ID: 172799

Article Last Modified on 7/15/2004



APPLIES TO

  • Microsoft SNA Server 3.0 Service Pack 4, when used with:
    • Microsoft Windows NT 4.0
  • Microsoft SNA Server 4.0, when used with:
    • Microsoft Windows NT 4.0



This article was previously published under Q172799


SYMPTOMS

When you print an LU3 host print job through Microsoft SNA Server, an extra form feed occurs after the job is printed.

CAUSE

The host was sending the following characters at the end of the print job:

0C 0D 19    *or*   0C 19
                

where:

0C = form feed (FF)
0D = carriage return (CR)
19 = end of medium/end of message (EM)
                

Both FF and EM were resulting in form feeds, causing an extra form feed to occur.

RESOLUTION

To correct this problem, a PDF file can be used which eliminates the form feed sent at the end of the print job. To configure this, follow these steps:

  1. Copy the default <SNARoot>\System\Hplj2.pdf file to Noff.pdf (or whatever name you wish).
  2. Edit the Noff.pdf file and change the END_JOB entry to read as follows: END_JOB = CUL CBP CS1


The default is "END_JOB = CUL CBP CS1 FFF", where FFF = form feed.

  1. Compile the Noff.pdf file as follows: PDFCOMP NOFF.PDF NOFF.PDT
  2. Configure the SNA Print Server session to use the PDT file using SNA Manager. To do this, choose the Print Server session property page, and focus on the Overrides folder. At the bottom of this folder, choose the following:


[X] PDF C:\sna\system\noff.pdt

and click OK.

  1. Save the configuration file, Noff.pdf, then stop and start the SNA Print Server.


STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Microsoft is researching this problem and will post more information in this article when the information becomes available.

Keywords: kbbug KB172799