The following suggestions will help you to isolate
the specific location of any bad hardware or corrupted printing software
in your printing setup.
-
Use a different method to send the job
to the queue.
If a different method works, there may be
a problem with CAPTURE.EXE, NPRINT.EXE,
or the options that are being used with them.
If you are currently using CAPTURE,
try NPRINT. If you are currently
using NPRINT, try a DOS COPY
to a captured port. Make sure you use similar options
with CAPTURE and NPRINT.
-
Print the job using CAPTURE or
NPRINT using the ``HOLD''
option.
-
Find the print job name in the queue
as described in
``Checking the contents of your job for incorrect control sequences''.
-
If it is a text file, view the
contents of it using FILER.
If the job is corrupt, the problem occurred
before or while the job was written to
the queue.
-
If the job is not corrupt or you
cannot tell because it is graphics, make a
reference file by copying the job file to
a different name or directory.
-
Allow the job to print by removing it
from hold status.
-
Print the reference file by using PCONSOLE
or NPRINT, or by copying it to a captured
port.
WARNING:
When printing the reference file, do not use
a print job configuration that specifies a mode.
This will cause the control codes to be
duplicated in the job.
-
Compare the printout of the reference file to
the first printout.
If the two printouts are different, the job
is being corrupted after it is written to
the queue. There may be a problem with
the printer hardware (port, cable, printer) or the
print server (PSERVER), port
driver (NPRINTER), or printer
configuration.
-
If the printouts are the same, print the
same job from the application again using the
``HOLD'' option.
-
Use DOS COMP, MS-DOS FC,
or a similar utility to compare the reference
file and the job that has been reprinted
from the application.
If these files do not compare, the job
is being corrupted before or during being written
to the queue.
-
If a NetWare utility appears to have a
problem, recopy it to ensure that it is
not corrupt.
If the problem persists, contact your support representative
to see if there is an updated version
of the utility.