My Filepro Printers Quit Working

Jean-Pierre A. Radley appl at jpr.com
Fri Sep 21 10:29:35 PDT 2007


Ken Brody propounded (on Fri, Sep 21, 2007 at 09:28:52AM -0400):
| Quoting Frank7767 (Thu, 20 Sep 2007 20:24:53 EDT):
| 
| > HELP!
| >       System is SCO-UNIX 3.2.5.07 W/FILEPRO.  system has 4 printers..2 HP
| [... installed rlp ...]
| > from dclerk or dreport..The only error we saw was when JP tried to hardcopy a
| > screen. The error was "cannot open /usr/bin/lp"
| >
| > I removed the rlp [using makdev rlp] and rebooted the system..no  change...
| >
| > Clearly FilePRO is looking for something the mkdev rlp smashed..God knows
| > what...
| >
| > right know the customer is sending the output to a file and calls me to
| > print it.
| 
| Well, the only thing filePro will look for to print is what you tell it
| to look for.  Given that the error is "cannot open /usr/bin/lp", the
| first question is "do you have a /usr/bin/lp and can filePro access it?"
| (And a side question is, how exactly does that error text appear?  In a
| filePro error message?  In the middle of the screen?  Somewhere else?)
| 
| If you su to "filepro", can you print using:
| 
|      echo "This is a test" | the_exact_command_line_defined_in_pmaint
| 
| For example:
| 
|      echo "This is a test" | lp -dlaserjet
| 

Frank was paraphrasing.  The exact message is:

	/usr/bin/lp: /usr/bin/lp: cannot open

Makes little sense, implying that a program (which I *can* run from the
command line) cannot open itself.

IAC, MP5 on OSR 5.0.7 somehow impairs the aboility to install remote
printing.  I removed the CUPS subsystem, and all is well again. See SCO's
TA 125723.

-- 
JP
	==> http://www.frappr.com/cusm <==


More information about the Filepro-list mailing list