
            OS/2 PRINT SUBSYSTEM PRINTER DRIVER - PSCRIPT
                     FOR OS/2 WARP 4.00 OR ABOVE

                              IMPORTANT
                              ---------
    PLEASE READ THE FOLLOWING TERMS AND CONDITIONS. DOWNLOADING
    THE DRIVER PACKAGE THAT FOLLOWS, INDICATES YOUR ACCEPTANCE 
    OF THE FOLLOWING TERMS AND CONDITIONS:

    - YOU MUST BE, AND YOU AGREE THAT YOU ARE, A PRIOR LICENSE OF OS/2
      WARP VERSION 4.00 OR ABOVE
    - YOU MAY MAKE COPIES OF THE OS/2 WARP VERSION 4.00 SERVICE FIX EQUAL TO
      THE NUMBER OF LICENSED COPIES OF OS/2 WARP VERSION 4.00 YOU POSSESS
    - YOU MAY ONLY USE THIS DRIVER PACKAGE FOR MAINTENANCE PURPOSES
    - ALL OTHER TERMS AND CONDITIONS OF YOUR OS/2 WARP VERSION 4.00 LICENSE
      AGREEMENT APPLY TO THIS DRIVER PACKAGE; HOWEVER, THIS DOES NOT EXTEND
      ANY WARRANTY OUTLINED IN SUCH AGREEMENT.


CONTENTS
--------
1.0  Introduction
2.0  Printer Driver Level
3.0  Files Included in This Driver Package
4.0  Installation
5.0  Importing PostScript Printer Description files
   5.1 Introduction
   5.2 Converting PPDs with Special Characters (Using PPDENC.EXE)
   5.3 Importing a New PPD (Using PIN.EXE)
   5.4 Using the Driver with Imported Devices in a Network Environment
6.0  Printer Devices Added Since Ver 30.797
7.0  Printer Devices Updated Since Ver 30.797
8.0  APARs Fixed Since Ver 30.797
9.0  Copyright and Trademark Information


1.0 INTRODUCTION
-----------------
This driver package provides you with IBM's most current support
for printer devices on the OS/2 Operating System.


2.0 PRINTER DRIVER LEVEL
------------------------
Current printer driver level is 30.800


3.0 FILES INCLUDED IN THIS DRIVER PACKAGE
-----------------------------------------
README        - INSTALLATION INSTRUCTIONS (THIS FILE)
PSCRIPT.DRV   - PSCRIPT DRIVER
PSCRIPT.EA    - PSCRIPT DRIVER EAs.
PSCRIPT.SYM   - PSCRIPT DRIVER SYMBOL FILE (FOR DEBUGGING ONLY)
PSCRIPT.HLP   - PSCRIPT DRIVER HELP FILE
PSCRIPT.LST   - LIST OF ALL DEVICES SUPPORTED
PRINTER1.PAK  - PSCRIPT DRIVER DEVICE DATA
PIN.EXE       - POSTSCRIPT RESOURCE IMPORTING UTILITY
PIN.SYM       - SYMBOL FILE (FOR DEBUGGING ONLY) FOR PIN.EXE
PPDENC.EXE    - PPD FILE ENCODING CONVERTER UTILITY
PPDENC.SYM    - SYMBOL FILE (FOR DEBUGGING ONLY) FOR PPDENC.EXE

Exception for JP and TW drivers

instead of PSCRIPT.DRV use PSCRIPT2.DRV
instead of PSCRIPT.EA  use PSCRIPT2.EA


4.0 INSTALLATION
----------------
Use these printer drivers as you would your original printer driver.

Method #1
---------
- Point to a printer object.
- Click Mouse Button 2.
- Select properties.
- Select the printer driver tab.
- Point to one of the printer driver objects.
- Click mouse button 2.
- Select the install / new driver.
- The "Install New Printer Driver" dialog will appear.
- Select "Other OS/2 Printer Driver" and enter the drive and/or
  directory that you have put the driver files into for the install.
- Press Refresh button.
- Select the driver to install and press Install button.
- Select Yes to replace printer driver if prompted.
- Select OK to close the "Install New Printer Driver" dialog and
  select the correct driver for the print object.
- Close print object.

Method #2
---------
- Select the printer object in the source directory.
- Pick the printer object you want to install by dragging and dropping
  onto the desktop.

You will now be ready to print using the driver.

If you need additional help installing the printer driver,
please refer to the on-line help facility.

Note 
----
If you are in a network environment, we suggest that you match printer
driver levels between both the server and the requestors.

