User`s guide

Appendix B:Troubleshooting
142 - ScanShop User’s Guide
Possible causes and solutions:
• Please see the symptoms above relating to SCSI scanners for possible
problems and solutions, substituting “scanner” for “printer” when
appropriate.
Symptom:
Some system printers do not show up in the “Print Controls” window, and you
are running Solaris 2.x, HP-UX, or IRIX (System V-style print systems).
Possible causes and solutions:
• The file $VV_HOME/id/postscript.id does not exist or does not have read
permission set. Make sure you have read permission set on the file and read
and execute permissions set on the $VV_HOME/id directory.
• ScanShop may not have access to your printer interfaces directory
(/var/spool/lp/interfaces for IRIX and HP-UX 9.x, /usr/spool/lp/interfaces
for HP-UX 10.x, and /etc/lp/interfaces for Solaris 2.x). Make sure the
directory has read and execute access, and that all printers in this directory
that you want users to access have read and write permissions.
• A printer interface script may not exist for a particular printer. Create a
interface script for each printer you want users to access. Refer to your
printer administration guide for details on how to do this. Note: Remote
printers may not be accessible by this method.
• PostShop printers will not show up if the interface file references an invalid
ID file.
Symptom:
Some system printers do not show up in the “Print Controls” window, and you
are running OSF/1, SunOS 4.x, or AIX.
Possible causes and solutions:
• The file $VV_HOME/id/postscript.id does not exist or does not have read
permission set. Make sure you have read permission set on the file and read
and execute permissions set on the $VV_HOME/id directory.
• ScanShop may not have access to your /etc/printcap file (OSF/1, SunOS) or
/etc/qconfig file (AIX). Make sure the file has read access.