Problems with HP 4000 and 8000 printers cropping bottom third of page of print
Posted on 2004-11-11
All of our printers are HP4000 (network version I can't remember if it N, TN or what, they are networked with jet direct cards) except for 3 which are HP8000 printers. All of our users run Office XP Professional Suite. The majority of my users are on NT4.0 platforms, however I have 15 users who are on XP Professional operating system (no SP2 applied yet, but all other patches are up to date).
Here is the problem: for some reason the printers (both 4000 and 8000 models) just suddenly crop off the bottom third of the page of text. Usually if you print preview the document you can see that it is cutting off the bottom of the pages, however it has started cutting off the bottom of pages in the middle of a print job (for example, a 26 page document will print fine for the first 6 or 8 pages then cut off stuff for the remainder of the pages).
We have (1) downloaded the latest HP drivers for all the printers (both in the NT environment and the XP environment); (2) complete scrubbed the registry of all references to any printers and reinstalled the new drivers; (3) discovered "duplicate" vbs files on some workstations and deleted them but the problem comes back; (4) removed all references to printers in the registry and gone back to the original drivers from the original installation discs for the printers; and finally most drastic of all (4) completely reformatted workstations so we "start from scratch". None of the above actions solves our problem -- it only a temporary fix. The fact that this has started occurring in the middle of print jobs makes this way more than annoying. We have been battling this problem for 3 years. We even contacted Microsoft directly (and paid an outrageous amount of money to be told that they had never seen this problem before). Nothing solves the problem permanently. The best fix is to simply close Word once this happens and then reopen the application -- that is also a temporary fix because the problem always comes back. (Each user has their own "normal.dot" on their individual hard drives so if this is a "corrupted normal" I don't know how it could corrupt all the normals.)