pscript driver update with PIN broken in 30.827? - OS2

This is a discussion on pscript driver update with PIN broken in 30.827? - OS2 ; Hi all, now I am trying to tell the postscript driver (30.827) about my Epson Acculaser C1900 colour postscript printer. To that end, I am using the pin.exe utility as documented in the readme file of the printer driver, together ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: pscript driver update with PIN broken in 30.827?

  1. pscript driver update with PIN broken in 30.827?


    Hi all,


    now I am trying to tell the postscript driver (30.827) about my Epson
    Acculaser C1900 colour postscript printer. To that end, I am using the
    pin.exe utility as documented in the readme file of the printer driver,
    together with the PPD file of the printer. This used to work with
    earlier versions of the ps driver. It does not now anymore.

    Here is the log of pin.exe, when run on the 30.827 driver.

    [E:\tmp\ps]PIN.EXE PPD PPD\ OUT\pscript.drv
    PostScript resource packaging utility version 1.00
    Copyright (c) IBM Corp. 2000,2001. All rights reserved.
    Producing Printer Device PAK
    reading driver extended attributes
    success
    extended attributes read
    checking driver version: EA item was not found
    fail
    fail


    And indeed, the file pscript.drv, when opened in the WPS, does not have
    the typical printer icon attached to it. It looks just like a data file.
    Upon double click it opens as usual, but apparently this is enough to
    have pin.exe fail the test?

    Directory of E:\tmp\ps\out
    1-31-05 11:20a 141,418 0 a--- pin.exe
    1-31-05 11:20a 10,100 0 a--- pin.sym
    1-31-05 11:20a 58,223 0 a--- ppdenc.exe
    1-31-05 11:20a 5,236 0 a--- ppdenc.sym
    1-31-05 11:21a 4,666,084 0 a--- printer1.pak
    1-31-05 11:32a 806,550 0 a--- pscript.drv
    1-31-05 11:21a 18,968 0 a--- pscript.ea
    1-31-05 11:20a 49,169 0 a--- pscript.hlp
    1-31-05 11:21a 39,128 0 a--- pscript.lst
    1-31-05 11:21a 37,956 0 a--- pscript.sym
    1-26-05 2:31p 13,347 0 a--- readme
    Directory of E:\tmp\ps\ppd
    11-19-05 10:03a 56,399 0 a--- epalc190.ppd


    By comparison, the 30.800 driver does work, as does the version 30.817
    as shipped with ecs 1.2.

    I tried attaching the ea with eautil, but it complains about mismatching
    EA sizes and refuses to do its thing.

    Any ideas on (a) how to fix this and (b) where to report it?


    Cheers, Stefan

  2. Re: pscript driver update with PIN broken in 30.827?

    Sir:

    Stefan A. Deutscher wrote:
    > Hi all,
    >
    >
    > now I am trying to tell the postscript driver (30.827) about my Epson
    > Acculaser C1900 colour postscript printer. To that end, I am using the
    > pin.exe utility as documented in the readme file of the printer driver,
    > together with the PPD file of the printer. This used to work with
    > earlier versions of the ps driver. It does not now anymore.
    >
    > Here is the log of pin.exe, when run on the 30.827 driver.
    >
    > [E:\tmp\ps]PIN.EXE PPD PPD\ OUT\pscript.drv
    > PostScript resource packaging utility version 1.00
    > Copyright (c) IBM Corp. 2000,2001. All rights reserved.
    > Producing Printer Device PAK
    > reading driver extended attributes
    > success
    > extended attributes read
    > checking driver version: EA item was not found
    > fail
    > fail
    >
    >
    > And indeed, the file pscript.drv, when opened in the WPS, does not have
    > the typical printer icon attached to it. It looks just like a data file.
    > Upon double click it opens as usual, but apparently this is enough to
    > have pin.exe fail the test?
    >
    > Directory of E:\tmp\ps\out
    > 1-31-05 11:20a 141,418 0 a--- pin.exe
    > 1-31-05 11:20a 10,100 0 a--- pin.sym
    > 1-31-05 11:20a 58,223 0 a--- ppdenc.exe
    > 1-31-05 11:20a 5,236 0 a--- ppdenc.sym
    > 1-31-05 11:21a 4,666,084 0 a--- printer1.pak
    > 1-31-05 11:32a 806,550 0 a--- pscript.drv
    > 1-31-05 11:21a 18,968 0 a--- pscript.ea
    > 1-31-05 11:20a 49,169 0 a--- pscript.hlp
    > 1-31-05 11:21a 39,128 0 a--- pscript.lst
    > 1-31-05 11:21a 37,956 0 a--- pscript.sym
    > 1-26-05 2:31p 13,347 0 a--- readme
    > Directory of E:\tmp\ps\ppd
    > 11-19-05 10:03a 56,399 0 a--- epalc190.ppd
    >
    >
    > By comparison, the 30.800 driver does work, as does the version 30.817
    > as shipped with ecs 1.2.
    >
    > I tried attaching the ea with eautil, but it complains about mismatching
    > EA sizes and refuses to do its thing.
    >
    > Any ideas on (a) how to fix this and (b) where to report it?
    >
    >

    Download it again and see if it will unpack correctly this time? Use
    the 30.817 build?

    --
    Bill
    Thanks a Million!

  3. Re: pscript driver update with PIN broken in 30.827?

    On Sat, 19 Nov 2005 04:47:43 -0600, William L. Hartzell
    wrote:
    >Sir:
    >
    >Stefan A. Deutscher wrote:
    >> Hi all,
    >>
    >> now I am trying to tell the postscript driver (30.827) about my Epson
    >> Acculaser C1900 colour postscript printer. To that end, I am using the
    >> pin.exe utility as documented in the readme file of the printer driver,
    >> together with the PPD file of the printer. This used to work with
    >> earlier versions of the ps driver. It does not now anymore.
    >>
    >> Here is the log of pin.exe, when run on the 30.827 driver.
    >>
    >> [E:\tmp\ps]PIN.EXE PPD PPD\ OUT\pscript.drv
    >> PostScript resource packaging utility version 1.00
    >> Copyright (c) IBM Corp. 2000,2001. All rights reserved.
    >> Producing Printer Device PAK
    >> reading driver extended attributes
    >> success
    >> extended attributes read
    >> checking driver version: EA item was not found
    >> fail
    >> fail



    [ snip ]

    >> By comparison, the 30.800 driver does work, as does the version 30.817
    >> as shipped with ecs 1.2.
    >>
    >> I tried attaching the ea with eautil, but it complains about mismatching
    >> EA sizes and refuses to do its thing.
    >>
    >> Any ideas on (a) how to fix this and (b) where to report it?
    >>
    >>

    >Download it again and see if it will unpack correctly this time? Use
    >the 30.817 build?


    Hi Bill,

    thanks for chiming in here! I went back to 30.817, indeed. The download
    appears to be fine - it is what ecsMNT put on my disk, and AFAIK it
    verifies it before application. I just am worried that this may be a
    degression which from now on is carried forward, so I would like to
    report it to the proper authorities ... I guess I'll send a mail to the
    Mensys folks who sold me my copy of eCS, or report a bug on the ecs web
    site.


    Cheers,
    Stefan

    >
    >--
    >Bill
    >Thanks a Million!


+ Reply to Thread