We set our 8150's to Panic Behavior=DUMP_AND_REBOOT This works /most/ of the time... the printer will delete the job and reset itself. Sometimes it doesn't work.
We get the 79.00FE with things other than PDF printing as well..... sometimes even a student printing a text file from a Windows machine (using the PostScript driver) will hang the printers with the 79.00FE. It's strange. HP can offer no help. While it /may/ be related to Code Red activity, we keep very careful logs of all "hack attempts" against our network... Code Red activity has been fairly non-existant lately around here and the printers still act up. Here's the best part -- one of our 8150DN's is far worse about this than the other. We've patched the firmware on them both to the same, latest revisions... explain that one!!! Strangely enough, I /only/ have this problem with the 8150's when *nix is involved in the mix. But the funny part is, it's typically people printing from the Windows workstations that lock the printers up! Many of my clients have simple Win2K servers with 8150's or 5000's attached on the network (shared through the Win2K server), and anywhere from 5 to 50 Windows workstations printing to the printers... they never get the error. My prayer is that SOMEONE, SOMEWHERE will track this down and figure out what the heck is going on. --- Keith Rinaldo Systems Administrator College of Engineering University of Nevada, Las Vegas Email: [EMAIL PROTECTED] ----- Original Message ----- From: "Ken D'Ambrosio" <[EMAIL PROTECTED]> > On Wed, 2002-05-01 at 01:32, Glen Davison wrote: > > On Wed, 1 May 2002 13:50, you wrote: > > > On Tue, 30 Apr 2002, Keith Rinaldo wrote: > > > > How about the infamous 79.00FE error that all of our 8150DN's jam up with > > > > periodically? > > > > > > we also get this with 4000tn and 4500 s.. I assumed it had something to do > > > will a malformed ethernet frame... sure would be nice to eliminate them. > > Code Red may (or may not) have caused this, but it is *definitely* > possible to do it with Adobe Acrobat printing PDFs. I've had it happen > to a 4050, and 8550, and a 5000. I can reproduce it most reliably by > printing from AA on an HPUX box, and have had it happen regardless of > queuing software on the Linux box (LPR, CUPS and LPRng). The wonderful > thing about this particular glitch is that it actually "crashes" the > printer; a power-cycle just has the job get re-submitted, and cause the > same error; the job has to either be cancelled on the queue, or the > magic "delete job" (or whatever) button has to be pressed on the HP. If > anyone has any suggestion as to how to avoid this (trash the job, patch > it "mid-flight," whatever), I'd be most interested. > > > -------------------------------------------------------------------------- --- > 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. > -------------------------------------------------------------------------- --- > ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
