You are currently offline, waiting for your internet to reconnect

How Windows NT LPD Server Implements LPR Control Characters

This article was previously published under Q124735
This article has been archived. It is offered "as is" and will no longer be updated.
The Windows NT LPD Server is based on RFC1179, which defines the standardfor TCP/IP Printing using Berkeley Style Daemons (BSD). However, theWindows NT LPD Server does not implement all incoming control charactersbecause of overlapping functionality which already is present in WindowsNT or because the control character is Unix-specific.
The following format control characters as specified in RFC1179 areimplemented by Windows NT's LPD Server:

   f - Print formatted file   l - Print file leaving control characters				

Other LPR format control characters, such as 'o' for format file asPostScript, can be emulated in Windows NT by setting the print queue'sDatatype to TEXT and using the proper printer driver. When the TEXTDatatype is selected for a print queue, any incoming jobs are formattedusing the driver that is set up for the queue.

To emulate LPR jobs that send the 'o' control character, the print queueshould be set up to use the proper PostScript driver and the Datatypeshould be set to TEXT. Then, any incoming jobs (regardless of source) willbe formatted using the PostScript driver. Thus, the 'o' control characterdoes not need to be implemented by LPD, as the Datatype already providesthis functionality.

Also, because the TEXT Datatype can use any Windows NT printer driver,more functionality is provided than the control characters defined inRFC1179, as there are several types of printers supported by Windows NTwhose formats are not specified in RFC1179.

Other LPR control characters, such as L for print banner page, can beemulated in Windows NT by using the proper set up. To print a banner page,set up the Windows NT Separator Page for the queue.

Some LPR control characters are Unix-specific, such as S for symbolic linkdata, thus they cannot be emulated in Windows NT.

For additional information on RFC1179, see the following article in theMicrosoft Knowledge Base:
124734: Text of RFC1179 Standard for Windows NT TCP/IP Printing

Article ID: 124735 - Last Review: 02/27/2014 10:17:25 - Revision: 2.2

Microsoft Windows 2000 Server, Microsoft Windows 2000 Advanced Server, Microsoft Windows 2000 Professional Edition, Microsoft Windows NT Workstation 3.5, Microsoft Windows NT Workstation 3.51, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 3.5, Microsoft Windows NT Server 3.51, Microsoft Windows NT Server 4.0 Standard Edition

  • kbnosurvey kbarchive kbprint KB124735