The Font manager in the network environment is fully functional only if
downloaded fonts are available for both server and client and are in the
same directory path.


5.0 Importing PostScript Printer Description files.
---------------------------------------------------

   5.1 Introduction
   ----------------
       PostScript Printer Description (PPD) files describe the fonts, 
       paper sizes, resolution capabilities, and other features that are
       standard for your PostScript printer. 

       PPD files are used by PostScript printer drivers to determine how
       to print your document (if you do not print using the correct PPD
       file, your document may not print correctly or all of the printer's
       features may not be available when you print).

       Your printer manufacture is ultimately responsible for creating and
       providing the correct PPD file for your printer (you can usually
       find the PPD file on the floppy disk or CD-ROM included with your
       printer or visit manufactures Web site to download the PPD file you
       need, contact the customer support department of your printer
       manufacturer to find out how to obtain PPD file.)
      
       If you have a device not supported by OS/2 PostScript printer 
       driver, you can "import" a PPD file to add your device using the
       PIN.EXE utility (see section 5.3 for details).

       Upgrading devices is supported.  If you have a newer version of a PPD
       for a device that is already supported in the driver and import a newer 
       PPD, the newer version of the PPD will take precedence over the current
       device.
     
   5.2 Converting PPDs with Special Characters (Using PPDENC.EXE)
   --------------------------------------------------------------
       PPD files are usually provided in IsoLatin1 and WindowsANSI encoding,
       which are not compatible with the OS/2 code page. Of course, this
       only affects languages that make use of special characters - like
       French or Spanish. If you only use English PPDs, you will not need to
       use this utility.
    
       If PPDs are used for the languages that contain these special 
       characters, conversion of the PPD file to an OS/2 compatible codepage
       will be required before importing. Failure to do so will result in
       the display of incorrect characters in OS/2. 

       NOTE: This step needs to be completed before importing the PPDs 
       into the driver (before you copy the downloaded PPD files into 
       your PPD\ directory).

       * PPDENC can convert single file:
       >PPDENC.EXE <input_ppd_file> <output_ppd_file>

       The input file will be read and the output file will be created. 
       The output file name must be different than the input file name.

       * PPDENC can convert multiple files in one directory, writing the 
       converted files to the destination directory (directory must exist):
       >PPDENC.EXE -d <source_directory> <dest_directory>

       Files (*.PPD) in the source directory will be processed file by file
       and the output files will be created in destination directory.
    
       Currently supported PPD encoding standards are "IsoLatin1" and 
       "WindowsANSI". PPDENC will automatically detect encoding in PPD from 
       which to convert.

       When the PPD is converted, the output file will have its 
       *LanguageEncoding set to "OS2-850" to indicate that it's been 
       processed. If the PPDENC utility later sees this, it will not 
       attempt to change the encoding and will copy the file intact. 
       Similar, if the PPD encoding is not recognized, the PPD file will
       just be copied over without modification.

       PPDENC does not modify it's input files in any way.


       *** Sample scenario ***

       You have a Spanish PPD that has been downloaded from the WWW and 
       want to include it in your driver distribution. First, you need 
       to convert it to an OS/2 codepage.

       >PPDENC IsoLatin1 spanish.ppd spanish2.ppd

       This will create spanish2.ppd that will be encoded 
       in an OS/2 codepage.

       Now spanish2.ppd can be copied into your PPD directory 
       (as d:\PSDRIVER\PPD) and then you can import the PPD files into
       the PSCRIPT driver (see steps 3-6 in: 5.3 Importing a New PPD).
   
   5.3 Importing a New PPD (Using PIN.EXE)
   ---------------------------------------
       PIN.EXE is a utility to add new or upgrade device support in the
       Postscript driver by importing PPD files. The PPD file is usually
       created and provided by your PostScript printer manufacturer.

       Syntax:
       PIN.EXE <command> <arguments>

       Currently, the only supported command is "PPD".

       Syntax of command 'PPD' arguments:
       PIN.EXE PPD <path_to_directory_with_ppd_files> <path_to_driver>

       The first argument is the directory path where PPD files to be 
       imported are stored. The second argument is the path to the driver
       (including the driver file name) where the PPD files will be imported. 
       
       One or multiple PPDs can be imported at once.


       *** Suggested usage scenario ***

       1) Create directory where you will store all of the PSCRIPT files.
          >mkdir d:\PSDRIVER

       2) Put PIN.EXE in this directory.
          >copy PIN.EXE d:\PSDRIVER

       3) Create 3 subdirectories in d:\PSDRIVER directory.
          >cd d:\PSDRIVER
          >mkdir BAK
          >mkdir PPD
          >mkdir OUT

          The BAK directory will be the backup driver files - the original, 
          unmodified driver. Copy the unmodified driver files here.

          The PPD directory will contain the PPD files for your new printer 
          devices that you want imported into the driver.

          The OUT directory will be where you build your driver which contains 
          the new devices to be imported for immediate use or distribution.


       To import new devices into the driver, perform the following steps:

       4) Clean the output directory.
          >del OUT\*

       5) Copy the unmodified driver files from the backup (BAK) to the OUT 
          directory.
          >copy BAK\* OUT\

       6) Run the PIN utility to import the PPDs.
          >PIN.EXE PPD PPD\ OUT\pscript.drv

          "PPD" is command that tells PIN.EXE what to do.
          "PPD\" is path to directory with the source PPD files.
          "OUT\pscript.drv" is the driver file name where the PPDs are going to 
          be imported into.

       7) The driver in the OUT\ directory now will have the imported PPDs!


       You can install it (as specified above (see: section 4.0 INSTALLATION)) 
       or distribute it to users.

       IMPORTANT: After the resources are imported to the printer driver,
       you can't just 'add' on top of that. If you add a new PPD to the 
       directory and want to make use of it, you have to start with a "fresh"
       driver and import all of the devices at once, as previously done.
       It is required that you delete all of the files in the output 
       directory (step 3) and copy the driver from the backup directory
       (step 4) to perform device importing - every time.

   5.4 Using the Driver with Imported Devices in a Network Environment
   -------------------------------------------------------------------
       There is a known problem with updating drivers in a network 
       environment. If you put the driver with imported PPDs on a print
       server, and distribute it to requesters, then upgrade the server 
       with the same driver with some new PPDs imported, the new devices
       will not be automatically distributed to requesters.

       This is an issue with the code that implements automatic network 
       update. We are currently working on a solution.

       For now, if you update the driver (import new PPDs) you will have to
       distribute the updated driver to clients by some other means.


