 HP Network Peripheral Port Monitor Software

 COPYRIGHT (c) HEWLETT-PACKARD COMPANY 1993.  ALL RIGHTS RESERVED.
 11311 Chinden Boulevard
 Boise, Idaho  83714


* * * * * * * * * * * * * *  R E A D M E . T X T  * * * * * * * * * * * * * *


- Configuration parameters in SYSTEM.INI

    There are a number of parameters in the [HP Network Ports] section of
    SYSTEM.INI that can be changed.

    MAXNUMPORTS
        This parameter determines the maximum number of network ports you
        may have on your system at one time.  The default number is 5.
        If you wish to configure more ports on your system, you need to
        increase this number.

    MAXNUMBUFFERS
        This parameter determines how many buffers are allocated for use
        by the DLC protocol stack.  Buffers are used for both printing and
        receiving printer status.  The default number is 15.  If you have
        only a few ports configured (1-3) AND you don't print to more than
        one at a time, you might want to reduce this number and save
        some memory.  Try values between 8 and 12.  It is not recommended
        that you use a value below 8.

        If you have a large number of ports configured (more than 8) OR you
        print to more than two ports at the same time, you will probably
        want to increase this value for better performance.  Values in the
        range 20-25 should be sufficient.



- Setting Print Spooler timeouts in WIN.INI

    If you're using the Peer-to-Peer network printing model, you may wish
    to increase the default Transmission Retry timeout of the Network
    Peripheral Port.  The default is 45 seconds.  Look for the section
    labeled [PrinterPorts] in the WIN.INI file.  You will find a line that
    looks like this:

    HP LaserJet IIISi=HPPCL5MS,NET1:,15,45

    where NET1: is the name of the port you defined in HP Network Port
    Monitor.  Change the default of 45 seconds to the new timeout value. A
    value of 300 seconds (5 minutes) should be good.  This should change the
    above line to look like this:

    HP LaserJet IIISi=HPPCL5MS,NET1:,15,300

    Increasing this value gives the network software more time to try to
    access the peripheral before Print Manager gives up.  If Print Manager
    is reporting problems printing to a device because the device is
    already in use by another user, then increasing this value will help.



- Waiting for printers to report their LAN Hardware Address

    If there are a large number of JetDirect cards on your network
    (greater than 15), it may take a few moments for any particular net-
    work address to appear in the Card Address field of the "Add a
    Network Peripheral Port" dialog box.  If you can't find the address
    you are looking for, wait a few minutes (leaving the dialog box
    up) and then look again.

    Additionally, you can increase the MAXNUMBUFFERS parameter in
    SYSTEM.INI which will allow more card addresses to be accepted (see
    the "Configuration parameters in SYSTEM.INI" section of this file
    for more information).



- Deinstalling the software

    1) First, delete all ports that have been configured using the HP
       Network Port Monitor program.

    2) Deinstall the DLC.  To do this, run the Control Panel application
       and use the Network applet.

    3) After deinstalling the DLC, remove all the files in the HP Network
       Port Monitor directory where (the default directory is C:\HPNETPRN.W4W).

    4) Remove the following files from your Windows for Workgroups system
       directory (the default directory is C:\WINDOWS\SYSTEM):

                              HPNPMAPP.CPL
                              HPVNPD.386
                              CTL3D.DLL

    5) Remove the [HP Network Ports] section from SYSTEM.INI.

    6) Finally, reboot your system.



- Working with Novell Netware

    If you are using Windows for Workgroups on a Novell Netware network,
    it is recommended that you use Hewlett-Packard's JetPrint utility
    instead of Monitor.  You should find JetPrint in the same disk pack
    in which Monitor came.



- Working with OS/2 (connection states)

    The HP Monitor software has adopted a model where a connection is estab-
    lished with the remote peripheral, data is transferred, and the con-
    nection is dropped.  If another system has a connection to
    the peripheral, Print Manager will continue to retry the connection until
    it gives up (see the "Setting Print Spooler timeouts in WIN.INI"
    section of this file for more information).

    However, currently released versions of the HP network software for OS/2
    LAN Manager and LAN Server use a different model.  They establish the
    connection to the remote peripheral at initialization time and never drop
    it.

    This means an OS/2 system may establish a connection to a peripheral
    and the Windows for Workgroups system will never be able to break that
    connection or print.

    To avoid this, make sure an OS/2 system and a Windows for Workgroups
    system running Monitor never configure the same peripheral (that is
    they are not using the same card address).



