Changes between Version 1 and Version 2 of AddPpdFiles


Ignore:
Timestamp:
Oct 8, 2018, 2:51:51 PM (6 years ago)
Author:
ak120
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • AddPpdFiles

    v1 v2  
    1 The folllowing is my observations from updating the postscript drivers on eCS.
     1The following are my observations from updating the PostScript drivers on eCS.
    22
    3 The first step is to get the tools and environment setup.  I will first discuss manual process and then talk of Alex Taylor's gui interface that uses the command line tools.
     3The first step is to get the tools and environment setup. I will first discuss manual process and then talk of Alex Taylor's GUI that uses the command line tools.
    44
    55First we need to create a directory well call it pscriptdrvr here.
    6 Then we need to unpack the pscript driver package (any relatively recent
    7 pscript dirver package will have the tools for the conversion).
     6Then we need to unpack the PSCRIPT driver package (any relatively recent PSCRIPT driver package will have the tools for the conversion).
    87There should be the following files:
    9 README        - INSTALLATION INSTRUCTIONS
    10 PSCRIPT.DRV   - PSCRIPT DRIVER
    11 PSCRIPT.EA    - PSCRIPT DRIVER EAs.
    12 PSCRIPT.SYM   - PSCRIPT DRIVER SYMBOL FILE (FOR DEBUGGING ONLY)
    13 PSCRIPT.HLP   - PSCRIPT DRIVER HELP FILE
    14 PSCRIPT.LST   - LIST OF ALL DEVICES SUPPORTED
    15 PRINTER1.PAK  - PSCRIPT DRIVER DEVICE DATA
    16 PIN.EXE       - POSTSCRIPT RESOURCE IMPORTING UTILITY
    17 PIN.SYM       - SYMBOL FILE (FOR DEBUGGING ONLY) FOR PIN.EXE
    18 PPDENC.EXE    - PPD FILE ENCODING CONVERTER UTILITY
    19 PPDENC.SYM    - SYMBOL FILE (FOR DEBUGGING ONLY) FOR PPDENC.EXE
    20 
    21 Note: Exception for JP and TW drivers
    22 instead of PSCRIPT.DRV use PSCRIPT2.DRV
    23 instead of PSCRIPT.EA  use PSCRIPT2.EA
     8{{{
     9 README        - INSTALLATION INSTRUCTIONS
     10 PSCRIPT.DRV   - PSCRIPT DRIVER
     11 PSCRIPT.EA    - PSCRIPT DRIVER EAs.
     12 PSCRIPT.SYM   - PSCRIPT DRIVER SYMBOL FILE (FOR DEBUGGING ONLY)
     13 PSCRIPT.HLP   - PSCRIPT DRIVER HELP FILE
     14 PSCRIPT.LST   - LIST OF ALL DEVICES SUPPORTED
     15 PRINTER1.PAK  - PSCRIPT DRIVER DEVICE DATA
     16 PIN.EXE       - POSTSCRIPT RESOURCE IMPORTING UTILITY
     17 PIN.SYM       - SYMBOL FILE (FOR DEBUGGING ONLY) FOR PIN.EXE
     18 PPDENC.EXE    - PPD FILE ENCODING CONVERTER UTILITY
     19 PPDENC.SYM    - SYMBOL FILE (FOR DEBUGGING ONLY) FOR PPDENC.EXE
     20}}}
     21Note: Exception for JP and TW drivers instead of PSCRIPT.DRV use PSCRIPT2.DRV instead of PSCRIPT.EA use PSCRIPT2.EA
    2422If you are using these then you will need to make the substitution to the text below.
    2523
    … …  
    2826Next we want to create three folders... pre-ppd, post-ppd, and driver.
    2927
    30 Now we want to obtain the ppd files for the printer.  These may be on a cd
    31 that came with the printer, download a self executing zip (Lexmark and Xerox Phaser I know have these - I generally use Odin for these), or you may have to install from either the cd or a download onto a windows machine and then find the ppd file (I would start by looking in system32\spool).
     28Now we want to obtain the ppd files for the printer. These may be on a CD that came with the printer, download a self executing zip (Lexmark and Xerox Phaser I know have these - I generally use Odin for these), or you may have to install from either the CD or a download onto a Windows machine and then find the ppd file (I would start by looking in system32\spool).
    3229
    33 Once the ppd files are located put them in pre-ppd.  Technically they can be pulled directly from the cd for instance during this process but it is easier for this case usage to copy them over (besides I myself prefer keeping them where I know where they are).
     30Once the ppd files are located put them in pre-ppd. Technically they can be pulled directly from the CD for instance during this process but it is easier for this case usage to copy them over (besides I myself prefer keeping them where I know where they are).
    3431
    3532Note:  Gary Drag reported in the eComStation mailing list that he had to add the following to the ppd file to fix problems with RAW postscript output:
     33{{{
    3634*% === Job Control Language ==
    3735
    … …  
    3937*JCLToPSInterpreter: "@PJL ENTER LANGUAGE = Postscript <0A>"
    4038*JCLEnd: "<1B>%-12345X@PJL EOJ <0A><1B>%-12345X"
    41 
     39}}}
    4240These lines solve the problem with applications that generate RAW postscript output.
    4341
    44 Now we need to convert the encoding for OS/2 usage.  The readme says this is only needed for non-english ppd files. Currently supported PPD encoding standards are "IsoLatin1" and "WindowsANSI".  PPDENC will automatically detect encoding in PPD from which to convert. 
     42Now we need to convert the encoding for OS/2 usage. The readme says this is only needed for non-english ppd files. Currently supported PPD encoding standards are "IsoLatin1" and "WindowsANSI".  PPDENC will automatically detect encoding in PPD from which to convert. 
    4543Run ppdenc from the command line for the parameters.  For our purposes:
     44{{{
    4645ppdenc -d pre-ppd post-ppd
     46}}}
    4747This will set *LanguageEncoding to "OS2-850". 
    4848Note:  If *LanguageEncoding is already set to "OS2-850" then it will not convert the file and only copy it to post-ppd.
    4949
    50 Note:  I have seen one instance where a ctrl-z character got inserted after the LanguageEncoding: OS2-850 line and had to be removed... I could not determine why it was inserted as the other ppd files I converted did not have this problem and in that section are nearly identical except the name of the printer itself.
     50Note:  I have seen one instance where a Ctrl-Z character got inserted after the LanguageEncoding: OS2-850 line and had to be removed... I could not determine why it was inserted as the other ppd files I converted did not have this problem and in that section are nearly identical except the name of the printer itself.
    5151
    52 Now we need to copy pscript.* and printer1.pak to the driver directry we created earlier (for the actual conversion only pscript.drv is required but makes the next steps easier to copy them all).
     52Now we need to copy pscript.* and printer1.pak to the driver directory we created earlier (for the actual conversion only pscript.drv is required but makes the next steps easier to copy them all).
    5353
    5454We are now ready to actually update the postscript driver.  Run pin at the command line for parameters and usage.  For our purposes:
     55{{{
    5556pin ppd post-ppd driver\pscript.drv
    56 
     57}}}
    5758       IMPORTANT: After the resources are imported to the printer driver,
    5859       you can't just 'add' on top of that. If you add a new PPD to the
    … …  
    6263       driver again.
    6364       
    64 Note:  If you have to remove the ctrl-z or similarly had to edit the ppdenc converted file then you may want to remove the one from pre-ppd.  This is important due to the preceding in case you have to convert a new printer.  You can remove them all as well, though I like to keep them for the date so that I can see if a newer one is released.
     65Note:  If you have to remove the Ctrl-Z or similarly had to edit the ppdenc converted file then you may want to remove the one from pre-ppd.  This is important due to the preceding in case you have to convert a new printer.  You can remove them all as well, though I like to keep them for the date so that I can see if a newer one is released.
    6566
    6667Now you need to install your printer as you normally would and tell it to find the drivers in the pscriptdrv\driver directory.  If it asks to replace files tell it yes.
    … …  
    6869(and if you happen to be using a newer pscript package than what you previously had installed pscriptdrv\driver\printer1.pak) to C:\OS2\DLL\PSCRIPT (where C is of course replaced by your boot drive letter).  You may find that pscript.drv is locked, in which case you may be able to close any apps that have it locked (Citrix I know does, ae.exe might) or you can unlock it, replace it, and reboot (or just reboot may work or you may boot to command prompt).  You should now be able to access the job properties and print.
    6970
    70 Ok, now that the mechanics of what is going on is handled I will talk about the gui that Alex Taylor has created (instpdr.exe).  It uses the ppdenc and pin for you.  It also keeps track internally and saves ppd files that you have converted so that if you do so again you don't have to worry about that yourself.  It also adds the printer to the eComStation list of printers so that you don't have to locate them.
     71== InstPDR ==
    7172
    72 Its setup is like the above, unpack the postscript drivers into pscriptdrv and put instpdr.exe into this same directory.  You can either create a directory to hold ppd files as we did for the manual installation or use the gui to go out to a cd, with the gui either is about as easy as the other.  The gui guides you through the process so I will not go further from there, internally it is taking care of what is documented above.
     73Ok, now that the mechanics of what is going on is handled I will talk about the GUI that Alex Taylor has created (instpdr.exe).  It uses the ppdenc and pin for you.  It also keeps track internally and saves ppd files that you have converted so that if you do so again you don't have to worry about that yourself.  It also adds the printer to the eComStation list of printers so that you don't have to locate them.
     74
     75Its setup is like the above, unpack the postscript drivers into pscriptdrv and put instpdr.exe into this same directory.  You can either create a directory to hold ppd files as we did for the manual installation or use the GUI to go out to a CD, with the GUI either is about as easy as the other.  The GUI guides you through the process so I will not go further from there, internally it is taking care of what is documented above.