Specifications

job. For example, a PostScript print job must begin with the two characters %!. If the printer
fails to receive these characters, all the remaining data in the job prints as ASCII. This kind of
problem is usually the result of some sort of communications failure between the PC and the
printer. Check that the cable connections are secure and the cable is not damaged. If the prob-
lem occurs consistently, it might be the result of an improperly configured port in the PC, par-
ticularly if you are using a serial port. Check the port’s parameters in the operating system. A
serial port should be configured to use 8 data bits, 1 stop bit, and no parity (N-8-1).
Using the wrong printer driver also causes gibberish printing. If you had an inkjet printer as
your default and switched to a laser printer but failed to set the laser printer as the default, your
print jobs would produce garbage printing unless you specifically sent jobs to the laser printer.
Similarly, failing to flip a switchbox to use the intended printer also causes this type of printing
error. Thus, many of these printing problems are due to operator error. Whenever you change to
a new printer, make sure you set it as the default. Also, to avoid printer-switch errors, consider
adding a second parallel port for the other printer, or use the new USB-compatible printers if
your system is compatible with them.
■ Printer not available error. When Windows does not receive a response from a printer over the
designated port, it switches the driver to offline mode, which enables you to print jobs and
store them in the print spooler until the printer is available. The printer might be unavailable
because the parallel or serial port is incorrectly configured; the printer cable is faulty; or the
printer is turned off, is offline, or is malfunctioning. A malfunctioning port can be caused by an
IRQ conflict (LPT1 uses IRQ 7, and COM 1 and COM 2 use IRQs 4 and 3, by default). In the
case of a serial port, incorrect start/stop/parity bit settings could be the culprit. A switchbox that
is supposed to automatically scan for print jobs but has been set to manual mode or has been
turned off also can cause this error.
■ Printer does not notify Windows when it is out of paper, is jammed, or has some other problem. This
indicates a communications problem between the printer and the PC. Check the printer cable
and its connections at both ends. Some manufacturers recommend that you use a cable that
complies with the IEEE-1284 standard.
Note
IEEE-1284 cables don’t work in their advanced EPP/ECP modes unless your printer port is also set for an IEEE-1284
mode. Check your system documentation for details.
■ Intermittent or failed communications or a partial print job followed by gibberish. Interruptions in the
communication between the computer and the printer can cause data to be lost in transit,
resulting in partial print jobs or no print output at all. Aside from a faulty cable, these problems
can result from the use of additional hardware between the printer port and the printer.
Switchboxes used to share a printer among several computers and peripherals that share the
parallel port with the printer (such as CD-ROM drives) are particularly prone to causing prob-
lems such as this.
■ Port is busy error or printer goes offline. These errors can occur when an ECP sends data to a
printer at a rate faster than it can handle. You can remedy the problem by using the Windows
System Control Panel to load the standard printer port driver instead of the ECP driver.
■ Error-reporting methods. Some models of the HP LaserJet printers (such as the LaserJet II and III)
report errors with a numerical code displayed on their LCD status panels. Other models use a
series of blinking lights on the system to report errors. Note the error number or blinking light
pattern and check the printer manual or online source to determine the problem and its reso-
lution.