6.0 PRINTER DEVICES ADDED SINCE Ver 30.797
------------------------------------------
HP Business InkJet 2300 PS
HP Color LaserJet 3700 PS
HP LaserJet 1300 Series PS
Kyocera Mita FS-1020D (KPDL)
Kyocera Mita FS-C5016N (KPDL)
Kyocera Mita KM-1510 (KPDL)
Kyocera Mita KM-1530 (KPDL)
Kyocera Mita KM-1810 (KPDL)
Kyocera Mita KM-2030 (KPDL)
Kyocera Mita KM-2530 (KPDL)
Kyocera Mita KM-4030 (KPDL)
Kyocera Mita KM-4530 (KPDL)
Kyocera Mita KM-5530 (KPDL)
Kyocera Mita KM-6330 (KPDL)
Kyocera Mita KM-7530 (KPDL)
Kyocera Mita KM-C850 (KPDL)
Minolta-QMS Magicolor 3300
Minolta-QMS Magicolor 7300
Minolta-QMS Magicolor 7300 Mono


7.0 PRINTER DEVICES UPDATED SINCE Ver 30.797
--------------------------------------------
None


8.0 APARs FIXED SINCE Ver 30.797
--------------------------------
None


9.0 COPYRIGHT AND TRADEMARK INFORMATION    
---------------------------------------
The following terms are trademarks of International Business Machines
Corporation in the United States and/or other countries:

     IBM
     LAN Distance
     OS/2
     ThinkPad
     Ultrabay
     WIN-OS/2
     WebSphere

Other company, product, and service names may be trademarks or service
marks of others.

THE INFORMATION PROVIDED IN THIS README IS PROVIDED "AS IS" WITHOUT 
WARRANTY OF ANY KIND. IBM DISCLAIMS ALL WARRANTIES, WHETHER 
EXPRESSED OR IMPLIED, INCLUDING WITHOUT LIMITATION, THE IMPLIED 
WARRANTIES OF FITNESS FOR A PARTICULAR PURPOSE AND MERCHANTABILITY 
WITH RESPECT TO THE INFORMATION IN THIS DOCUMENT. BY FURNISHING
THIS DOCUMENT, IBM GRANTS NO LICENSES TO ANY PATENTS OR COPYRIGHTS.

(C) Copyright IBM Corporation 1990, 2003. All rights reserved.
U.S. Government Users Restricted Rights -- Use, duplication or 
disclosure restricted by GSA ADP Schedule Contract with IBM Corp.