Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.postscript > #3269

Re: postscript -> ghostscript -> HP8600

From Martin Leese <please@see.Web.for.e-mail.INVALID>
Newsgroups comp.lang.postscript
Subject Re: postscript -> ghostscript -> HP8600
Date 2018-06-16 10:21 -0600
Organization A noiseless patient Spider
Message-ID <pg3ddm$d7r$1@dont-email.me> (permalink)
References <pfv5b7$tkl$1@adore.lightlink.com> <87d33c70-74c4-4ccb-859d-e6b357921285@googlegroups.com>

Show all headers | View raw


luser droog wrote:

> On Thursday, June 14, 2018 at 8:38:48 PM UTC-5, ho...@lightlink.com wrote:
>> I have a properly setup CentOS 7 box, running the latest
>> ghostscript.
>>
>>     I use gnuplot to produce postscript plots which I wish to
>> print on these newer HP Office Jet Pro 86xx which do not
>> accept postscript.
>>
>>     I am told I can use the HPLIP package to make ghostscript
>> properly convert postscript to HP8600 format.
>>
>>      However I have found no serious documentation on how to use
>> ghostscript with HPLIP, and the HPLIP web site is horrid.
>>
>>     The command line I am told is:
>>
>> #!/bin/bash
>>  
>> gs \
>> -sDEVICE=ijs -sIjsServer=hpijs \
>> -dIjsUseOutputFD \
>> -sDeviceManufacturer="HP"  \
>> -sDeviceModel="OfficeJet Pro 8600 E-aio n911a" \
>> /tmp/data.ps     <- output of gnuplot.
>>  
>>        Which produces the following errors:
>>
>> Script started on Thu 14 Jun 2018 09:33:36 PM EDT
>> [root@vm2 ~]# testgs
>>
>> GPL Ghostscript 9.07 (2013-02-14)
>> Copyright (C) 2012 Artifex Software, Inc.  All rights reserved.
>> This software comes with NO WARRANTY: see the file PUBLIC for details.
>> GPL Ghostscript 9.07: **** Could not open the file  .
>> **** Unable to open the initial device, quitting.
>> [root@vm2 ~]# 
>>
>> Script done on Thu 14 Jun 2018 09:33:40 PM EDT
>>
>>      The errors are too cryptic for me to understand what they are
>> referring to.
>>
>>      Thanks for your help.
>>
>>      Homer
> 
> ISTM that ghostscript can't open the output device. Possibly the
> hpijs server (daemon?) needs to be running. Or it could be that
> your vm isn't linking up to the host device so gs is getting dead
> air or bad responses. 
> 
> So the things I'd check (if you haven't already) is that the VM
> really can access the printer; and that the hplip package is all
> installed and running. 

I am not sure if this helps or not, but I
ran the script on my system.  This has an
old version of Ghostscript running under
Windows.  I get the error messages:
     GPL Ghostscript 8.60: Can't start ijs
         server "hpijs"
     **** Unable to open the initial device,
         quitting.

This suggests that the hpijs does not have
to be running as Ghostscript will try to run
it.

> It may be possible to work around some of these issues if you
> specify an output file with sOutputFile=/tmp/gsout.hpij or
> similar. gs may be about to create the output even if it cannot
> access the real device or print server. You could then send 
> file to printer some other way (in theory).

This looks like good advice to me.

-- 
Regards,
Martin Leese
E-mail: please@see.Web.for.e-mail.INVALID
Web: http://members.tripod.com/martin_leese/

Back to comp.lang.postscript | Previous | NextPrevious in thread | Next in thread | Find similar


Thread

postscript -> ghostscript -> HP8600 homer@lightlink.com - 2018-06-14 21:38 -0400
  Re: postscript -> ghostscript -> HP8600 luser droog <luser.droog@gmail.com> - 2018-06-15 14:30 -0700
    Re: postscript -> ghostscript -> HP8600 Martin Leese <please@see.Web.for.e-mail.INVALID> - 2018-06-16 10:21 -0600
      SOLVED:  postscript -> ghostscript -> HP8600 homer@lightlink.com - 2018-06-17 23:22 -0400

csiph-web