|
|
PageView PCL/PS Viewer FAQs
Q: How is Input filetype selected?
A: PageView can be configured for either PS or PCL input.
It recognizes the file extensions .ps and .pcl and will use the
appropriate converter if such a file is opened when it is not the
default.
Q: What
options can be set?
A: Color options (Monochrome, 1 bit/pixel (RGB) and 8
bits/pixel (CMYK).
PCL font options: default font, default symbol set, other, viewing resolution.
Q: How is viewing resolution
selected?
A: In Files, Configure PageView, you can select the
resolution at which you will view. The better the resolution, the
longer it will take to image a file. Usually 2x screen resolution
is satisfactory. Files are always printed at printer
resolution.
Q: How can
I print from PageView?
A: You can print the screen image (bitmap) to any printer,
including page ranges.
If the file was made by a driver which is compatible with the
printer, you can send the original file to the printer, but you
will print all pages.
Q:
Why does PageView slow down significantly with progress through a
large file?
A: Converted images are stored in temporary (mapped
memory) files on disk. Note that by increasing viewing resolution
by N, temporary file size will be increased by N squared.
Q: Does
PageView's OLE interface allow you to print onto a given printer,
in order to start one print job for several different
documents?
A: No. PageView's OLE interface allows the user to specify
the printer name for both the application and the individual
documents. If the printer name is not specified, the current
windows default printer is used. The OLE does not provide a way
to send a file to the printer as a part of a print job which has
already begun.
Q:
Why is the printed output from PageView offset on the
page?
A: The offset in the printed output is the result of 2
printer offsets.
- The original PCL file includes an offset, manifest in the
screen image, which places the image on the page according to the
source printer's printable area.
- When you print the screen image to your local printer, that
printer driver creates a printer file which includes the offset
for its printable area. This offset is manifest on the printed
output.
Solution:
First determine the offset by trial and measurement. Then enter
the offsets in the viewer's printing configuration (File,
Configure LDV, Printed Page Offset).
Q: Can the PageView progress bar
be disabled?
A: Yes. The progress bar can be disabled using the
SetBDisableProgress(TRUE) method.
Q:
What is the difference between OpenFile and ViewFile?
A: With OpenFile, a file can be in-place activated as part
of the container app's document. With ViewFile, a Pageview
application window is opened to display the file.
Q: Does the
IPVEventSink(Docset_complete) event really signal the document
has been converted?
A: The IPVEventSink(Docset_complete) event signals that
the document has been converted to a bitmap but not necessarily
completely displayed. Just after signaling this event, the
progress dialog is closed. We do not have an event that signals
the page has been converted.
Q: How can you
get PageView to use a macro which is downloaded to a printer and
called by a file?
A: To get forms to load automatically, create a StartUp
folder in the LincJet RootDir and place the forms files in the
StartUp folder. To locate the LincJet RootDir, look in the
EPFax.ini file (located in the Windows directory). In the
EPFax.ini file, the RootDir is specified in the [LincJet]
directory. The default value is C:\Lincoln\LincJet.
Q: Do you have Visual Basic sample code?
A: No. PageView includes a COM interface.
Q: Can I set up the PCL viewer to ignore default pagesize and accept only Form Feed characters
inside the text?
A: If the PCL contains a pagesize command, it will
override the default. If the file is ASCII, the page size will be
either the default or that size otherwise specified by the user.
The default pagesize can be specified on the command line or in
the .ini file.
Q: What are the
error codes for the PCL viewer?
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 |
33 |
Font rotation wait |
|
| FULLNOEXP |
34 |
Not enough memory for fullpage mode |
|
| DUPMEMERR |
35 |
Not enough memory for duplex page |
|
| FRAGMEMERR |
36 |
Memory pool is too fragmented |
|
| INSUFRAM |
37 |
Insufficient RAM for scalable font |
|
| LOGICALERR |
38 |
Logical error in code |
|
| PB_FATAL |
39 |
Can't allocate initializing buffers |
|
| PB_FATAL1 |
40 |
Logical error in adding extra bands |
|
| FFCPYUFST |
41 |
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
registry settings does PageView use?
A: The following string values are required in the
registry under
HKEY_LOCAL_MACHINE\Software\Lincoln\PageView\3.0\Settings:
| Value Name |
Sample Value Data |
| COLOROPTIONS |
0,0,1,1,1,1,1 |
| FILETYPE |
1 |
| MAINTOOLBAR |
-2,38,130,70,0 |
| MAINWINDOW |
2,3,-1,-1,-1,-1,110,110,878,647 |
| ORIENTATION |
-1 |
| PAGESIZE |
0,-1,8.500000,11.000000 |
| PAGEVIEWOPTIONS |
222,0,0,16777215,0,1,10,0 |
| PCLFONTPROPERTIES |
0,6,10.0000,12.0000,8U,0,0 |
| PCLOPTIONS |
0,0,0,1,0,1,0,1,0,0,0 |
| RESOLUTION |
3,300,300 |
| SHOWCONTROLBARS |
1,1,1 |
| VIEWSTATE |
3,1,2,1,25,1,5,50,75,100,150,200 |
| VIEWTOOLBAR |
128,38,660,70,0 |
|
If you are making your own installation package, your
installation must modify the registry to include your selected
values. Selected PageView options are saved in registry by
properly exiting PageView (File, Exit).
|
(978) 244-0250
