Category : OS/2 Files
Archive   : HPDJET.ZIP
Filename : INSTALL.DOC

LICENSE
-------

Please see the 'LICENSE' text file included in this package
for licensing information.

BEFORE INSTALLATION
-------------------

1. Attaching Extended Attributes

The Extended Attribute file (.EA) for the driver must be attached
to the actual driver file (.DRV) so installation of the driver
will succeed.

This is because the file compression utility does not support
Extended Attributes and essentially erases them during compression.

The .EA files are actually the Extended Attributes
separated from the files they would normally be attached to and
made to show up as files you (and the compression utility) can see.

Extended Attributes for .DRV files contain information about
what directories to create during installation and what files
go in what directory. Without the EAs on the .DRV file installation
will in most cases fail.

Restoring EAs is done by using the EAUTIL.EXE program that is part
of OS/2.

-> Use the command file provided to do this for you.
(examples: HPDJPM.CMD for the beta DeskJet printer driver
HPDJPM.DRV
EPSON.CMD for the Epson printer driver EPSON.DRV
LASERJET.CMD for the Laserjet driver LASERJET.DRV
PSCRIPT.CMD for the PostScript driver PSCRIPT.DRV
SMGXPJET.CMD for the PaintJet driver SMGXPJET.DRV
IBMNULL.CMD for the IBM Null driver IBMNULL.DRV
IBM4019.CMD for the IBM 4019 driver IBM4019.DRV
IBM42XX.CMD for the IBM 42XX driver IBM42XX.DRV
IBM52XX.CMD for the IBM 52XX driver IBM45XX.DRV
IBM52012.CMD for the IBM 52012 driver IBM52012.DRV
PLOTTERS.CMD for the IBM Plotter driver PLOTTERS.DRV)

The command file must be run from the same directory where all
the driver files were unzipped to.

You can verify that the EAs were attached successfully by doing
a "dir /n" on the .DRV file. The "/n" option on the "dir" command
causes the size of the EA on a file to appear next to each file's
name.

After the EAs are attached, the size of the .EA file should be the
same size as the EA column shown using "dir /n".

Once this is done successfully, you can proceed with printer driver
installation. When prompted by the installation panel replace
the default drive/directory (usually a:\) with the directory
you have been working in.

NOTE: If you are installing a newer version of a driver over an
older version see step #2 below.

The installation of an OS/2 Printer Driver is documented in
OS/2 2.0's online Master Help Index under the topic 'installing'
and the subtopic 'OS/2 printer drivers'.

The installation of an OS/2 Printer Object is documented in
OS/2 2.0's online Master Help Index under the topic 'Creating'
and subtopic 'Printer Object'.

2. Replacing existing drivers

The problem we face is that printer drivers, once loaded, are
loaded until a reboot occurs. We need to try and guarantee
that when we reboot the driver will not get loaded so that
we can install over it with a newer version.

If you are replacing an existing driver with the same driver there
are a few things that need to be done before installation to help
guarantee the old driver will not be loaded when we go to install
over it.

a) Wherever the driver you want to replace is the "Default
Printer Driver" for a printer object (queue) select another
driver as the default like (IBMNULL).

"Default printer driver" for a print object (queue) is found by:
i. Right mouse button on the printer object (queue),
a menu should appear.
ii. Left mouse button on the arrow to the left of menu item
"Open", a sub menu should appear.
iii. Left mouse button on the sub-menu item "Settings",
a notebook should appear.
iv. Left mouse button on the notebook tab labelled "Printer driver",
the notebook page should change.
v. You should see a window on this page labelled
"Default printer driver" where all printer drivers used
by this queue are shown.

b) "Hold" all printer objects (queues) you have installed.

"Holding" a printer object (queue) is accomplished by:
i. Right mouse button on the printer object (queue),
a menu should appear.
ii. Left mouse button on the menu item "Change status",
a sub-menu should appear.
iii. Left mouse button on the sub-menu item "Hold"
A check mark should appear next to the "Hold" sub-menu item
on subsequent accesses of this sub-menu.

c) Shut down all programs that may print.

Also, remember to remove any programs that might automatically
start upon booting from the "startup" folder or startup.cmd file
or other command files.

NOTE: This includes AES (Automatic Emulation Switching) utility
that Lexmark provides for their IBM laser printers.

d) Make sure all printer objects (queues) minimized (not showing
printer jobs in ICON view).

e) Shut down your computer to save any changes.

f) Reboot your computer. Your system should come up fresh
with no jobs printing or printing programs running and no open
print queues.

g) To verify your driver is unloaded open up any print object
and delete any device that is part of the driver you are replacing.

When you delete the last device from that driver you will be
asked if you wisj to erase the driver's files. Say "OK".

You can then manually verify that the files were deleted from
their respective directories ( \os2\dll\"drivername" directory)
before installing the new driver.

This ensures that the driver uses only the newer files and is not
a hybrid between the old and newer driver.

f) Directly following this reboot, install the new version
of the printer driver from the directory you unzipped it to.

The installation of an OS/2 Printer Driver is documented in
OS/2 2.0's online Master Help Index under the topic 'installing'
and the subtopic 'OS/2 printer drivers'.

The installation of an OS/2 Printer Object is documented in
OS/2 2.0's online Master Help Index under the topic 'Creating'
and subtopic 'Printer Object'.