New RPM 7 Beta is now available — try the new release →

RPM Raw Print Action

Screenshots in this article are from RPM 6.2.

ActionsText printRaw printEmailArchive to diskFilter/programCopy to queueLPR printIP printArchive to FTP

What it does

Sends documents consisting of printer codes directly to a printer, bypassing the printer driver. Typically the original print job contained the raw printer codes; RPM can also generate printer codes from other input types.

Purpose

RPM works with the Windows print system, but in the case of raw print, we do not talk to the device driver. We still spool to the printer for Windows to manage in the usual way.

We support:

The raw print action also supports page range, using form feeds to delimit pages.

Setup

Two things the driver was doing for you

Bypassing the print driver means bypassing the small conversions it performed silently. Two show up often enough to be worth naming, and both are cured either by a transform or by switching the queue to the Text print action, which handles them automatically.

Stair-step output. The sending host — typically a UNIX or Linux system — ends each line with a bare line feed, and the printer expects a carriage return with it. With no carriage return the next line begins where the last one ended, so the text walks down and across the page. Add the Unix to DOS transform to the queue. In our experience printers marketed as working with Windows are the least likely to handle a bare line feed on their own.

No page break between documents. A raw stream carries nothing to say a document has ended; with text print, that separation comes courtesy of the Windows driver. Three transforms cover it:

Further reading