______________________________________________ PrintServer Software for UNIX Release Notes These release notes contain information about PrintServer Software for UNIX, Version V5.1. Operating System and Version: IBM-AIX Version 3.2 HP-UX Version 9.05 Silicon Graphics IRIX Version 5.2 SCO UNIX Version 3.2.2 Solaris/SPARC Version 2.3, 2.4 Solaris/Intel Version 2.4 SunOS Version 4.1.2 DEC OSF/1 (Also known as Digital UNIX), Version 2.0, 3.0 Software Version: PrintServer Software, Version V5.1 Digital Equipment Corporation Maynard, Massachusetts __________________________________________________________ June, 1995 Digital Equipment Corporation makes no representations that the use of its products in the manner described in this publication will not infringe on existing or future patent rights, nor do the descriptions contained in this publication imply the granting of licenses to make, use, or sell equipment or software in accordance with the description. Possession, use, or copying of the software described in this publication is authorized only pursuant to a valid written license from Digital or an authorized sublicensor. © Digital Equipment Corporation 1995. All Rights Reserved. The postpaid Reader's Comments forms at the end of this document request your critical evaluation to assist in preparing future documentation. The following are trademarks of Digital Equipment Corporation: AXP, DEC, DECnet, DECprint, PrintServer, MicroVAX, Q-bus, ThinWire, TK, PrintServer, ULTRIX, ULTRIX-32, VAX, VAXcluster, VAX DOCUMENT, VAXELN, OpenVMS, OpenVMS, DECimage Plus, and the DIGITAL logo. PostScript is a trademark of Adobe Systems, Inc., registered in the U.S.A and other countries. PCL is a registered trademark of Hewlett-Packard Company. LaserJet is a registered trademark of Hewlett-Packard Company. UNIX is a registered trademark of UNIX System Laboratories, Inc., a subsidiary of American Telephone & Telegraph Company. Helvetica and Palatino are registered trademarks of Allied Corporation. ITC Bookman, ITC Zapf Chancery, and ITC Zapf Dingbats are registered trademarks of International Typeface Corporation. This document was prepared using VAX DOCUMENT Version 2.1. ________________________________________________________________ Contents Preface.................................................. vii 1 Executive Summary 2 New Features 2.1 All PrintServer printers..................... 2-1 2.1.1 Printer Status Manager (PRISM)........... 2-1 2.1.2 SNMP..................................... 2-1 2.1.3 LPD...................................... 2-3 2.1.4 Remote console enhancements.............. 2-3 2.1.5 Motif-based Printing Tool (xlpsprint).... 2-4 2.1.6 Unified Booting Daemon (lpsbootd)........ 2-4 2.1.7 ANSI Translation Capabilities............ 2-4 2.2 turbo PrintServer 20 printers and PrintServer 32 series printers........................... 2-5 2.2.1 Hardware upgrades........................ 2-5 2.2.2 Adobe PostScript level 2................. 2-5 2.2.3 Fonts.................................... 2-6 2.2.4 On-demand resource loading............... 2-6 3 Problems Addressed in this Release iii 4 UNIX Release Notes 4.1 Installing the Software...................... 4-1 4.2 Verifying the Installation................... 4-1 4.2.1 Installation and Setup enhancements...... 4-2 4.2.1.1 Improved Installation Procedure (lpsinstall)........................... 4-2 4.2.1.2 Improved Integration with "setld" on Digital UNIX Systems................... 4-2 4.2.1.3 Reduced Log Messages for Low Logging Levels................................. 4-3 4.2.1.4 Examine Log Files...................... 4-3 4.2.1.5 Print a Test Page for a New or Modified Print Client........................... 4-3 4.2.1.6 Emergency Backup Copy of the LPS Object Database (/etc/lpsodb)................. 4-3 4.2.1.7 Automatic Preservation of System Files.................................. 4-3 4.2.1.8 Enhanced Management Menus (lpssetup)... 4-4 4.2.1.9 More Consistent Object Definition Procedure.............................. 4-4 4.2.1.10 Allow Use of Hyphens and Underscores in Object Names........................... 4-4 4.2.1.11 Disallow Installation of Multiple Binary Sets............................ 4-4 4.2.1.12 Allow Specification of a Known Host for a Gateway Address...................... 4-4 4.2.1.13 Prototype Entries for /etc/bootptab Now in LPSDOC.............................. 4-4 4.3 UNIX Print Clients........................... 4-4 4.3.1 PrintServer 17 Used as the Default Model.................................... 4-5 4.3.2 Electronic Mail Message Sent When Print Job is Locally Aborted................... 4-5 4.3.3 Removal of Print Queue can Fail When Jobs Still Exist in the Queue................. 4-5 4.3.4 Page Size Parameters Ignored for ANSI Print Jobs............................... 4-5 4.3.5 "C codeset" Error Messages (Solaris)..... 4-6 4.3.6 Altering the Electronic Mail Configuration is Risky................... 4-6 4.3.7 No Verification of Target Interpreter in the Printer.............................. 4-6 iv 4.3.8 No Automatic Datatype Detection Available for ANSI Print Data...................... 4-6 4.4 Novell Print Clients......................... 4-7 4.5 OpenVMS Print Clients........................ 4-7 4.5.1 Updated ANSI Prologue.................... 4-7 4.5.2 Extraneous DPLXNOSUP message............. 4-7 4.6 ULTRIX Print Clients......................... 4-7 4.6.1 Selecting PrintServer 32 series or PrintServer 17 series Output Trays ...... 4-7 4.6.2 Selecting a PrintServer 17 Series Envelope Feeder or Manual Feed Mode...... 4-8 4.6.3 Correcting number_up problems............ 4-10 4.6.4 Correcting Problems with Internet Printing (iplpscomm)..................... 4-10 4.6.5 DECnet performance problem............... 4-11 4.6.6 Locating ULTRIX Print Client Errors...... 4-11 4.6.6.1 Check the syslog file.................. 4-11 4.6.6.2 Check the lp#err file.................. 4-12 4.6.6.3 Check the lpslog.... 4-12 4.7 Remote Console Client........................ 4-12 4.7.1 Enhanced Motif-based Remote Console (xlpsrc)................................. 4-12 4.7.2 Remote Console "quit" Command (lpsrc).... 4-13 4.7.3 No Way to Stop a Connection Attempt to a Printer (xlpsrc)......................... 4-13 4.7.4 Cancelling from "Reconnect" menu option................................... 4-13 4.8 PCL5......................................... 4-13 4.8.1 PJL and PCL5e Not Supported.............. 4-13 4.8.2 PCL5 performance......................... 4-14 4.9 Management Client............................ 4-14 4.9.1 SNMP Configuration is Not Used for PrintServer 20 or PrintServer 40......... 4-14 4.9.2 Manual Editing of the Printer Configuration File for Subnet Mask....... 4-14 4.10 Server....................................... 4-15 4.10.1 All PrintServer printers................. 4-15 4.10.1.1 Erroneous "Fatal software error" message................................ 4-15 4.10.1.2 Reduced number of simultaneous connections............................ 4-15 4.10.1.3 PrintServer fails to load resources.... 4-15 v 4.10.1.4 "Rest of Job (to EOJ) will be ignored" error on defaults file................. 4-15 4.10.2 Adobe PostScript level 2 Printers........ 4-16 4.10.2.1 Image interpreter...................... 4-16 4.10.2.2 Longer boot time....................... 4-16 4.10.2.3 VM exhausted errors.................... 4-16 4.10.2.4 One-sided tumble printing.............. 4-16 4.10.2.5 duplex printing and number_up work incorrectly............................ 4-17 4.10.2.6 DECimage Plus.......................... 4-17 4.10.2.7 Incorrect error message when paper size is unsupported by optional output devices................................ 4-17 4.10.2.8 Erroneous "Cover open" message on front panel.................................. 4-17 4.10.2.9 Tray removal causes tray switch........ 4-17 4.10.2.10 DCc circuit connect failure occurred............................... 4-18 4.10.2.11 PostScript "setdefaultpapertray" operator may not function.............. 4-18 4.10.3 PrintServer 17 Series Printers........... 4-18 4.10.3.1 Envelope feeder and Universal tray sizes not accessible from PCL5......... 4-18 4.10.3.2 Manual feed mode and default duplex printing generates error............... 4-19 4.10.4 turbo PrintServer 20 printers (with additional memory) and PrintServer 32 plus printers............................ 4-19 4.10.4.1 PrintServer fails to boot earlier version of software.................... 4-19 4.10.4.2 PostScript page counter gets reset..... 4-19 4.10.4.3 Corrupted output on printers running earlier version of software............ 4-20 4.10.4.4 Changing halftone frequency............ 4-20 4.10.5 PrintServer 40 series printers........... 4-20 4.10.5.1 Hardware Event During Secondary Boot ....................................... 4-21 4.10.5.2 Responding to Hardware Events.......... 4-21 4.10.6 Print Status Manager (PRISM)............. 4-21 4.10.7 Incorrect spacing for some error messages................................. 4-21 4.11 Helpful Print Tools.......................... 4-21 4.11.1 Printer Features Card.................... 4-21 vi 4.11.2 Obtaining Current Printer Defaults ...... 4-22 4.11.3 Editing the Printer Defaults File........ 4-23 4.12 Documentation Errors......................... 4-23 Tables 2-1 Hardware order numbers................... 2-5 vii ________________________________________________________________ Preface These release notes provide information not covered in the Installation or Management guides specific to the following software: o PrintServer Software for UNIX, Version V5.1 Intended Audience System administrators and managers who install and manage the PrintServer printer and supporting host system. Document Structure This document includes the following chapters: o Chapter 1, Executive Summary o Chapter 2, New Features o Chapter 3, Problems Addressed in this Release o Chapter 4, Information for UNIX supporting host systems, including installation notes and known problems vii 1 ________________________________________________________________ Executive Summary These release notes are for the following software: o PrintServer Software for UNIX, Version V5.1 This product supports the following printers: o PrintServer 17 o PrintServer 17/600 o PrintServer 20 o turbo PrintServer 20 o PrintServer 32 o PrintServer 32 plus o PrintServer 40 plus Please note that the PrintServer 40 is no longer supported. Contact your local sales or field service office or printers@digital.com for more details. The following features are new to Version V5.1. Some restrictions may apply. See Chapter 2 for more details. o Support for the new PrintServer 32 plus printer. (To upgrade an existing PrintServer 32 printer, see Section 2.2.1). o Adobe PostScript level 2, PCL5, and additional resident fonts for turbo PrintServer 20 printers (with additional memory) and PrintServer 32 plus printers. (This feature is already available on the PrintServer 17 series printers.) Executive Summary 1-1 o Printer Status Manager (PRISM) o SNMP o LPD o Remote Console enhancements o On-demand resource loading o Memory options for the turbo PrintServer 20 and PrintServer 32 printers. o Installation and Setup Enhancements o Motif-based Printing Tool (xlpsprint) o Unified Booting Daemon (lpsbootd) o ANSI Translation Capabilities 1-2 Executive Summary 2 ________________________________________________________________ New Features 2.1 All PrintServer printers 2.1.1 Printer Status Manager (PRISM) PRISM, a graphical user interface which allows you to simply monitor the status of multiple PrintServer printers, is available on the PrintServer 20 series, PrintServer 32 series, and PrintServer 17 series printers. Invoke PRISM with the command xlpsprism. The "look and feel" of PRISM varies considerably with the platform it is run on. Please see the PrintServer Software for UNIX Management Guide for more information. Please submit PRISM comments to printers@digital.com. 2.1.2 SNMP SNMP, an Internet-standard protocol used by many network management applications to monitor network nodes, is available on the turbo PrintServer 20, PrintServer 32 series, and PrintServer 17 series printers. In this release, if you load the SNMP protocol on a PrintServer 17/600 printer with 16 MB, only 29 fonts will be available and PCL emulation will be disabled. The following MIB-II objects are not supported by the SNMP agent in this release: o ipForwDatagrams o ipInDiscards o ipOutDiscards New Features 2-1 o ipRoutingDiscards o ipRouteAge o icmpInDestUnreachs o icmpInTimeExcds o icmpInParmProbs o icmpInSrcQuenchs o icmpInRedirects o icmpInEchos o icmpInEchoReps o icmpInTimestamps o icmpInTimestampReps o icmpInAddrMasks o icmpInAddrMaskReps o icmpOutErrors o icmpOutDestUnreachs o icmpOutTimeExcds o icmpOutParmProbs o icmpOutSrcQuenchs o icmpOutRedirects o icmpOutEchos o icmpOutEchoReps o icmpOutTimestamps o icmpOutTimestampReps o icmpOutAddrMasks o icmpOutAddrMaskReps o tcpAttemptFails o tcpEstabResets o egp group objects 2-2 New Features For more information, refer to the PrintServer Software Installation guide. 2.1.3 LPD LPD protocol support is available on all PrintServer printers. There are several ways to set up a local print queue. For more information, refer to your PrintServer Software Installation guide or your specific UN*X operating system documentation. Although the LPD protocol allows users and system managers to remove jobs from remote systems, this feature is not implemented in this release. 2.1.4 Remote console enhancements o The current message on the printer's front panel is now displayed at the top right-hand corner of the screen and within the "status" command in the remote console. This allows you to determine the state of the PrintServer printer. This feature is not available on PrintServer 40 series printers. o A "Reboot" command has been added. This privileged command causes the PrintServer printer to immediately stop any processing and reload its software over the network. The result is similar to toggling the power, except that powerup diagnostics are not performed. ________________________Note ________________________ This command should be used cautiously. All connections to management, console, and print clients will be broken. If there is any paper moving in the PrintServer at the time of the reboot command, the PrintServer printer will jam. _____________________________________________________ New Features 2-3 o The "configuration" command has been enhanced to report which software component have been loaded, how much memory is installed, and the IP gateway address. For example: LPS> config Accounting: On -> HOSTNAME Logging: On -> HOSTNAME . . . IP gateway: 16.34.144.252 Software: Adobe PostScript Level 2, SNMP MIB-II, LPD Option(s): Memory 12M base + 4M optional Duplexer Installed 2.1.5 Motif-based Printing Tool (xlpsprint) A new Motif utility called "xlpsprint" is included with this release. This tool provides a point-and-click user interface to greatly simplify setting print job options. 2.1.6 Unified Booting Daemon (lpsbootd) A new daemon program called "lpsbootd" is provided to simplify the booting of a PrintServer printer. This daemon can operate as a BOOTP server and/or TFTP server, thereby eliminating the need for you to configure a BOOTP server ("bootpd") if you only require such a server for handling PrintServer printer requests. If your PrintServer printer has the proper Version 3.7 ROMs installed, then the new lpsbootd daemon will use an alternate network port address to perform the booting of the printer without conflicting with your existing BOOTP /TFTP configuration. 2.1.7 ANSI Translation Capabilities ANSI translation facilities are now provided that should allow you to send print jobs formatted for LN03 or DEClaser printers, or most other printers that support the ANSI escape sequences. 2-4 New Features 2.2 turbo PrintServer 20 printers and PrintServer 32 series printers 2.2.1 Hardware upgrades To upgrade your turbo PrintServer 20 or PrintServer 32 printer, consult the following table. Table_2-1_Hardware_order_numbers__________________________ Part____________________________Order_Number______________ 4-MB Memory and Version 3.7 LPS3X-UA Firmware kit 4-MB SIMM LPS1X-UE 8-MB SIMM LPS1X-UF Version 3.7 Firmware-only kit 4A-LPS2XFW-B01 Memory option board without 54-23796-01 (Contact SIMM____________________________Digital_Services)_________ 2.2.2 Adobe PostScript level 2 This release adds PostScript level 2 to the turbo PrintServer 20 printer (with additional memory) and the PrintServer 32 plus printer. Without the addi- tional memory, the printers will have PostScript level 1. (PostScript level 2 is already available on the PrintServer 17 series printers.) You can order the memory upgrades through Digital. Please see Table 2-1 for ordering information. For more information on PostScript level 2 features, refer to the PostScript Language Reference Manual and PrintServer Printers PostScript Level 2 Programmer's Supplement. New Features 2-5 2.2.3 Fonts This release adds the following additional 14 fonts to the turbo PrintServer 20 (with additional memory) and PrintServer 32 plus printers. o Palatino family (4 fonts) o ITC Bookman family (4 fonts) o Helvetica-Narrow family (4 fonts) o ITC Zapf Chancery (1 font) o ITC Zapf Dingbats (1 font) If you have previously used the resource loading mechanism to download these fonts into the printer, Digital strongly recommends that you remove them from your resource file. For more information, refer to the PrintServer Software Management guide. 2.2.4 On-demand resource loading This release adds the ability to load resources on-demand for PostScript level 2 PrintServer printers from OpenVMS, ULTRIX, and Digital UNIX platforms. This feature is sometimes known as font faulting because the primary use of this mechanism on the PrintServer printer is to support faulting in font resources from a printer's supporting host system. When you use the font faulting feature, Type 1 fonts do not need to be loaded during the booting process. When the PrintServer printer cannot find the font in its memory, it asks the management client to find the font in the supporting host's directory. If found, the PrintServer printer uses the font across the network. The usual font fallback mechanism applies if the font is not in memory or the management client cannot find it on the supporting host system. To enable font faulting, edit GENERIC.dft and change the value of setDECfs from "false" to "true" and reconfigure the printer. The fonts need to be stored in /usr/opt/LPS/servers/fonts on Digital UNIX systems. 2-6 New Features If the directory doesn't exist, create one and make sure the management client can access the directory and fonts. In order for this mechanism to work, the management client must be running. New Features 2-7 3 ________________________________________________________________ Problems Addressed in this Release Specific changes include the following: o A PrintServer printer running Version 5.0 cannot be booted with bootp over a gateway. This means that the primary boot host, secondary boot host, and PrintServer printer must all be in the same subnet. This has been fixed in Version V5.1. o Version 5.0 does not properly load the pcl defaults file on the PrintServer 17 series printer at secondary boot time. This has been fixed in Version V5.1. o The emulate PostScript compatibility operator does not function properly in Version 5.0. It causes a rangecheck or invalidaccess error. In Version V5.1, the operator may be used to invoke the PCL5 emulator. The correct invocation of the emulate operator is: statusdict begin currentfile /LaserJetIII emulate o In Version 5.0, the PostScript sheetcount and pagecount operators return the same value. In Version V5.1, the sheetcount reflects the number of sheets of media printed by PostScript and the PCL5 emulator. The pagecount reflects the number of sides (or images) printed by PostScript and the PCL5 emulator. o Version 5.0 occasionally hangs with "processing" on the front panel if an error handler is in use and you send a print job containing privileged commands which has an error in it. The hang been fixed in Version V5.1. However, a "(DCc) Circuit connect failure nn occurred" message may still appear in the event log, and the trailer page (if any) may not be printed. Problems Addressed in this Release 3-1 o A PrintServer 40 running Version 5.0 will hang if you type "exit" at the LOCAL console. This has been fixed in Version V5.1. o Version 5.0 occasionally hangs with an exception message on the front panel similar to the following if a management client is repeatedly rejected by the PrintServer printer over some period of time: +---------------------------+ | LPS-F-EXCEPTION | | 0n/nn 00007CE4 0000nnnn | +---------------------------+ This may occur if four management daemons are connected to the same PrintServer printer, and a fifth management daemon is rejected and is continually retrying (OpenVMS clients do not retry), or if there are frequent "incompatible versions" rejections, or if you frequently stop and restart the management daemon for any reason. This problem is fixed in Version V5.1. o In Version 5.0, some files incorrectly failed with the PostScript error message: undefined: name not known - offending command is sendctrlsb This problem is fixed in Version V5.1. o In Version 5.0, a PrintServer printer may hang after loading a large number of resources during booting. This problem is fixed in Version V5.1. o In Version 5.0, there is an incompatibility between the EEPROM on a PrintServer 17 printer and on a PrintServer 17/600 printer. Due to differences in printer resolution, the printer will hang if the controller board with the EEPROM is inadvertently switched between the two types of printers. This problem is fixed in Version V5.1. o The compatibility operator "doret" has been changed to return "0", instead of "true", for compatiblity reasons. 3-2 Problems Addressed in this Release o In Version 5.0, under very specific circumstances, the remote console can cause an exception when the "netstat" command is issued. The result is a crash of the remote console. The PrintServer is still operational. This has been fixed in Version V5.1. o Certain UNIX Version 5.0 kits display a problem only when a management daemon runs WITHOUT accounting and logging enabled. The only symptom of the problem is that a message, "Management session ends", is logged to the lpslog file for the PrintServer printer every 2 minutes. This starts whenever the daemon is disconnected, and stops whenever another daemon connects to the PrintServer. This problem has been fixed in Version V5.1. o Certain DDIF files failed with the following error: $ %DCPS-W-IOERROR, ioerror: System I/O error occurred - offending command is image This has been fixed. o In Version 5.0, if you change the options file, you need to stop and restart the daemon before the change takes effect. In Version V5.1, the change automatically takes effect the next time the PrintServer is booted. o In Version 5.0, the PrintServer 20 series, PrintServer 32 series, and PrintServer 40 plus printers would occasionally hang because of memory constraints when there are many print connections (over 11, under 16) and the Image interpreter is loaded. In this release, connections that cannot be serviced are rejected, and the PrintServer printer will not hang. o In Version 5.0, the PrintServer 17 series printer left paper in the duplex path when a duplex job was paused from the front panel. In Version V5.1, this will not occur. o In Version 5.0, the imageable area on the PrintServer 17 series printer was not centered when using manual feed and B5 sheet size. In Version V5.1, this has been corrected. Problems Addressed in this Release 3-3 o In Version 5.0, some files were not removed by the deinstallation procedure (lpsdeinstall). The system startup commands used to launch Management Clients are now removed when the PrintServer Software is deinstalled using the "lpsdeinstall" script. Online manual page files are now removed. X Window application defaults files are now removed. o Previous versions of the software required the user to enter two EOF characters (usually CTRL/D on most systems) when running the "lpspr" utility to read from standard input when the input was fairly small. Now only a single EOF character is required. o In Version 5.0, manually removing a print queue definition outside of the execution of the "lpssetup" utility sometimes caused the PrintServer Software to get confused between what is defined in the LPS Object Database (/etc/lpsodb) and the corresponding print queue definitions. The software has been improved to be more forgiving of such situations. o In the previous version, when a print job is aborted by a privileged user on a Remote Console ("lpsrc" or "xlpsrc"), the print client could fail with a fatal error message, resulting in a hang of the print queue. This problem has been resolved in this release. o In Version 5.0, the print queue state (SunOS, Digital UNIX) was incorrectly recognized. The final test of "lpc down $QNAME" was reversed, resulting in erroneous messages declaring a problem with the target print queue. This has been corrected in this release. o In Version 5.0, the LPS Object Database (/etc/lpsodb) was not readable by some users. Whenever the LPS Object Database file is updated, the new copy was written using the process' existing umask value. Normally this umask value is such that read access is provided to the world ("other"); however, some customers change that value to lock out such read access. As a result, some of the LPS software components in previous versions would fail due to the inability to read the LPS Object Database. This problem has been fixed in this release 3-4 Problems Addressed in this Release by forcing world read access after the new version of the database has been written. o In Version 5.0, access control information in the Printer Configuration File was missing. If you specified "allow" access for hosts, but did not specify "deny" access for any hosts, the "allow" list would not be written to the configuration file. This problem has been fixed in this release. o In Version 5.0, the Management Client terminated if for some reason the log file was missing. This problem has been fixed in this release. Problems Addressed in this Release 3-5 4 ________________________________________________________________ UNIX Release Notes This section provides information about installing and using the PrintServer Software. Read this section and the installation guide before installing PrintServer Software for UNIX, Version V5.1. ________________________Note ________________________ The DEC OSF/1 operating system is also known as Digital UNIX. _____________________________________________________ 4.1 Installing the Software 4.2 Verifying the Installation After booting, verify that the new software is running by using the PrintServer console client (local console on PrintServer 40 printer or remote console for any PrintServer printer). Invoke the remote console utility with either of the following commands: lpsrc, xlpsrc, or xlpsprism Issue the console utility's "versions" command and look for the following version number in the output: PrintServer Software: V5.1-15 Issue the console utility's "configuration" command and look at the "software" output. If the printer is a turbo PrintServer 20, PrintServer 32 plus, or PrintServer 17 series printer, you should see the words "Adobe PostScript level 2". Otherwise, you should see the words "Adobe PostScript". You should also see the word PCL5, indicating UNIX Release Notes 4-1 that the PCL5 interpreter is available. If you selected SNMP, you see the words "SNMP MIB-II". When booting your PrintServer 20 series, PrintServer 32 series, or PrintServer 17 series printer over TCP/IP, if the IP address specified in /etc/hosts and the one in /etc/bootptab do not match, the PrintServer printer successfully completes primary boot, but is unavailable to the network. /etc/ping and lpsrc fail to connect. There is no error code or message. If you have these symptoms, grep /etc/host and /etc/bootptab and carefully check the addresses to be sure they are correct. The following messages have been added to help diagnose TCP/IP booting problems: BOOTP: Bad GW size BOOTP: Bad SM size BOOTP: GW, no SM 4.2.1 Installation and Setup enhancements 4.2.1.1 Improved Installation Procedure (lpsinstall) You can now specify the target installation directory and still accept default values for the remainder of the software configuration. Previous versions required you to specify the entire set of environment configuration variables if all you wanted to do was specify the target installation directory. Note that this feature does not apply to Digital UNIX systems; see the next section for installation on Digital UNIX systems. The installation has been improved to better handle CD-ROM as the distribution media. 4.2.1.2 Improved Integration with "setld" on Digital UNIX Systems The Digital UNIX version is now integrated with the stan- dard setld utility. The installation and deinstallation facilities are now setld aware during execution. 4-2 UNIX Release Notes 4.2.1.3 Reduced Log Messages for Low Logging Levels The logging facilities for Print Clients and Management Clients have been changed so that a log level of zero ("0") results in very little, if any, status-related log messages written to the log file. Error messages, however, will still be logged regardless of the log level so that you are able to detect problems with minimum investigation. 4.2.1.4 Examine Log Files To make it easier and quicker for you to view the log file of a Print Client or Management Client, a new menu item has been added to the menus for these objects in the "lpssetup" utility. No longer do you have to first determine the location of the target log file in order to view it. 4.2.1.5 Print a Test Page for a New or Modified Print Client After creating or modifying a Print Client, you can now allow a test page to be printed on the Client. The test page describes the detailed configuration of the Print Client. 4.2.1.6 Emergency Backup Copy of the LPS Object Database (/etc/lpsodb) To assist you in recovering from catastrophic file system problems, the "lpssetup" utility now automatically creates a copy of a newly modified database in the $LPSROOT directory. Every time you modify the database (by adding, modifying or removing an LPS object), a copy of the new database is made, and the location of the copy is displayed on your terminal window. 4.2.1.7 Automatic Preservation of System Files As with previous versions of the software, this release has the ability to create "backup" versions of modified system files. However, with this release you are no longer asked whether you want to preserve a given file; the supporting scripts automatically preserve all system files so that you no longer have to respond to this question. UNIX Release Notes 4-3 4.2.1.8 Enhanced Management Menus (lpssetup) Several new items have been added to most of the menus in the "lpssetup" utility, giving you new and more rapid access to the many features of the PrintServer Software product. 4.2.1.9 More Consistent Object Definition Procedure The scripts used by the "lpssetup" utility have been modified so as to have a more consistent look and feel when defining any type of object. 4.2.1.10 Allow Use of Hyphens and Underscores in Object Names You can now create objects that have hyphens ("-") and/or underscore ("_") characters in the object name. 4.2.1.11 Disallow Installation of Multiple Binary Sets Previous versions of the software allowed you to install all versions of the binary executable files that are based on a target operating system version. This feature proved to have limited utility and was removed. 4.2.1.12 Allow Specification of a Known Host for a Gateway Address You can now enter the name of a known hostname as the gateway address when configuring a printer. Previous versions required you to enter the internet address. Now you can enter either a hostname or an address. 4.2.1.13 Prototype Entries for /etc/bootptab Now in LPSDOC If you require the use of a "bootpd" daemon to boot one or more PrintServer printers, then when you create or modify a printer configuration with the "lpssetup" utility, the fully defined bootptab entry text is now stored in the $LPSDOC directory instead of the $LPSSERVERS directory. Files of this type have a name comprising the associated PrintServer printer name and a file suffix of ".bpt". 4.3 UNIX Print Clients 4-4 UNIX Release Notes 4.3.1 PrintServer 17 Used as the Default Model Unless you specify otherwise, all software components that offer functionality based on a specific PrintServer printer model will assume a model of "LPS17" (PrintServer 17 family). Previous versions of the software assumed the model was "LPS20" (PrintServer 20 family). 4.3.2 Electronic Mail Message Sent When Print Job is Locally Aborted When a Print Client is notified by the local system to abort the current job (due to a "lprm" or "cancel" command), the Print Client will immediately shutdown the transfer of the print job data to the printer. If the print data is PostScript, then the sudden termination of the PostScript data will usually cause the printer's PostScript interpreter to declare an error message; this error message, in turn, is received by the Print Client, which in turn sends to the requesting user an electronic mail message containing the PostScript error message. Such messages should be disregarded by the user. 4.3.3 Removal of Print Queue can Fail When Jobs Still Exist in the Queue If you wish to remove a Print Client definition, the procedure will fail if there are print jobs in the associated print queue at the time of removal. To circumvent this failure, be sure to first clear the print queue either by allowing the queue to drain, aborting the jobs, or, in the case of System V platforms, moving the jobs to another queue. 4.3.4 Page Size Parameters Ignored for ANSI Print Jobs Some of the Print Client software components will allow you to specify page size parameters (width, length, sheet size, etc.) when you specify a datatype of "ansi." These parameters, however, are ignored by the ANSI translator facilities. UNIX Release Notes 4-5 4.3.5 "C codeset" Error Messages (Solaris) Some installations of Solaris result in character set mapping error messages by the X11 Window System software when using the PrintServer X11-based utilities. You may want to verify that your environment variables are set correctly. To define where the Motif and X11 libraries are located: LD_LIBRARY_PATH=/opt/SUNWmotif/lib:/usr/openwin/lib To define where the resource files for the LPS Motif programs are: XAPPLRESDIR=/opt/local/lps/lib 4.3.6 Altering the Electronic Mail Configuration is Risky The installation procedure allows you to change the default electronic mail program and its command line options. However, unless you are extremely familiar with your local electronic mail facilities, it is unwise to use anything other than the default values presented at installation time. 4.3.7 No Verification of Target Interpreter in the Printer If you specify a datatype for which no appropriate interpreter exists within the target printer, the printer will attempt to use the PostScript interpreter, resulting in the subsequent failure of the print job. 4.3.8 No Automatic Datatype Detection Available for ANSI Print Data If you do not specify the datatype of the print job, the software will attempt to automatically determine the proper datatype. This process works for ASCII, PostScript and PCL, but does not work for ANSI data. You must explicitly specify a datatype of "ansi" whenever you need to print ANSI print data. 4-6 UNIX Release Notes 4.4 Novell Print Clients Please see the print client section of the PrintServer Software for Novell NetWare Release Notes. 4.5 OpenVMS Print Clients This section is provided for those sites using OpenVMS print clients (DCPS). 4.5.1 Updated ANSI Prologue An updated ANSI Prologue (Version 3.3-0) has been included in this release. This prologue file also ships with DCPS V1.1. There is a version skew problem with this prologue file and the version number stored in existing resource files. The problem may cause the ANSI prologue to be downloaded for each ANSI print job, thus causing an unnecessary performance problem. To correct this problem, run SYS$MANAGER:LPS$UPGRADE_PRINTSERVER.COM for each PrintServer printer. 4.5.2 Extraneous DPLXNOSUP message When deleting a print job, the following error message may sometimes be generated immediately after the DCPS-I- JOBSTART message. "DCPS-E-DPLXNOSUP, does not support duplex printing" This message may safely be ignored. 4.6 ULTRIX Print Clients This section is included for sites using ULTRIX print clients. 4.6.1 Selecting PrintServer 32 series or PrintServer 17 series Output Trays This section describes a problem with selecting output trays on the PrintServer 32 series or PrintServer 17 series printers from an ULTRIX print client. UNIX Release Notes 4-7 Before you can select output trays on all PrintServer printers using the -o option to lpr, replace a file in the "/usr/lib/lpdfilters/lps_v3.a" device control library. If this is not done, all jobs sent to PrintServer 32 series or PrintServer 17 series printers using the -o option abort. (Jobs submitted without the -o option print normally.) A new module, LPS_SETOUTPUTTR, is included in this kit, and is located in the /usr/kits/lps directory. Issue the following commands to replace the module in the device control library. The first command saves a copy of lps_ v3.a in case something goes wrong during the archive operation. # cd /usr/lib/lpdfilters # cp lps_v3.a lps_v3.save # ar rv lps_v3.a /usr/kits/lps/LPS_SETOUTPUTTR This module is also provided in the PrintServer Software for OpenVMS kit for customers using OpenVMS boot hosts with ULTRIX print clients. The file LPS_SETOUTPUTTR is located in the SYS$COMMON:[SYSHLP.EXAMPLES.LPS] directory. To copy this file to your ULTRIX system from the OpenVMS supporting host system, perform the following commands on the ULTRIX system: # cd /usr/lib/lpdfilters # cp lps_v3.a lps_v3.save # dcp -v NODE::'sys$common:[syshlp.examples.lps]LPS_SETOUTPUTTR.' \ ./LPS_SETOUTPUTTR # ar rv lps_v3.a LPS_SETOUTPUTTR 4.6.2 Selecting a PrintServer 17 Series Envelope Feeder or Manual Feed Mode The envelope feeder and manual feed mode cannot be selected from the standard lpr command on an ULTRIX system because there are no corresponding qualifiers to the lpr command. This section describes a workaround to this problem where a qualifier that is unused on the PrintServer 17 series printers can be redefined to select either the envelope feeder or manual feed mode. 4-8 UNIX Release Notes Since the PrintServer 17 series printers do not have a "middle" input tray, the -Imiddle qualifier can be redefined as follows: 1. To redefine -Imiddle to select the envelope feeder skip to step 5. To redefine -Imiddle to select manual feed mode, proceed to step 2. 2. Edit the file /usr/kits/lps/LPS_SETINPUTTRA, which is included with the PrintServer software kit. # cd /usr/kits/lps # vi LPS_SETINPUTTRA # or use your favorite editor 3. Find the following two lines: /middle{99 setpapertray} % uncomment ... envelope feeder % /middle{0 setpapertray} % uncomment ... manual feed 4. Modify the first character of each line so they appear as follows: % /middle{99 setpapertray} % uncomment ... envelope feeder /middle{0 setpapertray} % uncomment ... manual feed 5. Issue the following commands to replace the module in the device control library. The second command saves a copy of lps_v3.a in case something goes wrong during the archive operation. # cd /usr/lib/lpdfilters # cp lps_v3.a lps_v3.save # ar rv lps_v3.a /usr/kits/lps/LPS_SETINPUTTRA This module is also provided in the PrintServer Software for OpenVMS kit for those customers using OpenVMS boot hosts along with ULTRIX print clients. The file LPS_ SETINPUTTRA. is located in the SYS$COMMON:[SYSHLP.EXAMPLES.LPS] directory. To copy this file to your ULTRIX system from the OpenVMS supporting host system, perform the following commands on the ULTRIX system: # cd /usr/lib/lpdfilters # cp lps_v3.a lps_v3.save # dcp -v NODE::'sys$common:[syshlp.examples.lps]LPS_SETINPUTTRA.' \ ./LPS_SETINPUTTRA # ar rv lps_v3.a LPS_SETINPUTTRA UNIX Release Notes 4-9 Once you have performed this step, specify "middle" for the -I option to lpr to select the optional envelope feeder or manual feed on the PrintServer 17 series printers. 4.6.3 Correcting number_up problems Several modules contained in the ULTRIX operating system have been modified to fix a problem with using the -N parameter with an odd number of pages. To obtain the fixed modules, the modules LPS_SETCONTEXT, LPS_SETNUMBERUP, and LPS_LOADDICT must be replaced into the device control library. These files are located in the /usr/kits/lps directory. Issue the following commands to replace the modules in the device control library. The first command saves a copy of lps_v3.a in case something goes wrong during the archive operation. # cd /usr/lib/lpdfilters # cp lps_v3.a lps_v3.save # ar rv lps_v3.a /usr/kits/lps/LPS_SETCONTEXT # ar rv lps_v3.a /usr/kits/lps/LPS_SETNUMBERUP # ar rv lps_v3.a /usr/kits/lps/LPS_LOADDICT If you would like the corrected modules and do not have the PrintServer Software for ULTRIX, you may wish to contact the customer support center for these files. 4.6.4 Correcting Problems with Internet Printing (iplpscomm) Three problems exist with the iplpscomm filter shipped with the ULTRIX operating system (Versions 4.3 and below). These problems have been fixed in Version 4.4 of the ULTRIX operating system. o Jobs are discarded when a network error occurs o Output from PostScript files containing image data is distorted o Userdata messages from printer can be truncated 4-10 UNIX Release Notes In addition, several ULTRIX abort problems have been fixed with the iplpscomm filter included with the PrintServer Software for ULTRIX. To install the filter, issue the following commands. You must have superuser privileges. # cd /usr/lib/lpdfilters # cp iplpscomm iplpscomm.save # cp /usr/kits/lps/bin/iplpscomm.`/bin/machine` iplpscomm # chmod 755 iplpscomm If you are experiencing problems and do not have the PrintServer Software for ULTRIX, you may wish to contact the customer support center for a new iplpscomm filter. 4.6.5 DECnet performance problem Printing large documents using DECnet from ULTRIX is much slower than using TCP/IP from ULTRIX. Therefore, Digital recommends that you use iplpscomm (not lpscomm) as the output filter in etc/printcap. See lprsetup and printcap man pages for additional information. 4.6.6 Locating ULTRIX Print Client Errors If jobs disappear from your print queue or fail to print, check the following files: o syslog o lp#err o lpslog. 4.6.6.1 Check the syslog file Your ULTRIX system maintains a syslog file of errors and events written by many of the processes running on your ULTRIX system. Check the contents of file /etc /syslog.conf. This file contains the location of the syslog file. On most systems the syslog file is located at /usr/spool/mqueue/syslog. UNIX Release Notes 4-11 4.6.6.2 Check the lp#err file Each lpd instantiation has its own error and event log file, which can be located by using grep on the /etc /printcap file. Look for the first line of the entry for the printer in question. The following examples are for a printer called "ogre". grep ogre /etc/printcap The response is similar to the following: ogre|lp2|ogre:\ Use grep on the /etc/printcap file again. Look for the lp# entry (lp2 in this example). grep lp2 /etc/printcap The response is similar to the following: lf:/usr/adm/lp2err In this example, /usr/adm/lp2err is the client-based event log file. 4.6.6.3 Check the lpslog. PrintServer printers maintain their own event log file. To locate a PrintServer printer's event log file, run the remote console program by typing the following command: /usr/kits/lps/lpsrc or /usr/kits/lps/xlpsrc -p Use the "config" command to list logging host node names. Inspect the file /var/kits/lps/lpslog. on one of the logging hosts. 4.7 Remote Console Client 4.7.1 Enhanced Motif-based Remote Console (xlpsrc) The Motif-based Remote Console utility "xlpsrc" has been enhanced to provide access to the new PrintServer printer "reboot" command. The user interface has been changed slightly to be more consistent in a windowing environment, and a new "keepalive" facility has been added to better detect network problems that result in 4-12 UNIX Release Notes unexpected disconnections between the application and the printer. 4.7.2 Remote Console "quit" Command (lpsrc) You can now specify a command called "quit" instead of "exit" in the character-based Remote Console ("lpsrc"). 4.7.3 No Way to Stop a Connection Attempt to a Printer (xlpsrc) Once you direct xlpsrc to connect to a printer, you are unable to terminate the connection attempt unless you terminate the program. If the printer is not available on the network for any reason, you must wait the nominal amount of time (usually about 45 seconds) for the connection attempt to fail before you can regain control of the application. 4.7.4 Cancelling from "Reconnect" menu option If you select "Reconnect to New PrintServer Printer" from the File menu of the remote console, the connection to the previous PrintServer printer is lost, even if you select "cancel". 4.8 PCL5 4.8.1 PJL and PCL5e Not Supported All suitably-configured Adobe PostScript level 2 PrintServer printers support the HP LaserJet IIIsi interpreter (PCL5). However, this interpreter does not support PJL commands. If you are printing from an application using a PCL printer driver that generates PJL commands, you may get a blank page at the end of your job or see the PJL characters printed on your output. In addition, this interpreter does not support PCL5e. Some PCL5e files may print incorrectly. UNIX Release Notes 4-13 4.8.2 PCL5 performance If you load paper into your printer in the long-edge feed direction, you will notice a drop in performance for your PCL5 jobs. This is caused by the PrintServer printer rotating the image to fit on the long-edged paper. Therefore, you may want to load your paper in the short- edge feed direction when printing PCL jobs. . 4.9 Management Client 4.9.1 SNMP Configuration is Not Used for PrintServer 20 or PrintServer 40 The new SNMP agent facilities are not available in the base PrintServer 20 printer or in the PrintServer 40 series printers. SNMP facilities are available for the turbo PrintServer 20, PrintServer 17 series, and PrintServer 32 series printers. You configure the SNMP facilities for a printer through the "lpssetup" utility. However, lpssetup does not currently differentiate between a PrintServer 20 printer and a turbo PrintServer 20 printer. As a result, you can enter various SNMP-related configuration information for a PrintServer 20, however that information is rendered useless due to the fact that this model can not load the SNMP software at boot time. 4.9.2 Manual Editing of the Printer Configuration File for Subnet Mask When a printer is configured through the "lpssetup" utility, the utility automatically uses the local system's subnetwork mask as the mask value for the printer. In most cases this is appropriate; however, there may be situations in which the printer's subnet mask must be different than the local host's mask value. To configure the printer with a different subnet mask value, you must manually edit the printer configuration file. 4-14 UNIX Release Notes 4.10 Server 4.10.1 All PrintServer printers 4.10.1.1 Erroneous "Fatal software error" message Pressing the front panel pause key while deleting a job may cause the erroneous message, "Fatal software error - reboot or recycle power." The printer remains operational. To remove the message, print a job, then press the front panel pause key again, then press the resume key. 4.10.1.2 Reduced number of simultaneous connections In Version 4.2, the PrintServer 40 printers were limited to 12 simultaneous print connections. Other PrintServer printers were limited to 16 simultaneous connections. In Version 5.0, the PrintServer 17 series printers could accept variable number of connections, depending upon the amount of memory available at the time of the connection. In Version 5.1 this "variable connection limit" has been extended to all PrintServer printers. There will never be more than 16 connections overall. Because of memory restrictions, however, some configurations (especially the PrintServer 17/600 with 16 MB) will allow a reduced number of connections. Excess connections are rejected by the PrintServer printer, and are retried by the print client. This restriction is greatly alleviated with the addition of 4MB of memory. 4.10.1.3 PrintServer fails to load resources The GENERIC.res file must not contain any extra leading or trailing spaces on any line. If, for example, the resource filename "ansipro.ps" has trailing spaces after it, the PrintServer will not successfully load the ansi prolog. 4.10.1.4 "Rest of Job (to EOJ) will be ignored" error on defaults file If you use a new version of the GENERIC.dft for a PrintServer printer that does NOT have optional memory installed, the PrintServer printer displays the message "Rest of Job (to EOJ) will be ignored" in the /var /adm/.elog file when loading the GENERIC.dft file. This is not an error message, but rather signals that the PrintServer printer is ignoring the UNIX Release Notes 4-15 PostScript level 2 portion of the new GENERIC.dft file because the interpreter is not level 2. 4.10.2 Adobe PostScript level 2 Printers This section refers to any PrintServer printer that loads Adobe PostScript level 2. See Section 4.2 to determine which level of Adobe PostScript you are running. 4.10.2.1 Image interpreter The Image interpreter is not available on PostScript level 2 PrintServer printers. However, it is available on turbo PrintServer 20 and PrintServer 32 printers running level 1 Adobe PostScript (i.e, in 12 Mbytes configurations). 4.10.2.2 Longer boot time Due to the larger, more complex PostScript image, you may notice that booting takes longer on Adobe PostScript level 2 PrintServer printers than in older versions. If you suspect there is a problem with the printer, refer to the PrintServer Software Installation guide for troubleshooting information. 4.10.2.3 VM exhausted errors If a print job loads many fonts on a minimum memory configuration, it may fail to print with a VM exhausted error. Lowering the value of the system parameter "MaxFontCache" (minimum value of 250000) may solve this problem. To make the default value persistent across job boundaries, add /MaxFontCache and its value to the GENERIC.spf file. If the file still fails to print completely, you need to add additional memory. For more information, refer to the PrintServer Software Management guide. 4.10.2.4 One-sided tumble printing One-sided tumble printing is not available. Jobs specified as such print in normal simplex mode. Two-sided tumble printing works as expected. 4-16 UNIX Release Notes 4.10.2.5 duplex printing and number_up work incorrectly Setting duplex mode in your print job and using the command line parameter to select number_up greater than 1 may cause the first page of your document to print incorrectly (either clipped or improperly scaled). To avoid this problem, set both the duplex and number_up parameters from the command line. 4.10.2.6 DECimage Plus Multiple DECimage compatibility operator invocations within a single PostScript job may result in the wrong halftone being applied. 4.10.2.7 Incorrect error message when paper size is unsupported by optional output devices The optional output devices support a limited number of paper sizes. If you try to send an unsupported paper size to it, the PrintServer printer aborts the job with an error message. This error message is not always appropriate. It may say, for example, "No 10x14 size medium is loaded in ", or it may give a rangecheck error. 4.10.2.8 Erroneous "Cover open" message on front panel If you open the optional output tray cover while the optional output tray is full, the front panel displays the message "Close optional output device cover or door". Once you close the door, this message remains until you clear the tray full condition. 4.10.2.9 Tray removal causes tray switch If you remove a tray from the PrintServer printer while it is printing (without pressing "pause" and waiting for the PrintServer printer to pause first) the printer stops on its own. If you then replace the tray, the PrintServer continues, but it pulls paper from the default tray, using the default paper size. UNIX Release Notes 4-17 4.10.2.10 DCc circuit connect failure occurred... The error message "DCc circuit connect failure occurred" is a generic message that indicates a temporary or permanent failure in PostScript's job stream. One known cause of a temporary failure is described below. If you send a privileged job to the PrintServer printer containing a startjob operator (level 2 only) or an exitserver operator (either level), and there is another document immediately following the privileged job, the PrintServer may abort the second document with an error in the lpslog.printername file that reads "Dcc circuit connect failure 31788 ocurred". (The number may vary). If you use DCPS to send the privileged job with trailer pages enabled, the trailer page aborts with this message. The privileged job prints successfully to completion, but the second document or job is lost and must be resubmitted. If the trailer page is the only document causing the error, (which is most often the case), the error may safely be ignored. 4.10.2.11 PostScript "setdefaultpapertray" operator may not function. If you send the privileged PostScript compatibility operator "setdefaultoutputtray" to a level 2 PrintServer printer, followed by the privileged compatibility operator "setdefaultpapertray", the default paper tray is not changed. If you send the operators in the reverse order, they work as expected. 4.10.3 PrintServer 17 Series Printers 4.10.3.1 Envelope feeder and Universal tray sizes not accessible from PCL5 The PrintServer 17 envelope feeder and universal tray are not accessible from PCL5. To workaround this problem, use the defaults file to set either of these as the default tray. 4-18 UNIX Release Notes 4.10.3.2 Manual feed mode and default duplex printing generates error On the PrintServer 17 series printers, if the default state of the printer is set to duplex, and the user requests manual feed in simplex mode from the command line, manual feed will be ignored and the job will print from the default tray. To workaround this problem, turn off duplex mode in the defaults file or use the following PostScript code at the top of your file: statusdict begin 0 setpapertray false setduplexmode end 4.10.4 turbo PrintServer 20 printers (with additional memory) and PrintServer 32 plus printers 4.10.4.1 PrintServer fails to boot earlier version of software If you have loaded level 2 PostScript into your PrintServer printer and inadvertently go back to a previous version of software or remove the optional memory board, the PrintServer printer may need to be power-cycled twice to successfully boot. 4.10.4.2 PostScript page counter gets reset If you have loaded level 2 PostScript into your PrintServer printer and inadvertently go back to a previous version of software or remove the optional memory board, the PostScript page counter will get reset. The PostScript page counter does not get reset when upgrading to PostScript level 2. UNIX Release Notes 4-19 4.10.4.3 Corrupted output on printers running earlier version of software A PrintServer 32 plus printer or turbo PrintServer 20 printer (with additional memory) cannot run software earlier than Version V5.1. If you inadvertently load old software, you will experience corrupted output. The startpage, for example, often appears somewhat like "reverse video" output, with a black background and each letter centered in a small white area. Other effects will occur on subsequent pages, and the PrintServer printer may crash. Check the remote console "config" command to determine if you are running PostScript level 2, and to see how much memory is installed. Either reboot the printer with the correct version of software or remove the memory board from the printer. 4.10.4.4 Changing halftone frequency The PostScript level 2 interpreter contains a halftone dictionary which specifies the halftoning process to be used by the painting operators. The following example shows how to persistently change the default frequency for the PrintServer 17/600 to 200. true (LPS) startjob /Halftone600 /Halftone findresource dup type /dicttype eq { dup length dict copy dup /Frequency 200 put } if dup /Halftone600 exch /Halftone defineresource pop 4.10.5 PrintServer 40 series printers 4-20 UNIX Release Notes 4.10.5.1 Hardware Event During Secondary Boot If the printer does not reach the "Idle" state and does not accept print jobs after a reboot even though the management client is connected to the printer, check the printer event log file (/var/adm/.elog) or local console for hardware error messages (such as paper jams). If you correct the hardware problem and the printer still does not reach the idle state, reboot again to clear the condition. 4.10.5.2 Responding to Hardware Events Certain events that occur on the PrintServer 40 or 40 plus printers require user or operator intervention before the printer can resume printing. Examples of these events include running out of paper or paper jams. When you correct the condition, the "Print engine error has been corrected" message appears on the local console and the printer resumes operation within a few seconds. If you correct the condition and the printer does not recover quickly, examine the stand-by indicator on the front panel. A flashing indicator means that the printer is resetting its internal state. Do not perform any other operation on the printer (such as opening doors) while the printer is resetting itself. After 2 minutes, the printer resumes operation. If additional printer events are generated during the reset period, the printer may hang and require a reboot. 4.10.6 Print Status Manager (PRISM) 4.10.7 Incorrect spacing for some error messages Error messages which normally span two lines on the front panel are not spaced correctly on the PRISM display. 4.11 Helpful Print Tools 4.11.1 Printer Features Card The PrintServer Software for UNIX, Version V5.1 kit includes a PostScript file of PrintServer printer features. This file lists commonly-used printing options and shows what these options do. When printed in duplex mode, this file provides a single sheet that contains the commonly-used PRINT options. UNIX Release Notes 4-21 This file is called usercard.ps and is installed in $LPSDOC. To print the file in duplex mode on a duplex printer, enter the following command: For BSD UNIX systems: #lpspr -Dpostscript -K2 usercard.ps | lpr -P printer-name For System V UNIX systems: #lp -d printer-name -o"datatype=postscript duplex" usercard.ps To print the file in simplex mode, enter this command: For BSD UNIX systems: #lpspr -Dpostscript usercard.ps | lpr -P printer-name For System V UNIX systems: #lp -d printer-name -o"datatype=postscript" usercard.ps In addition, several copies of the User Feature Card, printed on hardstock paper, have been supplied with each PrintServer printer. Additional copies (part number EK- TLLPS-RC) may be ordered through DECdirect at 1-800- DIGITAL. 4.11.2 Obtaining Current Printer Defaults To determine the current values for the PrintServer printer defaults (such as duplex mode, input tray, and output tray), read the GENERIC.dft file on the supporting host system that supplied the configuration files to the printer. For PostScript level 2 printers, the default values are printed on the startpage when the printer is booted. You can also obtain these default values by printing the file: $LPSROOT/servers/startpag.ps 4-22 UNIX Release Notes Please note that the page count shown on the startpage does not agree with the mechanical counter on the PrintServer 20 and PrintServer 32 series printers. The mechanical page counter counts revolutions of the OPC drum, not pages completed. 4.11.3 Editing the Printer Defaults File The following comments in the GENERIC.dft file: % PostScript Level 1 PrintServer Printers are: % PrintServer 40-series % PrintServer 20-series % PrintServer 32 % . % . % . % PostScript Level 2 PrintServer Printers are: % turbo PrintServer 20 % PrintServer 32-series % PrintServer 17-series should read: % PostScript Level 1 PrintServer Printers are: % PrintServer 40-series % PrintServer 20 % turbo PrintServer 20 with 12M memory % PrintServer 32 (has 12M memory) % . % . % . % PostScript Level 2 PrintServer Printers are: % turbo PrintServer 20 with 16M memory or more % PrintServer 32 plus (has 16M memory or more) % PrintServer 17-series 4.12 Documentation Errors The PrintServer 17 Operator's guide does not mention that the PrintServer 17 series printers support manual feed. This feature has been supported since Version 5.0. UNIX Release Notes 4-23