OS/2 Professional

home *** CD-ROM | disk | FTP | other *** search

/ OS/2 Professional / OS2PRO194.ISO / os2 / driver / printer / jetdir / readme < prev next >

Wrap

Text File | 1993-10-28 | 37.7 KB | 839 lines

╔═══════════════════════════════════════════════════════╗ ║ ║ ║ Hewlett-Packard* JetDirect* ║ ║ ║ ║ README ║ ║ ║ ║ Copyright 1991, 1992, 1993 All Rights Reserved ║ ║ ║ ╚═══════════════════════════════════════════════════════╝ Please review this document before installing the Hewlett-Packard JetDirect Network Printer Interface (NPI) software on your file server. It contains updated information not included in the manuals. Table Of Contents 1.0 Supported Configurations 2.0 Feature Profile Adjustments 3.0 Error Log file format and HP* JetDirect NPI HPREDIR.EXE output format 4.0 Spooler Commands 5.0 Printer Drivers 6.0 Server Hardware 7.0 Server Software 8.0 Locally Administered Addressing 9.0 Banner Pages 10.0 Plotter Test File 11.0 Defect Notice 12.0 Ordering Documentation 13.0 If you have problems 14.0 Trademarks and Service Marks ********************************************************************* * * 1.0 Supported Configurations * ********************************************************************* Certain configurations of IBM** OS/2**, IBM LAN Server**, and Microsoft LAN Manager** are required in order for the HP JetDirect NPI software to work properly. - IBM LAN Server Version 1.3 and IBM OS/2 1.3 EE Users * IBM OS/2 1.3 CSD 5050 must be applied. Note: This can be checked by typing SYSLEVEL at a OS/2 Command Prompt and checking the current CSD level of the OS/2 Base Operating System. - IBM LAN Server Version 2.0 and IBM OS/2 1.3 (Not EE) Users * IBM OS/2 1.3 CSD 5050 must be applied. Note: This can be checked by typing SYSLEVEL at a OS/2 Command Prompt and checking the current CSD level of the OS/2 Base Operating System. - IBM LAN Server Version 2.0 and IBM OS/2 2.0 Users * Boot drives other the C: are supported * If IBM OS/2 2.0 CSD XR06055 is applied, then IBM OS/2 2.0 APAR PJ08196 must be applied. * IBM LAN Server (LAPS) APAR fix JR06399 must be applied. * IBM LAN Adapter and Protocol Support (LAPS) for IEEE 802.2 must be installed. Note: LAPS is packaged with LAN Server 2.0. During the install of LAPS the IEEE 802.2 Protocol must be selected to be installed. - IBM LAN Server Version 2.0 and IBM OS/2 2.1 Users * Boot drives other the C: are supported * IBM LAN Server (LAPS) APAR fix JR06399 must be applied. * IBM LAN Adapter and Protocol Support (LAPS) for IEEE 802.2 must be installed. Note: LAPS is packaged with LAN Server 2.0. During the install of LAPS the IEEE 802.2 Protocol must be selected to be installed. - IBM LAN Server Version 3.0 and IBM OS/2 2.0 Users * Boot drives other the C: are supported * IBM LAN Server (LAPS) APAR fix JR06399 must be applied. * If IBM OS/2 2.0 CSD XR06055 is applied, then IBM OS/2 2.0 APAR PJ08196 must be applied. * IBM LAN Adapter and Protocol Support (LAPS) for IEEE 802.2 must be installed. Note: LAPS is packaged with LAN Server 3.0. During the install of LAPS the IEEE 802.2 Protocol must be selected to be installed. - IBM LAN Server Version 3.0 and IBM OS/2 2.1 Users * IBM LAN Server (LAPS) APAR fix JR06399 must be applied. * Boot drives other the C: are supported * IBM LAN Adapter and Protocol Support (LAPS) for IEEE 802.2 must be installed. Note: LAPS is packaged with LAN Server 3.0. During the install of LAPS the IEEE 802.2 Protocol must be selected to be installed. - Microsoft LAN Manager Version 2.1, 2.1a, or 2.2 and Microsoft OS/2 1.3 * RemoteBoot protocol must be installed. Note: RemoteBoot is installed from LAN Manager Setup. RemoteBoot provides the IEEE 802.2 protocol. IMPORTANT: To obtain IBM CSDs and APARs contact your IBM Service representative. ********************************************************************* * * 2.0 Feature Profile Adjustments * ********************************************************************* The information provided about changing network parameters is provided for convenience only, for more up to date information or for details about changing network parameters, see your IBM LAN Server or Microsoft LAN Manager network administrator guides. ┌──────────────────────────────────────┬─────────────────────────────────────┐ │ Running HP JetDirect NPI │ Increase IEEE 802.2 SAPs by 1, and │ │ │ IEEE 802.2 Link Stations by 18. │ │ │ *See Note 1. │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ HP JetDirect NPI SETUP.EXE or │ Increase IEEE 802.2 SAPs by 1, and │ │ HPREDIR.EXE fails with "Could not │ IEEE 802.2 Link Stations by 18. │ │ open a SAP. Increase the number of │ *See Note 1. │ │ SAPs in you network configuration, │ │ │ reboot, and try again. │ │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ Heavy Network Utilization (>60%) or │ Increase IEEE 802.2 T1 timer │ │ Printer(s) is/are configured across │ to 35, and IEEE 802.2 T2 timer │ │ bridge(s) from the print server │ to 5. *See Note 2. │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ HPREDIR.EXE cannot open the Network │ Increase the maximum number of │ │ adapter. │ users by 3. *See Note 3. │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ Want to support multiple │ Increase 'maxthreads' by 20 │ │ Network Printers with the HP │ *See Note 4. Under OS/2 1.3,increase│ │ JetDirect NPI │ 'maxchdevjob' by 6, 'maxchdevq' by │ │ │ 2,and 'maxchdevs' by 2. *See Note 5.│ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ Adding a printer from HP JetDirect │ Increase maxthreads by 20 │ │ NPI SETUP.EXE fails with a Error Log │ *See Note 4. │ │ file entry "Unable to create thread. │ │ │ Reboot server and/or change maximum │ │ │ number of threads." │ │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ Error message SYS0071 is displayed │ Under OS/2 1.3,increase │ │ during execution of the HP JetDirect │ 'maxchdevjob' by 6, 'maxchdevq' by │ │ NPI │ 2,and 'maxchdevs' by 2. *See Note 5.│ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ If MOST jobs are very large │ Increase numbigbuf by 5. │ │ (1MB or >) │ *See Note 6. │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ If MOST jobs are small and many │ Increase numreqbuf by 15. │ │ users print simultaneously │ *See Note 7. │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ If there are problems sharing │ See your IBM LAN Server or │ │ printers from the server │ Microsoft LAN Manager │ │ │ network adminstrator guides │ ├──────────────────────────────────────┼─────────────────────────────────────┤ │ If there are problems using │ See your IBM LAN Server or │ │ printers from a requester │ Microsoft LAN Manager │ │ │ network adminstrator guides │ └──────────────────────────────────────┴─────────────────────────────────────┘ Note 1: HPREDIR.EXE is an IEEE 802.2 application which requires one Service Access Point (SAP) to communicate with the network. The number of SAPs may need to be increased on the server. For IBM LAN Server 1.3, this is done in the LAN feature profiles within the Communications Manager. The field that needs to be changed is 'Maximum number SAPs' in the IEEE 802.2 Token-Ring Profile for Token Ring or the ETHERAND Network Profile for Ethernet. For IBM LAN Server 2.0 and 3.0, this is done in the LAN Adapter and Protocol Support utility. The field that needs to be changed is 'Maximum SAPs' in the IEEE 802.2 Profile. For IBM LAN Server 2.0 or 3.0 this can also be done in the PROTOCOL.INI file. The field that needs to be changed is 'MAX_SAPS' under the [LANDD_nif] section of PROTOCOL.INI. For Microsoft LAN Manager, this is done in the PROTOCOL.INI file. The field that needs to be changed is 'SAPS' under the [COMTKR_xif] section of PROTOCOL.INI. HPREDIR.EXE supports up to twelve printers on each OS/2 2.0 or 2.1 server and up to seven for OS/2 1.3 servers. 18 LINK STATIONS are required for the HP JetDirect NPI. For IBM LAN Server 1.3, this is done in the LAN feature profiles within the Communications Manager. The field that needs to be changed is 'Maximum link stations' in the IEEE 802.2 Token-Ring Profile for Token Ring or the ETHERAND Network Profile for Ethernet. For IBM LAN Server 2.0 and 3.0, this is done in the LAN Adapter and Protocol Support utility. The field that needs to be changed is 'Maximum Link Stations' in the IEEE 802.2 Profile. For IBM LAN Server 2.0 or 3.0 this can also be done in the PROTOCOL.INI file. The field that needs to be changed is 'LINKS' under the [LANDD_nif] section of PROTOCOL.INI. For Microsoft LAN Manager, this is done in the PROTOCOL.INI file. The field that needs to be changed is 'STATIONS' under the [COMTKR_xif] section of PROTOCOL.INI. IMPORTANT: Both the SAPs and LINK STATION changes must be done PRIOR to installing the Network Printer Interface software. See IBM LAN Server or Microsoft LAN Manager network administrator guides for more information. IMPORTANT: DO NOT Increase any other protocol's SAPs or LINK STATIONS, such as NETBIOS, as this will nullify the increase done for IEEE 802.2. If problems persist after increasing the number of SAPs, then make sure that IEEE 802.2 has at least 1 more SAP and 18 more Link Stations than any other protocol. Note 2: Under heavy network load (>60% utilization) or when printer(s) are configured across bridges from the print server, it may be necessary to increase the IEEE 802.2 T1 and T2 timers. For IBM LAN Server 1.3, this is done in the LAN feature profiles within the Communications Manager. The fields that needs to be changed are 'Group 1 response timer (T1)' and 'Group 1 acknowledgment timer (T2)' in the IEEE 802.2 Token-Ring Profile for Token Ring or the ETHERAND Network Profile for Ethernet. For IBM LAN Server 2.0 and 3.0, this is done in the LAN Adapter and Protocol Support utility. The fields that needs to be changed are 'Group 1 Response Timer - T1' and 'Group 1 Acknowledgment Timer - T2' in the IEEE 802.2 Profile. For IBM LAN Server 2.0 or 3.0 this can also be done in the PROTOCOL.INI file. The fields that need to be changed are 'T1_TICK_G1' and 'T2_TICK_G1' under the [LANDD_nif] section of PROTOCOL.INI. For Microsoft LAN Manager, this is done in the PROTOCOL.INI file. The fields that need to be changed are 'T1_TICK_ONE' and 'T2_TICK_ONE' under the [COMTKR_xif] section of PROTOCOL.INI. Note 3: The maximum number of users for the IEEE 802.2 protocol may need to be increased to allow HP JetDirect NPI HPREDIR.EXE to open the Network adapter through the IEEE 802.2 protocol. This parameter specifies how many applications may open the adapter through the IEEE 802.2 protocol at the same time. For IBM LAN Server 1.3, this is done in the LAN feature profiles within the Communications Manager. The field that needs to be changed is 'Maximum number of users' in the IEEE 802.2 Token-Ring Profile for Token Ring or the ETHERAND Network Profile for Ethernet. For IBM LAN Server 2.0 and 3.0, this is done in the LAN Adapter and Protocol Support utility. The field that needs to be changed is 'Maximum Number of Users' in the IEEE 802.2 Profile. For IBM LAN Server 2.0 or 3.0 this can also be done in the PROTOCOL.INI file. The field that needs to be changed is 'USERS' under the [LANDD_nif] section of PROTOCOL.INI. For Microsoft LAN Manager, this is done in the PROTOCOL.INI file. The field that needs to be changed is 'USERS' under the [COMTKR_xif] section of PROTOCOL.INI. Note 4: The 'maxthreads' parameter sets the maximum threads that can use the network simultaneously. HP JetDirect NPI HPREDIR.EXE will use a maximum of 20 threads. HP JetDirect NPI SETUP.EXE uses four threads plus the main process thread. For IBM LAN Server 1.3, this is done in the IBMLAN.INI. The field that needs to be changed is 'maxthreads' under the [requester] section of IBMLAN.INI. For IBM LAN Server 2.0 and 3.0, this is done in the IBMLAN.INI. The field that needs to be changed is 'maxthreads' under the [requester] section of IBMLAN.INI. For Microsoft LAN Manager, this is done in the LANMAN.INI file. The field that needs to be changed is 'maxthreads' under the [requester] section of LANMAN.INI. Note 5: The 'maxchdevjob' parameter specifies the maximum number of requests the server can accept for all serial queues combined. The 'maxchdevq' parameter specifies the maximum number of shared serial device queues. The 'maxchdevs' parameter specifies the maximum number of shared serial devices. These parameters may need to updated when a user wants to support multiple printers on a print server. IMPORTANT: These parameters will ONLY have an effect in an OS/2 1.3 environment. For IBM LAN Server 1.3, this is done in the IBMLAN.INI. The fields that need to be changed are 'maxchdevjob', 'maxchdevq' and 'maxchdevs' under the [server] section of IBMLAN.INI. For IBM LAN Server 2.0 and 3.0, this is done in the IBMLAN.INI. The fields that need to be changed are 'maxchdevjob', 'maxchdevq' and 'maxchdevs' under the [server] section of IBMLAN.INI. For Microsoft LAN Manager, this is done in the LANMAN.INI file. The field that need to be changed are 'maxchdevjob', 'maxchdevq' and 'maxchdevs' under the [server] section of LANMAN.INI. Note 6: The 'numbigbuf' parameter specifies the number of 64KB buffers the server uses for moving large files or large amounts of data. This parameter gets increased to improve server performance in moving big files. For IBM LAN Server 1.3, this is done in the IBMLAN.INI. The field that needs to be changed is 'numbigbuf' under the [server] section of IBMLAN.INI. For IBM LAN Server 2.0 and 3.0, this is done in the IBMLAN.INI. The field that needs to be changed is 'numbigbuf' under the [server] section of IBMLAN.INI. For Microsoft LAN Manager, this is done in the LANMAN.INI file. The field that needs to be changed is 'numbigbuf' under the [server] section of LANMAN.INI. Note 7: The 'numreqbuf' parameter specifies the number of buffers (with size specified by the 'sizereqbuf' parameter) the server uses to take requests from requestors. This parameter should be one of the first parameters checked if there is a performance problem with the server. For IBM LAN Server 1.3, this is done in the IBMLAN.INI. The field that needs to be changed is 'numreqbuf' under the [server] section of IBMLAN.INI. For IBM LAN Server 2.0 and 3.0, this is done in the IBMLAN.INI. The field that needs to be changed is 'numreqbuf' under the [server] section of IBMLAN.INI. For Microsoft LAN Manager, this is done in the LANMAN.INI file. The field that needs to be changed is 'numreqbuf' under the [server] section of LANMAN.INI. ********************************************************************* * * 3.0 Error Log file format and HP JetDirect NPI HPREDIR.EXE output format * ********************************************************************* There are two means of getting error indications and status information from the HP JetDirect NPI. The first is the HP JetDirect NPI Error Log file that is updated by the HP JetDirect NPI HPREDIR.EXE program and that can be viewed with the HP JetDirect NPI SETUP.EXE program. To view the Error Log: 1. Type "Setup" from the installation directory and press <Enter>, or select "HP Network Printer Setup" from the group that contains the SETUP utility. The "Welcome" screen might appear. Note: if you are already running SETUP, an information box appears. Select "OK" to exit the second version of SETUP and continue. 2. Select "OK" if the "Welcome" screen appears. 3. Select the "Log" menu. 4. Choose "View" to display the Error Log on the screen. Each line of the Error Log corresponds to a separate error message. To save the Error Log as an ASCII file: 1. Type "Setup" from the installation directory and press <Enter>, or select "HP Network Printer Setup" from the group that contains the SETUP utility. The "Welcome" screen might appear. Note: if you are already running SETUP, an information box appears. Select "OK" to exit the second version of SETUP and continue. 2. Select "OK" if the "Welcome" screen appears. 3. Select the "Log" menu. 4. Choose "Save As" to save the Error Log to an ASCII file. There are 5 fields in each Error Log entry: 1. Name of the printer the message refers to. 2. The date the error/status occured. 3. The time the error/status occured. 4. The error number. The errors are listed by number in the section "INSTALL and SETUP Error Messages" in the "LAN Server or LAN Manager" section of the "HP JetDirect Network Interface" document. 5. A brief description of the error/status. (Listed at the end of the description is the secondary error number. This number is used by the Customer Support Center staff to troubleshoot errors.) IMPORTANT: See the "HP JetDirect Network Interface" document for more details. The second means of getting error/status details is by running the HP JetDirect NPI HPREDIR.EXE program in a window, instead of from CONFIG.SYS. To do this: 1. Make sure HP JetDirect NPI SETUP.EXE isn't running. 2. Edit the CONFIG.SYS file and put a REM statement on the front of the line that looks like: RUN=C:\HPNETPRN\HPREDIR.EXE This line should now look like: REM RUN=C:\HPNETPRN\HPREDIR.EXE IMPORTANT: If your install path was different substitute your install path for 'C:\HPNETPRN'. E.g. if your boot drive is D: and you accepted the default install path. the line would be: RUN=D:\HPNETPRN\HPREDIR.EXE 3. Open up an OS/2 window. 4. Run the HP JetDirect NPI HPREDIR.EXE program from the window you opened. Type: CD \HPNETPRN HPREDIR IMPORTANT: See the IMPORTANT note above about install path for what directory you should be running from. IMPORTANT: If you want to save this output in a file that can viewed or printed later the line HPREDIR should be replaced with a line that redirects the output to a filename. E.g. HPREDIR > HPREDIR.OUT (Note: The output from HPREDIR is not documented and is for diagnostic purposes only, as directed by your HP service representative. Do not run HPREDIR in this mode for normal operation.) ********************************************************************* * * 4.0 Spooler Commands * ********************************************************************* JOB CANCEL may not result in the immediate cancellation of a printing job. Updates are necessary to both the spooler and printer device driver to correct this. LaserJet* (PCL4*) driver in CSD 5015 from IBM correct this. Check with the driver distribution sources listed below for the latest updates to the PCL5* driver. Check with your OS/2 dealer for possible updates to your version of OS/2. JOB HOLD and START AGAIN while printing may cause the error message NET2152 to be displayed, and not perform the desired function. If a job is to be held, it must be done prior to printing. Check with your OS/2 dealer for possible updates. ********************************************************************* * * 5.0 Printer Drivers * ********************************************************************* The latest peripheral Presentation Manager** (PM**) Printer Device Driver is available from HP distribution sources. To order the driver contact one of the following: HP's Distribution Center. Call (303) 353-7650 from 7 am to 6 pm (MT), Monday through Friday. Calling HP First from your FAX machine's telephone. You must have a touch tone group 3 FAX machine. Dial (208) 344-4809 24-hours a day. CompuServe's HP Forum. Choose the appropriate Presentation Manager Printer Device Driver for your peripheral. Each peripheral has a specific feature set. Not all drivers implement all features. PCL 4 drivers (LaserJet II family) are shipped with OS/2 1.21 and 1.3. They will work with JetDirect cards installed in HP LaserJet Series IIs and IIDs. A combined PCL4/PCL5 driver (LASERJET.HP) is shipped with OS/2 2.0 and can be obtained from HP for other OS/2 releases. It will work with LaserJet II and III families. A driver for the LaserJet 4 can be obtained from the above sources. The recommended driver for plotters is HP7586B plotter driver. The recommended driver for PaintJet* XL300 is the generic Postscript** driver for a server with only DOS or Windows** clients which preformat the print jobs. For PaintJets on OS/2 2.0 use the PaintJet driver shipped with OS/2. ********************************************************************* * * 6.0 Server Hardware * ********************************************************************* HPREDIR and Spooler utilization of server memory depends on the number of printers defined and the amount and size of print jobs. Under heavy load with very large print jobs printing continuously on six or more printers, it may be necessary to install 16 Mbytes of RAM in the server for optimum performance. For environments with moderate printing requirements, the memory recommendations for the network operating system should be sufficient. If SWAPPER.DAT file seems to grow, increasing memory on the server may help performance. ********************************************************************* * * 7.0 Server Software * ********************************************************************* HP recommends that you apply the latest updates for OS/2 and your network operating system prior to installing the JetDirect card software. On IBM PS/2** model 95 computers or other PS/2 machines using XGA** device drivers under OS/2 1.3, Presentation Manager will hang on reboot after installing the JetDirect software. Check with your OS/2 dealer for possible updates. This has been fixed on OS/2 2.0. Two workarounds are available. 1. Replace the XGA drivers with VGA drivers from CSD 5015 or newer. This is done by replacing the CONFIG.SYS statements SET VIDEO_DEVICES=VIO_IBMXGA SET VIO_IBMXGA=DEVICE(BVHVGA,BVHXGA) with SET VIDEO_DEVICES=VIO_IBMVGA SET VIO_IBMXGA=DEVICE(BVHVGA) and removing XGARING0.SYS from CONFIG.SYS. Also copy IBMVGA.DLL as DISPLAY.DLL to replace the current DISPLAY.DLL, and copy BVHVGA.DLL in place of BVHXGA.DLL. OR 2. Remove the following CONFIG.SYS statement added by Network Printer Interface Install: RUN=C:\HPNETPRN\HPREDIR.EXE Replace it with the following in STARTUP.CMD: DETACH C:\HPNETPRN\HPREDIR.EXE To ADD or DELETE a network printer, use the JetDirect Setup utility. For other tasks such as queue manipulation use the Print Manager. Avoid using the Print Manager to delete network printer definitions. ********************************************************************* * * 8.0 Locally Administered Addressing * ********************************************************************* The Locally Administered Addressing option is only supported on token ring cards for IBM LAN Server and Microsoft LAN Manager. The Locally Administered Address defined by the Setup program can be removed or reset to the factory default address with the printer cold reset procedure. On the HP LaserJet IIISi and 4Si, this is done by holding down the printer ONLINE key while powering on the printer. On HP LaserJets II, IID, III and IIID, address reset is done by pressing the interface status button while powering on the printer. The status button must be help down for about 15 seconds except on the HP LaserJet Series II, where the status button must be held down for about 40 seconds. ********************************************************************* * * 9.0 Banner (Separator) Pages * ********************************************************************* If you are using the Postscript option, the Banner Pages for the Postscript queue must be in the Postscript printer language. ASCII text characters or PCL escape sequences will not be recognized. ********************************************************************* * * 10.0 Plotter Test File * ********************************************************************* An HPGL2 file (TEST.GL2) has been included on the Install and Setup Utilities disk. Install copies it to the hard disk. This file is used instead of an ASCII test file when verifying installation of the JetDirect card and software for a plotter. ********************************************************************* * * 11.0 Defect Notice * ********************************************************************* There are a few known defects with using the HP JetDirect NPI. A detailed list of the known defects follows. 1. Problem: When deleting a printer from HP JetDirect NPI SETUP.EXE in OS/2 1.3, a "Error 0x4027 when deleting a logical address from OS2SYS.INI." error occurs when deleting the printer logical address from OS2SYS.INI. This problem will occur EVERYTIME a printer is deleted in under OS/2 1.3. Cause: Under OS/2 1.3, the HP JetDirect NPI SETUP.EXE program cannot delete a printer from OS2SYS.INI. The root cause of this is unknown. Workaround: This is NOT a fatal error. A printer with the same name will be able to be added. Fix: TBD. 2. Problem: A printer disconnects and doesn't reconnect. There is a message in the HP JetDirect NPI Error Log file that states that a printer thread exited. Cause: Unknown Workaround: Stop the HP JetDirect NPI HPREDIR.EXE program. The method to do this is to run the HP JetDirect NPI KILLRDR.EXE program. This is done by: 1) Opening an OS/2 command prompt. 2) Change to the HP JetDirect NPI installation directory. 3) Type: 'KILLRDR' Another method is to run the HP JetDirect NPI INSTALL.EXE program. This is done by: 1) Opening an OS/2 command prompt. 2) Change to the HP JetDirect NPI installation directory. 3) Type: 'INSTALL' 4) Click 'OK' at the "Welcome Screen". 5) Click 'OK' at the "Language Selection Screen". 6) Click 'YES' at the "The Software is already installed. Do you want to continue with installation? Screen" 7) Click 'CANCEL' at the "Network Printer Installation Screen". Fix: TBD. 3. Problem: Print jobs will disappear from the print object and never be printed in the case where a printer connection was lost. E.g. A few jobs sent to the printer just after it has been power cycled or physically disconnect will disappear. The following table and note tell the details of how print jobs will disappear. ┌────────────────┬───────────────────────────┬────────────────────────────────┐ │ Printer State │ Power Cycle │ Unplugged network cable │ ├────────────────┼───────────────────────────┼────────────────────────────────┤ │ Printing │ * 1 or more jobs lost │ * unplugged for < 2 seconds, │ │ │ * Wait 2 minutes after │ should otherwise 1 or more │ │ │ power cycle │ jobs lost │ │ │ │ * Wait 2 min after plugging │ │ │ │ back in unless left unplugged│ │ │ │ for more than 4 minutes. │ ├────────────────┼───────────────────────────┼────────────────────────────────┤ │ Connected │ * 2 minutes │ * 2 minutes │ │ (Logical) │ │ │ ├────────────────┼───────────────────────────┼────────────────────────────────┤ │ Not Connected │ * 0 seconds │ * 0 seconds │ │ (Logical) │ │ │ ├────────────────┼───────────────────────────┼────────────────────────────────┤ │ Long time with │ * 0 seconds │ * 0 seconds │ │ power off │ │ │ │ (> 4 minutes) │ │ │ │ OR │ │ │ │ Long time │ │ │ │ unplugged │ │ │ │ (> 4 minutes) │ │ │ └────────────────┴───────────────────────────┴────────────────────────────────┘ Table Note 1: After waiting the specified times and the printer is in a physical configuation that allows printing, a job should be able to be sent and be printed. If a job is sent before these times it could be lost. Table Note 2: The logical connections mentioned above are talking about the logical between the HP JetDirect NPI HPREDIR.EXE and the DLC. This connection can be broken by a physical connection being broken or a power off condition. Cause: The DLC Device Driver (LANDD.SYS in IBM LAN Server, or COMTKR.SYS in Microsoft LAN Manager) only checks for connections on minute boundries. The jobs cannot be restarted because the OS/2 Presentation Manager (PM**) will hang when a program tries to restart an interrupted job too many times, too quickly. Workaround: Follow the times set down in the table in the problem section. Fix: When IBM fixes the PM Hang condition caused by too many job restarts, the code to restart interrupted jobs can be re-added to the HP JetDirect NPI HPREDIR.EXE. 4. Problem: The spooler receives no status updates or messages. Cause: The spooler cannot receive messages because the OS/2 Presentation Manager will hang when a program tries to post too many messages to the Spooler Message Box, too quickly. Workaround: The printer status updates and messages are shown in the HP JetDirect NPI SETUP.EXE program, under the printer object and in the HP JetDirect NPI Error Log file. Fix: When IBM fixes the PM Hang condition caused by posting too many messages to the Spooler Message Box, the code to post messages to the Spooler Message Box will be re-added to the HP JetDirect NPI HPREDIR.EXE. 5. Problem: Old Error Log file information is lost when version A.00.05 of the HP JetDirect NPI is installed. Cause: The HP JetDirect NPI Error Log file formats for version A.00.03 and version A.00.05 are incompatible, so the HP JetDirect NPI INSTALL.EXE program deletes the old Error Log file when it installs. Workaround: There is NO way to get version A.00.05 of the HP JetDirect NPI to use the old Error Log file correctly. However, the old Error Log file can be outputed to a file from within the HP JetDirect NPI SETUP.EXE. Fix: None. ********************************************************************* * * 12.0 Ordering Documentation * ********************************************************************* Information for ordering documentation is listed below. Documentation Available: 1. HP JetDirect Card for IBM, Microsoft, 3Com 3+Open (Version 1.1f) Networks (for HP LaserJet IIISi Printer) (Part Number C2059-90920) 2. HP JetDirect Card for IBM, Microsoft, 3Com 3+Open (version 1.1f) Networks (for HP LaserJet Series II, IID, III, and IIID Printers) (Part Number C2071-90910) To order either of the above documents in the U.S., call HP Parts Direct at 1 800-227-8164. Hewlett-Packard products are sold and supported worldwide through Hewlett-Packard Sales and Service Offices. To locate the one nearest you, consult your telephone directory or contact one of the major Hewlett-Packard offices listed in your printer user's manual. ********************************************************************* * * 13.0 If you have problems * ********************************************************************* If you have any questions or concerns about the information in this file, you can contact HP's Customer Support Center at (208) 323-2551 for assistance. If you have any problems with the HP JetDirect NPI software, you can contact HP's Customer Support Center at (208) 323-2551 for assistance. If you contact HP for assistance, some of the following information may be requested: 1. A description of what symptoms you are observing. 2. The setup of your print server, including: a. OS/2 Version of the print server. b. IBM LAN Server or Microsoft LAN Manager Version of the print server. c. SYSLEVEL output from the print server. c. Print server machine type. d. Print server network interface card(s). e. Print server memory amount. 3. The OS/2 CONFIG.SYS file from your print server. 4. The OS/2 STARTUP.CMD file from your print server. 5. The IBM LAN Server or Microsoft LAN Manager PROTOCOL.INI file from your print server. 6. The IBM LAN Server IBMLAN.INI or the Microsoft LAN Manager LANMAN.INI from your print server. 7. HP JetDirect NPI Error Log file output. 8. HP JetDirect NPI HPREDIR.EXE output from running it in a window, see Section 3.0 "Error Log file format and HP JetDirect NPI HPREDIR.EXE output format" for details of how to obtain this output. 9. A sketch of your physical network, including: a. Ring(s), including 1) Speed of ring(s). 2) Where the network printer(s) are on the ring(s). 3) Where the print server(s) are on the ring(s). 4) Where bridges are between rings. b. Bridges 1) Type of bridge. c. Routers 1) Type of router. 2) Where the router connects into a ring. ********************************************************************* * * 14.0 Trademarks and Service Marks * ********************************************************************* The following terms, denoted by an asterisk (*) in this README, are trademarks or registered trademarks of the Hewlett-Packard Corporation in the United States or other countries: Hewlett-Packard ------------------------------------------ HP ------------------------------------------ HP LaserJet ------------------------------------------ HP JetDirect ------------------------------------------ HP PaintJet ------------------------------------------ PCL4 ------------------------------------------ PCL5 ------------------------------------------ The following terms, denoted by a double asterisk (**) in this README, are trademarks of other companies as follows: Trademark: Owner: -------------------------------------------------------------- IBM International Business Machines Corporation -------------------------------------------------------------- IBM Lan Server International Business Machines Corporation -------------------------------------------------------------- Microsoft LAN Manager Microsoft Corporation -------------------------------------------------------------- PostScript Adobe Systems Inc. -------------------------------------------------------------- OS/2 International Business Machines Corporation -------------------------------------------------------------- PM International Business Machines Corporation -------------------------------------------------------------- Presentation Manager International Business Machines Corporation -------------------------------------------------------------- PS/2 International Business Machines Corporation -------------------------------------------------------------- Windows Microsoft Corporation -------------------------------------------------------------- XGA International Business Machines Corporation -------------------------------------------------------------- HEWLETT-PACKARD MAKE NO WARRANTY OF ANY KIND WITH REGARD TO THIS MATERIAL, INCLUDING, BUT NO LIMITED TO, IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. BY FURNISHING THIS DOCUMENT, HEWLETT-PACKARD GRANTS NO LICENSES TO ANY RELATED PATENTS OR COPYRIGHTS.