Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

HP print driver issue

HP print driver issue

HP print driver issue

We just resently switched our print servers, we were on windows 2003 and moved to windows 2008x64.  i downloaded the windows 2008 x64 & 32 print drivers for all our printers.  Some i had to use a UPD because it wasn't available.  I originally downloaed the pcl6 driver but now 3 different hp models are having the same issue.  when prining from excel it prints tons of junk pages.  all other programs seem to pprint file.  I switched the print drivers to Pcl5 and now it prints but before each jobs prints it also prints a page with "@PJL JOBATTR="JobAcct4=20100827171550"  @PJL SET JOBATTR="JobAcct5=dd on it.  We also have some richoh all in ones and have not been having any issues with them.  just the hp printers, 3 diff models with same problem.  Help!

RE: HP print driver issue

I saw that thread, personality is set for auto already. any other suggestions? thanks!

RE: HP print driver issue

I vaguely recall a similar problem from several years ago (before I retired) and the underlying problem was that the driver was NOT prefixing the PJL statements (at the beginning of each job) with a Universal Exit Language (UEL) escape sequence.

You could check to see if this is what is happening by doing a test print with the 'print to file' option selected in the printer Preferences dialogue.

Then examine the resultant .PRN file (you can open it with Notepad).
Whilst most of it may appear to be gobbledy-gook, all you are looking for is the first few characters:


where the first character (shown as  above) is the escape character (the character with decimal code 27, or hexadecimal 1B).

This should be followed by one or more @PJL commands.

If the UEL is NOT present, it may explain your symptoms - but I'm not sure what you could do about it, other than demand that MS and/or HP fix a bug in their driver.

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close