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


Groups > comp.lang.postscript > #3267 > unrolled thread

postscript -> ghostscript -> HP8600

Started byhomer@lightlink.com
First post2018-06-14 21:38 -0400
Last post2018-06-17 23:22 -0400
Articles 4 — 3 participants

Back to article view | Back to comp.lang.postscript


Contents

  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

#3267 — postscript -> ghostscript -> HP8600

Fromhomer@lightlink.com
Date2018-06-14 21:38 -0400
Subjectpostscript -> ghostscript -> HP8600
Message-ID<pfv5b7$tkl$1@adore.lightlink.com>
    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

[toc] | [next] | [standalone]


#3268

Fromluser droog <luser.droog@gmail.com>
Date2018-06-15 14:30 -0700
Message-ID<87d33c70-74c4-4ccb-859d-e6b357921285@googlegroups.com>
In reply to#3267
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. 

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).

[toc] | [prev] | [next] | [standalone]


#3269

FromMartin Leese <please@see.Web.for.e-mail.INVALID>
Date2018-06-16 10:21 -0600
Message-ID<pg3ddm$d7r$1@dont-email.me>
In reply to#3268
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/

[toc] | [prev] | [next] | [standalone]


#3270 — SOLVED: postscript -> ghostscript -> HP8600

Fromhomer@lightlink.com
Date2018-06-17 23:22 -0400
SubjectSOLVED: postscript -> ghostscript -> HP8600
Message-ID<pg78i4$t37$1@adore.lightlink.com>
In reply to#3269
    Thanks for all your help.

    The download of HPLIP from HP does NOT include hpijs in its setup,
and in fact I can't find out where to down load it.  Without hpijs
installed on the system, GS can run it, so you get errors.

    Yum however in Centos 7 does download both hpijs and hplip,
and together they work for Office Jet PRO 8500, not 8600.

    No matter they are almost identical as far as graphics go.

    So thanks for all you help again.

    Homer

Martin Leese <please@see.web.for.e-mail.invalid> wrote:
> 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.
> 

-- 
------------------------------------------------------------------------
Homer Wilson Smith   Clean Air, Clear Water,    Art Matrix - Lightlink
(607) 277-0959       A Green Earth, and Peace,  Internet, Ithaca NY
homer@lightlink.com  Is that too much to ask?   http://www.lightlink.com

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.postscript


csiph-web