Showing posts with label uniprint technical support. Show all posts
Showing posts with label uniprint technical support. Show all posts

Saturday, January 30, 2010

LPR/LPD Printing

What is LPR/LPD?

LPR/LPD is a printing protocol that runs over TCP/IP. Originally implemented for BSD UNIX, its use has spread into other platforms such as AS/400 and legacy mainframe systems. It has essentially become a de-facto industry standard for cross-platform and platform-independent printing, which is a huge advantage of LPR/LPD printing.

The specifications for LPR are defined by the Internet Engineering Task Force (IETF) in Request for Comment 1179 (RFC-1179).

LPR stands for Line Printer Request. It refers to the process that sends print jobs to a remote printer or print queue. It is requesting the service of a print server, so it is the client side of LPR/LPD, and thus is often called the 'LPR client'.

LPD stands for Line Printer Daemon. It refers to the process that accepts print jobs from the LPR client. It is providing a service, so it is the server side of LPR/LPD, and thus is often called the 'LPD server. A daemon is a process running on a UNIX machine, providing services.

How does LPR work?

LPR client sends a request to port 515, the standard port for the LPR/LPD protocol. And the LPD server listens on the same port 515.

When the LPR client sends a print job to the LPD server, it send two files: a data file (the actual data to be printed), a control file.

The data file contains the actual data to be printed. It can be binary of text, depending on the actual format of the print file, or the application that generates the print file.

The name of the data file should start with "dfA", followed by a three digit job number, then followed by the host name that has constructed the data file.

The control file contains information that describes the data file (such as the format of the print data file, e.g., postscript, plain text, FORTRAN carriage control, etc.) and what to do with the data file (such as printing banner page, delete after print, or email after print).

The control file is a plain text file, and its file name should start with "cfA", followed by a three digit job number, followed by the host name which has constructed the control file.

Obviously, the "d" in the "dfA" prefix means data, and the "c" in the "cfA" prefix means control.

RFC-1179 does not impose on the order of the two files to be sent; i.e., one can send the control file first, or the data file first. However, some implementations may stipulate one way or the other, e.g., data file first, followed by control file.

In the future, we will show you how to print from non-windows systems to windows systems using this LPR/LPD protocol.



Click here to see a complete list of articles


To contact us: uniprint.user@gmail.com.

 


Saturday, January 23, 2010

UniPrint and .Net

We came across this podcast on DABCC Radio posted on January 14, 2010. UniPrint’s VP of Software Development Arron Fu was interviewed by Douglas Brown to talk about the upcoming new version 7 of UniPrint.

Arron Fu mentioned that UniPrint will be released "at the end of this year, or the beginning of next year." This would mean that UniPrint will come out by December 2010, or January 2011, which is contradictory to what says on their website. On their website, their banner says UniPrint version 7 is available January 2010. Probably it’s because the interview was done in 2009, but only posted recently.

As well, about 7 minutes 30 seconds into the audio clip, Arron Fu talked about the new things in version 7, one of them being "a new graphic interface, or the console". He continued to reveal that they "were able to rewrite the console completely in .Net platform."

Microsoft’s .Net technology has been around for about ten years by now, and UniPrint has just started writing their products in the .Net platform. Hmm, that makes one wonder, UniPrint being a software technology company, where they are on the technology curve.



Click here to see a complete list of articles


To contact us: uniprint.user@gmail.com.