Windows PCL/PS Converter FAQs
Using EPFax/W:
Developer Information:
Q: How do I select input file type?
A: In File…Properties select Input tab. Options
are PostScript, PackBits Compressed PostScript, PCL5e, HP/GL-2,
Auto Detect -Default PostScript, Auto Detect-Default PCL5e, and
PDF. The PCL5e converter (LincJet) emulates an HP LaserJet 4
printer. It supports the core HP/GL-2 which is supported by this
printer.
Q: Why can't I convert a
file?
A: First, make sure you are licensed for the type of
conversion you are doing, and that you have selected the correct
input file type. The default input file type is PostScript, even
if you have only installed the PCL converter.
For PostScript files, if you get several errors in fast
succession, the file may contain binary data. Enable the switch
for "Binary data in input file."
If all else fails, send the file to an appropriate (HP LJ4)
printer to verify its validity. If the file is printed correctly,
but does not convert correctly, then please e-mail it to us.
Q: Why is my output
incorrect?
A: If the converted or viewed output does not look
correct to you, first compare it to printer output. Check
PostScript files on a PostScript Level 2 printer, and PCL5e on a
HP LaserJet 4 printer. (LincJet emulates the LJ4.) If the
converter or viewer output is different from the printed output,
please e-mail us a copy of the source file and the bad output
file. If possible, please fax the desired output to us as
well.
Q: Does LincJet support
HP-GL/2?
A: Yes, it supports HP-GL/2 as it is supported by the
Hewlett Packard LaserJet 4 printer. HP-GL/2 consists of the
HP-GL/2 kernel (core instructions for ALL HP peripherals) and
various HP-GL/2 extensions (printer-specific instructions).
Q: What
is default page size?
A: The default page size is only used when pagesize is
not specified in input file or when an unsupported pagesize is
specified in input file. Fixed bitmap dimensions may be imposed
on an output file, and override input file pagesize. Input file
pagesize overrides default pagesize.
Q: How do I specify
output file configuration?
| Paper |
Specify the default page size for files for which no page size
is specified. Page size in source file overrides the default
setting. |
| Resolution |
Specify resolution of output file, and units of measure.
Includes an option to emulate an HP printer with a 300/600 dpi
toggle switch. This is useful for files with raster logos which
were imaged at 600 dpi. It is safe to leave this switch on all
the time, although there may be rare encounters with files which
convert improperly with this switch enabled. |
| Bitmap |
Specify bitmap size, offsets, fixed width, fixed height
Options: Long-edge scan, Edge-to-edge printer emulation,
alternate scaling, specify halftone (PostScript only) |
| Output |
Output type: raw binary, TIFF, PCX/DCX, Brooktrout Infopacket,
template, and PostScript (PDF only) Byte order in header
(Intel/Motorola) Multipage output switch Filenaming options
Single strip per image switch |
| Fax Encoding |
T4/ Group 3 TIFF, 1-dimensional (default) |
| T4/ Group 3 TIFF, 2-dimensional; K-value for
Group 3/ 2D |
| T6/ Group 4 TIFF |
| Allow uncompressed scans |
| EOL (end of line) (default) |
| Byte align scan lines (default) |
| EOB (end of block) (default) |
| Black is 1 (default) |
| Reverse fill order |
| PCL Font Options |
(used when font information is not specified in the input
file. MultiByte encoding options (for Asian fonts, etc.) default
text direction (horizontal or vertical) default font: source,
font ID, point size and pitch symbol set Write list of font
assignment numbers to the log file. |
| PDF Options |
specify page ranges, odd, even, all options: emit annotated
forms, set page size, emit raw data |
| Job Options |
Release memory at End of Job |
| Show Progress |
| Write log file |
| Job, page time limits (seconds) |
| VM, cache, display list limit (bytes) |
| Objects executed between progress |
| General |
Save Properties when OK is clicked: saves settings in
C:\Windows\EPFax.ini Specify directories for binpath, output,
root, and source. |
Q:
How long does it take to convert a file?
A: File conversion throughput is dependent upon several
factors. These are, among other things, file size and complexity,
CPU speed, available memory (especially with very large files)
and the number of fonts you have installed (beyond the default
font selection).
Q: Are there any restrictions on
the conversion (size of file etc.)?
A: The main restriction would be the limitation of
memory when converting an extremely large file (e. g. 500 to 4000
pages). Such a file would convert very slowly after most of the
available memory had been tied up. Without memory limitations,
the maximum size of a TIFF file is determined by the 32-bit TIFF
tag for number of pages (2*e32 pages).
Text
Extraction and PCL File Splitting
Q:
How can I extract text from PCL files?
A: EPFaxAPI provides the tools with which you can create
an application which can extract information from an input file,
and return information to the converter. The API function
convertFileEx4() enables you to extract unformatted text
information from a file. This information may be used to
determine the disposition of a part of the input file. We do not
provide sample code for any such OEM applications.
For example, many users extract fax number from the file, and use
the fax number to send the fax. To create several output files
from a single input file, one would extract data that
distinguished the parts of the file to be separated, or data
which indicated a break in the file, in order to create a
multipage output file from a portion of the input. In this case,
you can either make a single, multipage TIFF output file and then
use the information to split it into separate files. Or you can
make several single page TIFF output files, and then use the
information to merge these files into the desired multipage
output files.
Q: How can I extract numeric data from PCL files?
A: When the file is searched for numeric data without
success, there may be a problem with drivers downloading
characters with an offset from their actual ASCII value. The
following example illustrates how you can accommodate this:
A PCL file's numeric data has an offset of 3. In order to search
for or extract the number "2000/08/14" that appears at the
beginning of the page, enter the string as "533323;247" ,i.e. add
3 to the ASCII value.
Q: What are the error codes
for the PCL converter?
A: Controller Errors:
| Name |
Index |
Description |
Flash |
COMMERR |
1 |
Communication
line error |
12 |
BUFOVFLO |
2 |
Input
buffer overflow |
13 |
CARTGONE |
3 |
Cartridge has been removed |
14 |
TOOCMPLX |
4 |
Band
too complex to print |
15 |
PAGEOVFL |
5 |
Page
exceeds page buffer memory |
16 |
FROTATE |
6 |
Not
enough memory to rotate font |
21 |
FNTDLMEM |
7 |
Not
enough memory to download font |
23 |
BADFONT |
8 |
Bad
data in downloaded font |
24 |
NO_GLYPH |
9 |
Character
not in selected font |
25 |
FSLCTERR |
10 |
Can't
select required font |
26 |
NOFONTS |
11 |
No
font present |
27 |
ERR_NRAM |
12 |
Non-fatal
lower RAM error |
31 |
FFFULLDR |
13 |
Too
many fonts for table |
32 |
FFBADTBL |
14 |
Font
table has been damaged |
34 |
FFNODL |
15 |
Loading
middle without beginning |
35 |
FFBADCOD |
16 |
Loading
char code outside indexes |
36 |
ERR_PARA |
17 |
Parallel
loopback test failure |
41 |
ERR_LOOP |
18 |
Serial
loopback test failure |
42 |
GLYF2BIG |
19 |
Glyph
exceeds buffer size |
43 |
ERR_FRAM |
20 |
Fatal
lower RAM error |
71 |
ERR_FIRM |
21 |
CRC
error on firmware ROM |
73 |
ERR_TIMR |
22 |
Error
in one of the system timers |
74 |
CRCCHECK |
23 |
CRC
error on a rom or cart font |
|
FFFOMEM |
24 |
no
room for a form |
|
FFREORG |
25 |
No
memory during memory reorg. |
|
FFBADRLE |
26 |
bad
rle code |
|
UNKWNTYP |
27 |
unknown
type of ROM region |
|
BADSSREQ |
28 |
bad
summary sheet request |
|
GRNOMEM |
29 |
unable
to allocate mem for graphics |
|
GRNOOPEN |
30 |
graphics
procedural error |
|
GRNOSCR |
31 |
need
bigger scratch area |
|
GRMEMOVR |
32 |
graphics
record overflow |
|
ROT_WAIT |
|
|
|
FULLNOEXP |
|
Not
enough memory for fullpage mode |
|
DUPMEMERR |
|
Not
enough memory for duplex page |
|
FRAGMEMERR |
|
Memory
pool is too fragmented |
|
INSUFRAM |
|
Insufficient
RAM for scalable font |
|
LOGICALERR |
|
Logical
error in code |
|
PB_FATAL |
|
Can't
allocate initializing buffers |
|
PB_FATAL1 |
|
Logical
error in adding extra bands |
|
FFCPYUFST |
|
Cannot
download chars to hard font in UFST |
|
|
Various
errors (all errors >999 are fatal)
FATAL_ERR |
999 |
INF_ERR |
1000 |
PIPE_ERR |
1001 |
FORK_ERR |
1002 |
EXEC_ERR |
1003 |
LOGIC_ERR |
1004 |
FILE_ERR |
1005 |
PCX_ERR |
1006 |
STD_ERR |
1008 |
WAIT_ERR |
1009 |
TEMPLATE_ERR |
1010 |
COM_ERR |
1011 |
DIR_ERR |
1012 |
DUP_ERR |
1013 |
SYSTEM_ERR |
1014 |
TIMEOUT_ERR |
1015 |
DOC_TIMEOUT_ERR |
1016 |
PAGE_TIMEOUT_ERR |
1017 |
MEM_ERR |
1018 |
KILL_ERR
(Not
really an error) |
2000 |
MAXLINE |
2048 |
|
Various messages
EOJ |
128 |
DOC_TIME_OUT |
129 |
PAGE_DONE |
130 |
NO_MEM |
132 |
READY |
133 |
NO_DOC |
134 |
PAGE_TIME_OUT |
135 |
BAD_PARAM |
136 |
NO_DOC_FILE |
137 |
NO_TIFF_FILE |
138 |
NO_TEMP_FILE |
139 |
P_EOF
premature
end of file |
140 |
DISPLAY_READY |
141 |
FAX_WRITE_ERR |
142 |
TEMP_WRITE_ERR |
143 |
FILE_READ_ERR |
144 |
PROCESS_DONE |
145 |
PS_ERROR |
146 |
PCL_ERROR |
147 |
SYS_ERR |
148 |
CHLD_ERR |
149 |
|
Q: What are
the error codes for the non-Windows PostScript
converters?
A: The
following is a list of error codes that may be sent to the exit
function when a PostScript error occurs in psii2fax. In general,
an LPI function that follows the standard callin returns an
integer value indicating success or failure. A value of 0
(SUCCESS) indicates a successful return. The following codes,
referred symbolically, indicate errors of various
types.
| DICTFULL
|
1
|
dictionary full
|
| DSTACKOFL
|
2
|
dictstackoverflow
|
| DSTACKUFL
|
3
|
dictstackunderflow
|
| ESTACKOFL
|
4
|
execstackoverflow
|
| INTERRUPT
|
5
|
external interrupt
request
|
| INVALACC
|
6
|
invalidaccess
|
| INVALEXIT
|
7
|
invalidexit, "exit" in
improper context
|
| INVALFILE
|
8
|
invalidfileaccess,
unacceptable file access mode
|
| INVALFONT
|
9
|
invalidfont, font is
bad
|
| INVALRST
|
10
|
invalidrestore
|
| IOERROR
|
11
|
error in I/O
|
| LIMITCHECK
|
12
|
limits exceeded
|
| NOCURPNT
|
13
|
nocurrentpoint, current
point undefined
|
| RANGECHECK
|
14
|
operand out of
bounds
|
| STKOFL
|
15
|
operand stack
overflow
|
| STKUFL
|
16
|
operand stack
underflow
|
| SYNERROR
|
17
|
syntax error
|
| TIMEOUT
|
18
|
timeout exceeded
|
| TYPECHECK
|
19
|
incorrect operand
type
|
| UNDEFINED
|
20
|
name not known
|
| UNDEFFILE
|
21
|
file name not
known
|
| UNDEFRES
|
22
|
undefinedresult, overflow
or meaningless result
|
| UNMATMARK
|
23
|
unmatched mark
|
| UNREG
|
24
|
internal error
|
| VMERROR
|
25
|
VM exhausted, internal VM
error
|
| PSWDINCRCT
|
26
|
password
incorrect
|
| MFEEDTIME
|
27
|
manual feed timeout
error
|
| CONFIGERR
|
28
|
configuration
error
|
| INVALCONTEXT
|
29
|
improper use of context
operator
|
| INVALIDID
|
30
|
invalid identifier for
external object
|
| UNDEFRESRC
|
31
|
resource instance not found
|
|
Visual Basic
Q: How can I call EPFaxCL from Visual Basic?
A: To run EPFaxCL
from VB, assuming epfaxcl.exe is in the directory
shown:
Private Sub
EPFRun(InFile, OutPath, OutFile, Options)
Dim Test As
Variant
Test = Shell("c:\lincoln\bin\epfaxcl.exe -d"
& InFile & " -e" & OutPath & OutFile & " "
& Options, vbMinimizedNoFocus)
End
Sub
The subroutine
is called with the indicated arguments.
InFile is the
full path name string of the input file to be converted, OutPath
is a string the indicated the folder where the output should be
placed, OutFile is the output file name as a string, and Options
is a string containing any and all of the command line arguments
required. For instance, selecting PCL5 as the input file form and
TIFF G4 as output would be signified by:
Options = "-*s3 -*t3 -j2
|