
--------------------------------------------------------------
Changes to HP JetAdmin and JetPrint Utilities:
Version A.01.10 to A.01.11
--------------------------------------------------------------
[] JetAdmin - NDS Context configuration when the tree has
              a country context specified would result in
              an incorrect context being saved in the
              JetDirect card.

[] JetAdmin - JetAdmin is added to the NWAdmin "Tools" menu
              automatically now to allow running JetAdmin 
              from NWAdmin.

[] JetPrint - JetPrint if left open would cause the PC to hang
              upon exiting Windows forcing a reboot.

--------------------------------------------------------------
Notes on installing the HP JetAdmin and JetPrint Utilities:
--------------------------------------------------------------

Install.exe is a DOS application.

To INSTALL Hewlett-Packard's Network Printing software, type:
    A:\INSTALL <Enter>

400K of free conventional memory is required to run INSTALL.

If you have problems installing from a OS2, Windows NT, or
Chicago client try installing from a DOS client instead.


------------------------------------------------------
Notes on the Windows version of JetAdmin and JetPrint:
------------------------------------------------------

The Windows  version of JetAdmin and JetPrint  can be run over the
NETX  or VLM shells.  In order for the required networking modules
to  initialize, the Windows  client must be  configured for Novell
NetWare in the network selection (within SETUP.EXE).

For NETX shells you must  configure  the  network  setting  to  be
"Novell NetWare shell versions 3.26 and above".

For VLM shells you  must  configure  the  network  setting  to  be
"Novell NetWare shell versions 4.x".


1.  To use JetAdmin in Windows, from the Windows program manager:
             Select  the pull-down menu FILE
             Choose  Run...
             Type    JETADMIN  <Enter>

2.  To use JetPrint, from the Windows program manager:
             Select  the pull-down menu FILE
             Choose  Run...
             Type    JETPRINT  <Enter>


-------------------------------------
Notes on the DOS version of JetAdmin:
-------------------------------------

The  DOS version can also use NETX or VLM shells.  You may use ODI
LAN drivers or older-style IPX.COM drivers.

When used  under DOS, JetAdmin requires  400K of free conventional
memory.


1.  To use JetAdmin in DOS graphics mode, from the DOS prompt type:
             JETADMIN <Enter>

2.  To use JetAdmin in text mode, from the DOS prompt type:
             JETADMIN /T <Enter>


----------------------------------------------------------------
Notes on running JetAdmin and JetPrint in Windows Standard Mode:
----------------------------------------------------------------

When used  under Windows  JetPrint and  JetAdmin require  that the
latest NetWare drivers be installed and configured correctly.

The following trouble-shooting steps should be followed:

    1) Be sure that IPX.COM (version 3.10 or higher)
       or equivalent is loaded.  With ODI use IPXODI.COM
       version 1.20 or higher.

    2) Be sure that NETX.COM (version 3.26 or higher)
       or equivalent is loaded.

!!  3) Be sure that TBMI2.COM (version 2.1 or higher)
       if operating under Standard mode of Windows,
       not required for Enhanced mode.

    4) Be sure that Windows is configured for NetWare
       "shell versions 3.26 or above" with SETUP.EXE

(See NETWORKS.WRI from the Windows 3.1 installation for additional
details.)



----------
Platforms:
----------

JetPrint and JetAdmin have been tested on the following clients:

    Windows 3.1
    Windows 3.11
    Windows for Workgroups 3.1
    Windows for Workgroups 3.11
    OS/2 2.11
    Chicago
    Windows NT 3.5 (Driver Download not Supported)


JetPrint and JetAdmin have been tested on the following servers:

    NetWare 2.12, 2.15, 2.20
    NetWare 3.11, 3.12
    NetWare 4.x
        Queue Server mode is supported in NetWare 4.x
        Bindery Emulation mode only.

        NDS (NetWare Directory Services) is supported through
        Remote Printer mode only.


-------------------------------------------
Customizing JetAdmin and JetPrint behavior:
-------------------------------------------

JetAdmin  and JetPrint have a number of customizable INI settings.
The settings and  the possible  values are  described in  the file
JETSET.TXT.  This file is located at:

        (target directory)\HP_PRINT\JETSET.TXT

It is installed with the rest of the support files.


----------------------
Freeing up disk space:
----------------------

JetAdmin and JetPrint  are  installed  with  support  for  several
languages.    If  your  environment  only  requires  English  (for
example), you can delete the unneeded files.  The files are listed
in PACKING.LST on Diskette #1.


---------------
Error messages:
---------------

Segment Load Failure:
There have been reported problems in some environments concerning
a "Segment Load Failure".  If you experience this, attempt to
restart JetAdmin or JetPrint.  The problem is believed to be
related to the version of Windows, it is sporadic and will NOT
cause the client to lose data.


"Black Screen of Death:"
If  you should experience problems where the screen suddenly turns
black and the system locks up, download the latest NetWare drivers
from  Novell's NetWire forum on CompuServe.   The "Black Screen of
Death"  is the result of several  defects in NetWare and Microsoft
code.   These  problems have  been corrected  in the  new drivers.
Refer  to the file  DEADLOCK.TXT in the  DOSUPx.EXE and WINUPx.EXE
files.


