OS/2 Network Printer
                           for
                 Hewlett Packard Printers

                          README

This diskette contains an installation program which will enhance
the OS/2 print subsystem and add support for Hewlett Packard
network-attached printers.  For print clients, this will enhance
the information displayed by the OS/2 Print object and will allow
for the automatic downloading of print drivers not installed on
the OS/2 client.

For OS/2 print servers, this will replace the HP JetDirect software
that communicates with network-attached printers.  This enhancement
will allow bi-directional communications with the HP printers that
have installed network cards.

Bi-directional communications enable the following:

  - True end of job, which means that the print job
    is not removed from the OS/2 print spooler until
    the printer confirms that the job printed
    successfully.

  - Extended printer status, which includes "cover open,"
    "page printed," and "out of paper."

  - Changes to settings in a printer from a remote control panel
    application in an OS/2 host.

The following HP LaserJet printers are supported in bi-directional
mode over the network:

    HP LaserJet 4, 4V, 4Si, 4 Plus, 5Si, Color LaserJet


INSTALLING THE SOFTWARE
-----------------------
To install this program, type the following from an OS/2 command
prompt:

  A:\JETINST <sourcedrive>: <bootdrive>: <option>

      Example: A:\JETINST A: C: HP

where

<sourcedrive>  points to the drive that contains these install files.
<bootdrive>    is the OS/2 boot partition where you want to install
               this software.
<option>       can be one of the following:
               a) CLIENT   - install as a client (default)
               b) HP       - install as a print server




ENABLING OS/2 PRINTER DRIVER DOWNLOAD FOR OS/2 CLIENTS
------------------------------------------------------
The Lan administrator can set up a share to allow clients running
this update to download required print drivers from a common place.
This is useful when the print server is using a print driver that
is not yet installed on the client.  When the client creates a
network print object referencing the print server's shared print
queue, the print object will first check to see if the required
print driver has already been installed on the client.  If the driver
is not installed on the client, the print object will look in the
following places for a path to the print driver:

  1. The spooler will look in the OS2 system INI file
     for application name PM_SPOOLER_DRVSHARE.  The
     keynames for this application name will be print
     server names; the keyvalue will be the path to
     the print drivers that can be downloaded to clients.

     If the application name is found, the spooler will
     use the keyvalue for the print server requested or
     the first keyvalue if the print server requested is
     not a keyname.

     The following is an example entry for print server
     PRINTSRV on a LanServer Domain.  This assumes all
     clients have a "net use" in place for a drive that
     contains the print drivers.

     App Name                Key Name          Key Value
     ---------               ---------         ---------
     PM_SPOOLER_DRVSHARE     LS:\\PRINTSRV     X:\DRVS

  2. If no PM_SPOOLER_DRVSHARE entry exists, the print
     server will be checked for a directory share named
     PRINTDRV.

  3. If neither of the above finds a path to print drivers,
     the user's logon domain "LS:\\*ALIAS" will be checked
     for an alias name PRINTDRV.

The path returned by one of the above methods will be used by the
print object as follows:

  - Search the root of the path for packed files (*.DR_)
  - Search the root of the path for unpacked files (*.DRV)
  - Search the subdirectory OS2DRV of the path for packed
    or unpacked files
  - Search the subdirectory PMDD_n of the path, where n
    is the OS/2 printer driver diskette number and the
    subdirectory contains the OS/2 printer driver diskette
    contents

  For example, to share all OS/2 printer drivers, the
  administrator can create the following directories:

    a) D:\DRVS
    b) D:\DRVS\PMDD_1 - contains OS2 print driver diskette 1
    c) D:\DRVS\PMDD_2 - contains OS2 print driver diskette 2
    d) D:\DRVS\PMDD_3 - contains OS2 print driver diskette 3
    e) D:\DRVS\PMDD_4 - contains OS2 print driver diskette 4
    f) D:\DRVS\PMDD_5 - contains OS2 print driver diskette 5

  The administrator can then set up a share for users to the
  D:\DRVS directories.



CONNECTING A PRINT SERVER TO USE THE ENHANCED PRINTER COMMUNICATIONS
--------------------------------------------------------------------
--------------------------------------------------------------------


CREATING PRINT OBJECTS FOR YOUR NETWORK-ATTACHED PRINTERS
---------------------------------------------------------
If you do not have print objects for your network-attached
printers, create them using the printer template in the Templates
folder, but do not select an output port.

Select Settings on the print object, select the Output Port
Settings page, and select the Install New Port push button.
Follow the dialogs to create a printer port that is connected to
your network-attached printer, and then select this output port
for the print object.  You may now use this print object for
printing.


USING THE REMOTE PRINTER PANEL ON CLIENT MACHINES
-------------------------------------------------
If your print server and client are running this software and
Warp Server, users on client machines can view the current
state of the bi-directional printer by selecting the Printer
Panel menu item from the pop-up menu of the network print object.
Users see the printer status page only.


REMOTE PRINTER ADMINISTRATION ON CLIENT MACHINES
------------------------------------------------
Administrators can access the full Remote Printer Panel from client
machines just as users can, as described above.  This allows control
of printer settings just as at the server or from the printer's
physical control panel.  Administrators can access the network printer
port settings remotely from client machines.  This software plus LAN
Server 4.0 are required at the server and the client.  To access port
settings, select the Output Port page from the network print object
Settings notebook (click mouse button 2 on the object).  The
administrator can change port characteristics from the JetAdmin Port
Settings notebook.  New ports cannot be installed remotely, however.
New ports must be installed from the server.

To allow remote administration, the client machines must have access to
the port driver at the server.  This is done by one of two methods:

  1. The domain is checked for an alias PRINTDRV at the server for
     the directory that contains the HP Network Port Driver (HPPD.PDR).
     If this is the same directory used for driver distribution, the
     port driver HPPD.PDR must be in this directory.

     Or:

  2. The server will be checked for a directory share named PRINTDRV
     pointing to a directory that contains HPPR.PDR.


REDIRECTING LPT PORTS
---------------------
You can redirect an LPT port to a local print queue by using the SPOOL
command and specifying the print queue name as the output device.


RESTRICTIONS
------------
1. The OS/2 print spooler must be enabled to print to these network-
   attached printers.
2. Mixed vendor Network Printer solutions can be installed on
   an OS2 client.  Mixed vendor Network Printer solutions cannot
   be installed on a single print server.
3. This Network Printer solution must be reinstalled if the operating
   system is reinstalled.
4. The print server must have 802.2 support installed to connect
   to the network printers.