Technical data

The setup module DI_ON enables DECimage, and contains the following

instructions:

% ~~~~~~~~~~ DI_on ~~~~~~~~~~

statusdict begin false setDECimage end

systemdict /languagelevel known {languagelevel} {1} ifelse

2 ge {currentpagedevice /Install get exec} if

statusdict begin true setDECimage end

% ~~~~~~~~~~~~~~~~~~~~~~~~~~~

Note

Some setup modules contain escape sequences or graphics, which

cannot be displayed when you type the ﬁle. For such modules, you may

wish to use the DUMP/RECORD command on the extracted ﬁle.

7.3 Creating Custom Setup Modules

You can create setup modules that affect print jobs with different data types.

Some setup modules manipulate ANSI print jobs, while others affect PostScript

jobs. You can create setup modules for any data type you support.

Notes:

• If your PCL or Proprinter setup module needs carriage-control characters

after each line, manually supply them when you create the setup module

ﬁle. (PCL and Proprinter setup modules do not end line with carriage-

control characters because the setup modules may contain binary data, like

fonts and raster graphics.)

• ANSI setup modules cause a page eject in the printer before the data ﬁle,

if the setup module causes anything to be printed.

7.4 Creating Device Control Libraries

To make the setup module accessible to users, you must create a device control

library and put the module in the library. Create a different library for setup

modules of each data type. Do not include setup modules of different data

types in the same library. You can create a library for ANSI, PCL, Proprinter,

or PostScript ﬁles.

Creating Setup Modules and Device Control Libraries 7–3