JetPrint Drag-and-Drop problems:
If you experience problems using drag and drop with multiple files
you should try the following:

    Turn off the Print Manager.  The steps to do this are as
    follows:

        - Run Control Panel.
        - Double-Click on the Printers icon.
        - Insure that the "Use Print Manager" check box does not
          have a check in it.

    Doing this will eliminate use of the Print Manager which  will
    additionally increase performance for network printing.


----------------
Driver versions:
----------------

If you experience problems  running  JetAdmin  or  JetPrint  under
Windows, examine  the NetWare  components to  ensure that  you are
running the latest versions.

New   drivers  are  available  from   Novell's  NetWire  forum  on
CompuServe.


C> VERSION TBMI2.COM
TBMI2.COM:    ..
   Version Task Switched Buffer Manager for IPX/SPX  v3.14 (930603) 

   (C) Copyright 1990-1993 Novell, Inc.  All Rights Reserved.

   Checksum is 11101.

C> VERSION VIPX.386
VIPX.386:     ..
   Version :
VIPX.386 Version 1.18 (940119) 
(C) Copyright 1993 Novell, Inc.


C> VERSION VNETWARE.386
VNETWARE.386: .
   Version 2.03 (931119)
   (C) Copyright 1989-1993 Novell, Inc.  All rights reserved.
   Checksum is 25A1.

C> VERSION NETWARE.DRV
NETWARE.DRV:  ........
   Version 2.02  (921026)
   (C) Copyright 1989-1992 Novell, Inc.  All rights reserved.
   Checksum is 3E106.

C> VERSION NWIPXSPX.DLL
NWIPXSPX.DLL: ...
   Version 4.05 NWIPXSPX.DLL Client SDK 1.05
   (c) Copyright 1990-1994 Novell, Inc.  All rights reserved.
   Checksum is DD6C.

C> VERSION NWNETAPI.DLL
NWNETAPI.DLL: .......
   Version  1.30 NWNETAPI.DLL
    (c) Copyright. 1990,1991 Novell, Inc.  All rights reserved.
   Checksum is 6C705.

C> VERSION NWPSERV.DLL
NWPSERV.DLL:  ..
   Version  1.30 NWPSERV.DLL
    (c) Copyright. 1990,1991 Novell, Inc.  All rights reserved.
   Checksum is 191F3.




==================================================================
Final Release Notes for JetAdmin (A.01.05) and JetPrint (A.01.05):
==================================================================


1.  If you attempt to install the software to the file server
    and receive an error message indicating invalid access rights,
    insure that you are logged into the destination server in
    addition to having NETX (or VLM) loaded.

2.  There is now a way to set the timeout interval for the capture that 
    JetPrint performs.  By default, the timeout interval will be 0 seconds.
    To change this add a Timeout=n, where n is the interval in seconds, to the 
    JETPRINT.INI file in the Windows directory.  This entry should appear 
    under the [JetPrint] section in the file.  This will eliminate problems
    when printing from DOS apps under Windows with JetPrint.

    [JetPrint]
    :
    :
    Timeout=30    ;sets the timeout value to 30 for each capture that JetPrint does
    :


-------------------------------
JetAdmin Notes for NetWare 4.0:
-------------------------------

    JetAdmin requires the NetWare user group EVERYONE for granting
    access to printers, queues and print servers that are created
    by JetAdmin.  If the group does not exist (common in NetWare
    4.0 servers), JetAdmin will create that group and fill it with
    the users that are visible through NetWare 4.0's Bindery
    Emulation.

    By logging into the NetWare 4.0 Directory Tree as ADMIN, the
    user may not be visible in the bindery context, and may not
    have sufficient rights to print test jobs or to get print
    queue status.  To correct the problem, add the ADMIN user to
    the group EVERYONE previously created by JetAdmin.

    Early versions of the VLM software affect the performance
    and behavior of JetPrint and JetAdmin.  Please use the
    the latest VLM software, Windows drivers and DLLs.  The
    lastest VLM software is at version v1.11.


------------------------------------------------
Known Problems with Novell's PSERVER.NLM v4.0.0:
------------------------------------------------

    The initial release of Novell's Print Server NLM (v4.0.0)
    contains a defect that prevents the print server from
    communicating configuration information back to JetPrint and
    JetAdmin.  The print server does not yet respond to queries
    for Bindery Emulation information and only supports Directory
    Service calls.  It is expected that Novell will soon provide
    an update to the print server that resolves these problems.

    This problem has the following side effects:


In JetAdmin:

    The print server is unable to provide information about the
    print queues being serviced by the print server.  This
    prevents JetAdmin from associating Windows printer drivers
    with the print queue, preventing JetPrint driver downloads.
    This also prevents JetAdmin from acquiring printer slot names
    and printing test pages.


In JetPrint:

    JetPrint is unable to get the printer slot name configured for
    the queue.  The result is that the printer name will appear as
    "Unknown Printer" in the description box.  This will also
    result in a loss of Print Server status, with JetPrint
    defaulting to Queue status for queues configured for Print
    Server slots.