- Error log grows without bounds

    The error log maintained by Monitor is not limited in size.  Any
    new errors are always appended to the end of the existing error log
    file.  Thus, it is possible (although improbable) that you may run
    out of disk space if the error log gets too big.  It is recommended
    that you occasionally clear the error log to avoid the possibility
    of this happening.

    Information on how to clear the error log can be found in your
    manual or in the online help for Monitor.



- Starting network before running Windows for Workgroups masks DLC

    In version 3.1 of Windows for Workgroups, if you start the networking
    software before loading Windows (by typing "net logon" for example),
    the DLC protocol stack will be hidden.  Thus, once Windows is started you
    will not be able to print, and Monitor will report that HPVNPD.386 is
    not loaded.



- Running out of buffers, "Unknown" status

    It is possible that while printing, the DLC will temporarily run out
    of DLC buffers.  This may cause a status of "UNKNOWN" to appear in
    Monitor for some ports.

    The problem should only occur when there are a large number of ports
    configured, or you are printing to more than one port at a time.  Once
    printing has finished Monitor should resume reporting status correctly.

    If you are frequently seeing this problem, it means you probably need to
    increase you MAXNUMBUFFERS parameter in SYSTEM.INI.  See the "Configur-
    ation parameters for SYSTEM.INI" section of this file for more infor-
    mation.



- Disabling the 3D interface

    If you wish to remove the 3D interface to Monitor, add the following
    line to the HPCFG.INI file (usually located in C:\HPNETPRN.W4W):

    Use3D=0

    You might want to do this on certain LCD or other monochrome monitors.



- Status messages

    Monitor has the ability to report the following status messages:

    Offline
        The peripheral is offline.  The peripheral must be online to
        continue.

    Paper Out
        The peripheral has run out of print media.  Add more media
        (e.g. paper, envelopes, etc.) to the peripheral in order to continue.

    Manual Feed Required
        The peripheral requires a manual paper feed.  Insert the
        correct media into the manual feed area to continue.

    Paper Jam
        The peripheral has a paper jam.  Clear the jam to continue.

    Toner Low
        The peripheral has a toner low condition.  The peripheral
        may continue to operate, but output quality may suffer.

    No Toner
        The peripheral has no toner.  The peripheral requires the
        proper printing toner be inserted in order to continue.

    Page Punt
        The peripheral lost a page because data was not received
        fast enough to keep up with the print engine.

    Memory Out
        The peripheral does not have enough memory to generate the
        desired output.

    Processing
        The peripheral is processing data.

    Initializing
        The peripheral is initializing.

    Warming Up
        The peripheral is warming up.

    Door Open
        The peripheral's door is open.  The peripheral's door must
        be closed to continue.

    Printing
        The peripheral is currently printing a job.

    Output Full
        The peripheral's output bin is full.  Clear the peripheral's
        output bin to continue.

    Not Available
        The peripheral is not available.  This condition generally
        arises when another system has obtained ownership of the peripheral.

    Paper Problem
        The peripheral has a paper problem such as paper out.
        Correct the problem to continue.

    Ready
        The peripheral is ready to accept data.

    Unknown
        The state of the peripheral cannot be determined.  Check
        that the peripheral is turned on and properly connected to the
        network.



- Receiving status from different peripherals

    Many peripherals do not have the ability to report the entire set of
    status messages listed in the "Status Messages" section.

    In general, the HP LaserJet 4 and LaserJet 4Si are able to report
    all of them.  Other peripherals may report only a subset of the
    available status messages.  For example, the LaserJet IIISi can only
    report Offline, Paper Out, and other simple status messages.



- Using Monitor with older JetDirect cards

    HP Monitor will work fine with older versions of the JetDirect card
    (those that support only one protocol per card).  You should have
    no difficulty adding ports and printing.

    Older cards, however, cannot report the full set of status
    messages listed in the "Status Messages" section.  The only ones
    older cards will report are:  Offline, Paper Out, Ready, Unknown, Not
    Available, and Printing.




