User`s guide

Appendix D:Troubleshooting
PShop User’s Guide - 59
have a current version), or you can purchase a non-expiring key by
contacting Vividata.
• PShop cannot find the license server or license file. Follow the instructions
in Verify Licensing above.
Symptom:
Printer outputs garbage characters.
Possible causes and solutions:
• You have the wrong printer driver selected in the ID file. Either run ps_install
to create a new print queue using a different driver, or run
“$VV_HOME/bin/gs -help” for a list of available drivers and select a
different driver.
• In troubleshooting, you may have inadvertently changed the lp system’s idea
of the port for your printer (people often do this mistakenly with
AdminTool’s printer tool). For PShop, the lp system’s idea of the port device
should always /dev/null (or /dev/null0) since PShop finds its port designation
in the printer queue’s ID file. If the “Device: /dev/null0” in the
/etc/lp/printers/<printer_name>/configuration file (Solaris systems) is
showing something other than /dev/null0, change it back to /dev/null0 or use
ps_install to remove the queue entirely and recreate it. In Berkeley style
printing systems, check the port designation in /etc/printcap for your PShop
print queue. The line defining the port assignment should read:
lp=/dev/null0
• The printer cable is loose or defective, there is a bad connection, or there is
some other hardware problem. If you have the printer connected via a switch
box, remove the box and make the connection directly. If you are using a long
parallel or SCSI cable, try a shorter one. Check termination. Try another
cable. You may have a bad interface card or it may not be properly seated into
its connector.
Symptom:
The .results file indicates:
“Image read of ... failed, status = 700”