home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
OS/2 Shareware BBS: 11 Util
/
11-Util.zip
/
PRNMON.ZIP
/
PRNMON.DOC
< prev
next >
Wrap
Text File
|
1989-02-15
|
3KB
|
77 lines
NOTE: This program has NOT been "fully" tested.
Use at your own risk.
This monitor is designed to eliminate leading "garbled"
printer output when using the OS2 SE 1.1 Spooler Queue
Manager and IBM4201 driver with an incompatible printer. The
output is designed to be that of a "generic" driver.
The printer I am using is a HP Paintjet hooked up to a
Model 50 running IBM OS2 SE 1.1. I have no fonts loaded via
the control panel. I tester the monitor with straight text,
text with embedded escape sequences, and raster image files,
and encountered no errors in the output.
Start the monitor program after the Spooler Queue
Manager has finished loading. It may also be possible to
remove statements (printf's for instance) and detach the
process so it will not take up a screen group.
The monitor is loaded last in the chain and is designed
to operate on the first six packets for each new job sent by
the spooler. Each new job appears to be initialized with 1
"control" packet and 5 packets of escape sequences in the
following order:
Packet 1 00 00 00 00 --> packet header info
4 bytes
Packet 2 00 00 00 00 --> packet header info
16 bytes 1B 35 00
1B 34
1B 43 00 0B
12
1B 52
Packet 3 00 00 00 00 --> packet header info
16 bytes 1B 58 01 FF
0D
1B 55 00
1B 46
1B 48
Packet 4 00 00 00 00 --> packet header info
12 bytes 1B 54
1B 5F 00
1B 2D 00
Packet 5 00 00 00 00 --> packet header info
7 bytes 1B 49 00
Packet 6 00 00 00 00 --> packet header info
8 bytes 1B 43 00 0B
Blindly editing these packets is probably risky at
best. I have no idea what determines the size and
segregation of these escape sequence packets. It would
probably be valid to put them all in packet 2 (there should
be room). I also have no idea what effect
changing-adding-deleting fonts will have on the operation of
the monitor. Changes like these may insert packets
midstream that contain sequences that will produce "garbage"
on the printer.
I have had problems with the Queue Manager window
hanging after performing queue hold-release and job hold-
release-cancel operations. I don't know if it is due to a
shortage of space on the spool disk, problems in printer
code page switching or what. If the window does hang, files
being sent to the spooler will be accepted, but no output
will go to the printer. This problem has occurred with and
without the monitor registered. Rebooting after all files
needing to be printed have been sent to the spooler will
bring the window back with the previously sent files queued
for printing.
At risk of great embarrassment, the source code has
been included. Being a novice programmer, I would greatly
appreciate any help-comments-corrections concerning the
design and coding job.