HP 4M Plus Printer Fails Printing Duplex When Set at 600 DPI

 Last reviewed: March 19, 1997
Article ID: Q163506
The information in this article applies to:
  • Microsoft Windows NT operating system version 3.1
  • Microsoft Windows NT Advanced Server version 3.1
  • Microsoft Windows NT Workstation versions 3.5, 3.51, and 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, and 4.0

SYMPTOMS

The Hewlett-Packard (HP) 4M Plus printer using the PostScript driver does not print duplex at 600 dots per inch (DPI), while 300 DPI works fine.

CAUSE

The 600 DPI setting requires more resources than 300 DPI. The 600 DPI setting prints four times as many dots per inch as 300 DPI. The default memory in the HP 4M Plus is not enough for most printouts to be duplexed. These printouts will print duplex if enough memory is added to the printer.

RESOLUTION

The manual for the HP 4M Plus recommends 12 MB of RAM for duplexing legal size pages. Some printouts may be complex enough to require even more memory to duplex.

MORE INFORMATION

HP 4M Plus is manufactured by Hewlett-Packard, a vendor independent of Microsoft; we make no warranty, implied or otherwise, regarding this product's performance or reliability.

Additional query words: prodnt
Keywords : kb3rdparty kbprint ntprint NTSrvWkst
Version : 3.1 3.5 3.51 4.0
Platform : WinNT

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 19, 1997
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.