6.0
Table Of Contents
- Capturing Data
- Overview
- Key Concepts
- Detailed Directions
- Capture Sample Data for a Document You Install on a Printer
- Capture Sample Data for a Document You Install in PlanetPress Watch
- Capture Sample Data in Windows NT
- Capture Sample Data in Windows 2000/Server 2003/XP
- Capture Sample Data in Windows Host Using a Novell Print Server
- Capture Sample Data in UNIX (Solaris)
- Capture Sample Data using an AS/400 Systems
- Capture Sample Data From a Serial Port
- Creating Triggers
- Overview
- Key Concepts
- Detailed Directions
- Implement a Trigger under Novell 3.x
- Implement a Trigger under Novell 4.x and 5.x with NDS or Bindery Printers
- Implement a Trigger under Windows NT 4.0 with TCP/IP
- Implement a Trigger under BSD Printing Systems (BSDi, FreeBSD, Linux)
- Implement a Trigger under UNIX System V (Solaris)
- Implement a Trigger and Configure an AIX 4.3 Printer
- Implement a Trigger under VMS
- Implement a Trigger with AS/400 Systems
- Prepare SAP Device Type for PlanetPress Design
- Implement a Trigger under HP 3000
- Special Printer Requirements
- ASCII Conversion Table
- CL Program for AS/400 Systems
- Index
94
A
To set a parallel or INA port for binary data:
1. To switch to binary mode, enter the following (ASCII off):
%!PS
true 0 startjob
currentsystemparams /CurInputDevice get
<< /Filtering /None >> setdevparams
2. To switch to ASCII mode, enter the following (Binary off):
%!PS
true 0 startjob
currentsystemparams /CurInputDevice get
<< /Filtering /InterpreterBased >> setdevparams
Note that these files are port specific. Thus if you send the files to the printer using its parallel port, only
the parallel port is affected.
Also note that Optra S 81.10 base code does not support the /Filtering parameter. Base code 85.21 and
later in all Optra SC and Optra K code versions do support the /Filtering parameter. Optra + base code 52.04
and later releases all support switching from binary to ASCII mode.
Printers with Automatic Emulation Switching
A <CTRL+D> character on the first line of a trigger normally indicates the end of one job and the
beginning of another. This prevents mixups in print jobs.
Some printers implement an Automatic Emulation Switching (Auto Switch) feature that automatically
recognizes what emulation it requires to process a job. In this case, when the file containing your trigger is
in ASCII, the printer does not recognize the first few lines as a PostScript program (your trigger). Instead it
makes the printer enter ASCII emulation. To prevent this, you must modify the trigger as follows to force
the printer to switch to PostScript.
<ESC>%-12345X
<ESC>%-12345X@PJL JOB
@PJL ENTER LANGUAGE = POSTSCRIPT
%!PS-Adobe
(INVOICE) run INVOICE