Printing Multiple Copies of the Same Job Via LPD Broken in SP4

Article translations Article translations
Article ID: 197846 - View products that this article applies to.
This article was previously published under Q197846
This article has been archived. It is offered "as is" and will no longer be updated.
Expand all | Collapse all


When you submit a print job from a UNIX system to a Windows NT LPD server, you can specify an option to print multiple copies. When using Windows NT Service Pack 4 (SP4), only one copy is printed.


To work around this problem, the control characters "K" or "#" should be used to specify printing multiple copies.


To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
  • Windows Service Pack Center -or-

  • 152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:


Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

More information

Windows NT 4.0 supports two non-RFC 1179 extensions for the LPD control file. If the format control character ("f") is sent multiple times, the file is printed multiple times. Also the "K" or "#" control characters can be used to specify printing multiple copies.

Example: (bsd-style printing)
lpr -Pprinter -#2 <file>

In Windows NT 4.0 Service Pack 4, only one copy is printed even when there are multiple "f" commands in the control file.


Article ID: 197846 - Last Review: November 2, 2013 - Revision: 3.0
Applies to
  • Microsoft Windows NT Workstation 4.0 Developer Edition
  • Microsoft Windows NT Server 4.0 Standard Edition
kbnosurvey kbarchive kbhotfixserver kbqfe kbbug kbfix KB197846

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from