On Thu, Jul 17, 2003 at 04:57:54PM -0700, Akop Pogosian wrote: > This is not exactly LPRng related. I have run into a Windows NT 4 > system that reliably brings up the 79.00FE error on HP8150 printer > which requires to power-cycle the printer every time it happens. The > print jobs are sent from the NT4 system to a Samba server which then > forwards them to LPRng. The NT4 system has the latest HP8150DN > postscript driver installed (dating from 1999). I have managed to > configure Samba so that it just saves the file instead of forwarding > it to LPRng. If I try to print this file directly, bypassing the LPRng > print server using the "lightweight" mode of LPRng's lpr command, it > still "bluescreens" the printer. This happens with everything that the > NT4 system attempts to print. The output file seems to contain PJL > commands. I could post the file if anyone is interested. The printer > has the latest HP firmware version, 20021010 MB7.109, that I could > find on HP's web site. Does anyone know a solution to this problem? > > > -akop
I have found an unexpected work-around to this problem after spending several hours looking into it. After updating the printer and jetdirect firmware to the latest versions, printing the sample file using the lpr in lightweight mode does not "bluescreen" the printer any more. However, if I send the job normally through the LPRng print server, 79.00FE error comes up again. While tinkering with various LPRng options, I stumbled upon this observation. If I create another queue but with a slightly different name than the one that results in printer displaying the 79.00FE error, the document prints fine. For example, the queue for this printer is called hp3 and it results in 79.00FE error. If I create a queue that's identically setup but with a name "hp3test", the file prints just fine. "hp3s" also works. The same holds true for our "hp1" queue. (e.g. if I rename it into hp1s or hp1test, file prints fine). I was really puzzled by this and decided to run snoop to capture the communication between the printer and printserver when using hp3 and hp3test queue. I have actually gone through each captured packet and compared the data sent to the printer port. It's all identical except that at the very beginning LPRng sends a print job control information string that's -slightly- different (and contains the name "hp3" instead of "hp3test") and this somehow causes the printer to die. Note that this is happening only with the files that come out of the NT4 system. The files printed by the unix users seem to print just fine on either queue. Amazing, isn't it? Anyways, for now I just pointed samba to the queue with a changed name and things seem to work fine. I also noticed that the same problem can't be reproduced with our newer (about 1 year old or newer) HP8150 printer. It turns out that the newer printers have a -different- jetdirect card version than our older 8150s and it uses a firmware version that's incompatible with the older HP LJ8150s. Who knows, maybe the newer HP LJ8510s have a somewhat less crash prone JetDirect card? -akop ----------------------------------------------------------------------------- YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST The address you post from MUST be your subscription address If you need help, send email to [EMAIL PROTECTED] (or lprng-requests or lprng-digest-requests) with the word 'help' in the body. For the impatient, to subscribe to a list with name LIST, send mail to [EMAIL PROTECTED] with: | example: subscribe LIST <mailaddr> | subscribe lprng-digest [EMAIL PROTECTED] unsubscribe LIST <mailaddr> | unsubscribe lprng [EMAIL PROTECTED] If you have major problems, send email to [EMAIL PROTECTED] with the word LPRNGLIST in the SUBJECT line. -----------------------------------------------------------------------------
